Re: build failures after stdlib update

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Scot Hetzel
Date: Tuesday, March 23, 2010 - 11:19 am

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

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


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

Scot
_______________________________________________
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)