Re: build failures after stdlib update

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Alexander Best
Date: Tuesday, March 23, 2010 - 2:34 am

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.

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. ;)

-- 
Alexander Best
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: build failures after stdlib update, Alexander Best, (Tue Mar 23, 2:34 am)
Re: build failures after stdlib update, Scot Hetzel, (Tue Mar 23, 11:19 am)
Re: build failures after stdlib update, Garrett Cooper, (Tue Mar 23, 12:07 pm)