atom feed46 messages in org.freebsd.freebsd-currentRe: build failures after stdlib update
FromSent OnAttachments
Pegasus Mc CleaftMar 13, 2010 10:30 am 
Garrett CooperMar 13, 2010 12:49 pm 
Pegasus Mc CleaftMar 13, 2010 4:33 pm 
Alexander BestMar 16, 2010 4:15 am 
Peter JeremyMar 16, 2010 12:37 pm 
Alexander BestMar 16, 2010 7:22 pm 
Pegasus Mc CleaftMar 16, 2010 7:29 pm 
Pegasus Mc CleaftMar 17, 2010 9:53 am 
Alexander BestMar 20, 2010 3:21 pm 
Alexander BestMar 20, 2010 5:54 pm 
Andriy GaponMar 20, 2010 7:27 pm 
Garrett CooperMar 20, 2010 9:47 pm 
Alexander BestMar 21, 2010 3:59 am.txt
Garrett CooperMar 21, 2010 4:42 am 
Andriy GaponMar 21, 2010 5:01 am 
Alexander BestMar 21, 2010 5:26 am.conf, .conf
Pegasus Mc CleaftMar 21, 2010 5:32 am 
Alexander BestMar 21, 2010 5:35 am.txt
Alexander BestMar 21, 2010 5:43 am 
Andriy GaponMar 21, 2010 5:50 am 
Alexander BestMar 21, 2010 5:53 am 
Gary JennejohnMar 21, 2010 6:02 am 
Gary JennejohnMar 21, 2010 6:07 am 
Andriy GaponMar 21, 2010 8:10 am 
Dimitry AndricMar 21, 2010 8:34 am 
Alexander BestMar 21, 2010 11:45 am 
Andriy GaponMar 21, 2010 1:28 pm 
Alexander BestMar 21, 2010 2:10 pm 
Garrett CooperMar 21, 2010 2:19 pm.log
Garrett CooperMar 21, 2010 2:20 pm 
Garrett CooperMar 21, 2010 2:23 pm 
Andriy GaponMar 21, 2010 2:31 pm 
Alexander BestMar 21, 2010 3:11 pm 
jhellMar 21, 2010 5:28 pm 
Dimitry AndricMar 22, 2010 12:54 am 
Andriy GaponMar 22, 2010 1:07 am 
Alexander BestMar 22, 2010 2:39 am 
Scot HetzelMar 22, 2010 7:57 pm 
Alexander BestMar 23, 2010 2:33 am 
Pegasus Mc CleaftMar 23, 2010 2:59 am 
Alexander BestMar 23, 2010 3:40 am.txt, .txt
Scot HetzelMar 23, 2010 11:19 am 
Garrett CooperMar 23, 2010 12:07 pm 
Alexander BestMar 23, 2010 3:35 pm 
jhellMar 23, 2010 4:48 pm 
Xin LIMar 23, 2010 5:05 pm 
Subject:Re: build failures after stdlib update
From:Alexander Best (alex@wwu.de)
Date:Mar 23, 2010 3:35:58 pm
List:org.freebsd.freebsd-current

Scot Hetzel schrieb am 2010-03-23:

On Tue, Mar 23, 2010 at 4:34 AM, Alexander Best <alex@wwu.de> wrote:

i don't think conf/112997 and the issue where gcc segfaults are directly related to each other:

1. if CPUTYPE is set to 'native' your patch uses `gcc -v -x c -E -mtune=native /dev/null -o /dev/null 2>&1 | grep mtune | sed -e 's/.*mtune=//'` to determine gcc's idea of the appropriate -mtune value. that command however segfaults. so this doesn't really help.

The command runs correctly with a properly built gcc:

# gcc -v -x c -E -mtune=native /dev/null -o /dev/null 2>&1 | grep mtune | sed -e 's/.*mtune=//' generic

i was finally able to solve this issue. it turns out the issue was caused by an option in my CLFAGS called "-fno-builtin". sys/conf/NOTES recommends using this switch for kernel builds, but it seems in a world environment the flag is harmful to gcc. a gcc built with "-fno-builtin" trips over strlen() for some reason.

you should be able to reproduce this problem simply by adding "-O2 -fno-strict-aliasing -pipe -fno-builtin" to your CFLAGS. maybe "-O2 -fno-builtin" triggers it too, but "-fno-builtin" (without -O2) doesn't.

thanks to everyone for all the help. :)

cheers. alex

2. i wasn't able to reproduce your `make -V MACHINE_CPU -DCPUTYPE=native` examples. for me `make` prints the same no matter what CPUTYPE is set to:

otaku% make -V MACHINE_CPU -DCPUTYPE=native amd64 sse2 sse otaku% make -V MACHINE_CPU -DCPUTYPE=nocona amd64 sse2 sse otaku% make -V MACHINE_CPU -DCPUTYPE=i386 amd64 sse2 sse otaku% make -V MACHINE_CPU -DCPUTYPE=lalalala amd64 sse2 sse

..oh and of course i ran these commands with no CPUTYPE set in make.conf. ;)

If I run the same commands as above, I get similar results:

# make -V MACHINE_CPU -DCPUTYPE=native amd64 sse2 sse # make -V MACHINE_CPU -DCPUTYPE=k8 amd64 sse2 sse # make -V MACHINE_CPU -DCPUTYPE=nocona amd64 sse2 sse # make -V MACHINE_CPU -DCPUTYPE=i386 amd64 sse2 sse # make -V MACHINE_CPU -DCPUTYPE=lala amd64 sse2 sse

But if I run the commands without the "-D", it shows the problem correctly:

# make -V MACHINE_CPU CPUTYPE=native unknown amd64 sse2 sse mmx # make -V MACHINE_CPU CPUTYPE=k8 k8 3dnow amd64 sse2 sse mmx # make -V MACHINE_CPU CPUTYPE=nocona sse3 amd64 sse2 sse mmx # make -V MACHINE_CPU CPUTYPE=i386 unknown amd64 sse2 sse mmx # make -V MACHINE_CPU CPUTYPE=lalala unknown amd64 sse2 sse mmx # grep CPUTYPE /etc/make.conf /etc/src.conf grep: /etc/src.conf: No such file or directory

This was run under a Feb 28th -CURRENT.

Now here is something strange. Defining CPUTYPE in /etc/src.conf has no effect on the output of MACHING_CPU.

/etc/src.conf: 1 lines, 11 characters. # make -V MACHINE_CPU ; grep CPUTYPE /etc/make.conf /etc/src.conf amd64 sse2 sse /etc/src.conf:CPUTYPE=k8

# make -V MACHINE_CPU ; grep CPUTYPE /etc/make.conf /etc/src.conf k8 3dnow amd64 sse2 sse mmx /etc/make.conf:CPUTYPE=k8