This is done deliberately, to enable you to run NetBSD-i386 images on
a NetBSD-amd64 host.

If you want to eliminate these compatability libraries, you can set
the MKCOMPAT variable to NO:

        build.sh ... -V MKCOMPAT=NO release


On Sat, 23 May 2020, [email protected] wrote:

Hej,

I just tried to build release with optimisation for my little xeon server.
That fails, but I don???t understand why it seems to build some 386 32bit libs.
???
#     build  libgcc_s/libgcc_s.so.1.0
rm -f libgcc_s.so.1.0
/hurz/obj/tooldir.NetBSD-9.99.63-amd64/bin/x86_64--netbsd-gcc -nodefaultlibs 
-shared -Wl,-soname,libgcc_s.so.1  -Wl,--warn-shared-textrel 
-Wl,-Map=libgcc_s.so.1.map   -m32 
--sysroot=/hurz/obj/destdir.NetBSD-9.99.63-amd64 -nodefaultlibs -Wl,-z 
-Wl,nodelete 
-Wl,--version-script=/hurz/src/external/gpl3/gcc/lib/libgcc/libgcc_s/libgcc.map 
-Wl,-z,relro  -o libgcc_s.so.1.0.tmp  -Wl,-rpath,/usr/lib/i386  
-L=/usr/lib/i386 -Wl,-x  -Wl,--whole-archive libgcc_s_pic.a  
-Wl,--no-whole-archive -m32
/hurz/obj/tooldir.NetBSD-9.99.63-amd64/lib/gcc/x86_64--netbsd/8.4.0/../../../../x86_64--netbsd/bin/ld:
 i386:x86-64 architecture of input file 
`/hurz/obj/destdir.NetBSD-9.99.63-amd64/usr/lib/../lib/i386/crti.o' is 
incompatible with i386 output
???
optimization was done using cpuflags:
ARCH            : -march=native
FEATURES        : -mfpmath=sse -msse3
CPUFLAGS        : -mfpmath=sse -msse3 -march=native
GCC version     : 8.4.0
OS              : 'NetBSD'
OS version      : '9.99.63'
hw.model        : 'Intel 686-class'
hw.machine      : 'amd64'
hw.machine_arch : 'x86_64'
CPU             : ''
cpu_name="highest basic info 0000000d"
cpu_brand="IntelR XeonR CPU E5-2640 0 @ 2.50GHz???

Any ideas?

cheers
        Oskar



+--------------------+--------------------------+-----------------------+
| Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
| (Retired)          | FA29 0E3B 35AF E8AE 6651 | [email protected]     |
| Software Developer | 0786 F758 55DE 53BA 7731 | [email protected]   |
+--------------------+--------------------------+-----------------------+

Reply via email to