Re: HEADS UP: incompatible change with bsd.prefs.mk for i386

[Richard PALO <richard%netbsd.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 21/11/14 23:58, Joerg Sonnenberger a écrit :
|
| gcc shouldn't matter as long as you have don't try to make replace.
| Perl might. I am not that attached to the i486 part of the change,
| so if it creates too much trouble, that part can easily go back.
|
| Joerg
|

Thought I would take a look at perl..($WRKSRC/myconfig)

| #!/bin/sh
|
| # This script is designed to provide a handy summary of the
| configuration # information being used to build perl. This is
| especially useful if you # are requesting help from
| comp.lang.perl.misc on usenet or via mail.
|
| # Note that the text lines /^Summary of/ .. /^\s*$/ are copied into
| Config.pm. cat <<'!NO!SUBS!' Summary of my perl5 (revision 5
| version 20 subversion 1) configuration:
|
| Platform: osname=solaris, osvers=2.11, archname=i386-solaris
| uname='sunos omnis 5.11 illumos-gate-c40eb28 i86pc i386 i86pc '
| config_args='-sde -Duseshrplib -Uuseithreads -Dusedtrace
| -Uusemymalloc' hint=recommended, useposix=true, d_sigaction=define
| useithreads=undef, usemultiplicity=undef use64bitint=undef,
| use64bitall=undef, uselongdouble=undef usemymalloc=n,
| bincompat5005=undef Compiler: cc='gcc', ccflags ='-O2
| -I/opt/local/include -I/usr/include -fwrapv -fno-strict-aliasing
| -pipe -fstack-protector -I/opt/local/include -D_LARGEFILE_SOURCE
| -D_FILE_OFFSET _BITS=64 -DPERL_USE_SAFE_PUTENV', optimize='-O2
| -I/opt/local/include -I/usr/include', cppflags='-O2
| -I/opt/local/include -I/usr/include -fwrapv -fno-strict-aliasing
| -pipe -fstack-protector -I/opt/local/include' ccversion='',
| gccversion='4.9.2', gccosandvers='' intsize=4, longsize=4,
| ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define,
| longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long',
| ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
| alignbytes=4, prototype=define Linker and Libraries: ld='gcc',
| ldflags ='  -L/opt/local/gcc49/lib/gcc/i486-sun-solaris2.11/4.9.2
| -Wl,-R/opt/local/gcc49/lib/gcc/i486-sun-solaris2.11/4.9.2
| -L/opt/local/gcc49/lib -Wl,-R/opt/ local/gcc49/lib
| -L/opt/local/lib -L/usr/lib -Wl,-R/usr/lib -Wl,-R/opt/local/lib
| -fstack-protector -L/usr/gnu/lib ' libpth=/usr/lib /usr/ccs/lib
| /opt/local/lib /usr/gnu/lib libs=-lm -ldl -lsocket -lnsl
| perllibs=-lm -ldl -lsocket -lnsl libc=/lib/libc.so, so=so,
| useshrplib=true, libperl=libperl.so gnulibc_version='' Dynamic
| Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='
| -R /opt/local/lib/perl5/5.20.0/i386-solaris/CORE'
| cccdlflags='-fPIC', lddlflags='-shared
| -L/opt/local/gcc49/lib/gcc/i486-sun-solaris2.11/4.9.2
| -Wl,-R/opt/local/gcc49/lib/gcc/i486-sun-solaris2.11/4.9.2
| -L/opt/local/gcc4 9/lib -Wl,-R/opt/local/gcc49/lib -L/opt/local/lib
| -L/usr/lib -Wl,-R/usr/lib -Wl,-R/opt/local/lib -L/usr/gnu/lib
| -fstack-protector'
|
| !NO!SUBS!

it still creates and seems to use i386.

But I still question:
| $ bmake show-vars VARNAMES='MACHINE_ARCH MACHINE_GNU_ARCH' i386
| i486
is there a risk of confusion or even error can come out of this
difference in MACHINE*ARCH with package configure-related scripts?

There seems to be already some particular usage in pkgsrc where it
uses uname in mk/gnu-config.. for example, SUN_ARCH is always either
"i386" or "x86_64" in config.guess.

At best things seem a bit inconsistent now in some circonstances.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJUcNV+AAoJECAB22fHtp27zRgIAK8Z1O5o3AKpgAX2hyDa0BYH
W/OhKzvRei6Q5izklEDewfURGI0wrCHFeWnUeh/LHZvLn73Z1lckwragmzPBZ8P6
UAm3GP4lWWz2/TYlJK5nWFD7fQi7TgN12jL8bYTxHo14KRZ/qsXHhaE2fCY+RCIW
BRKEu/rkvh8ElRFj8kBze9dZcEEt8skx0vsb3+aIebcMJ6+vq3y5/MJw3rT7mJBL
6lKk9O7BM1Rzy3IaczoTt0V2b4yyQARpjUIG26yKRMVXcezzMX4BgE+Dl4t3f2K8
1jlHHdLFMYup7Wv8NguS5hzhIH4v8tiNNZpvvmxaqgX04/5Kdrwdzqwnuq9f9Oc=
=qMSn
-----END PGP SIGNATURE-----