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:jhell (jhe@DataIX.net)
Date:Mar 23, 2010 4:48:32 pm
List:org.freebsd.freebsd-current

On Tue, 23 Mar 2010 06:40, alexbestms@ wrote:

Pegasus Mc Cleaft schrieb am 2010-03-23:

-----Original Message-----

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.

;)

This is interesting. I tried the same thing on my computer (AMD64 - Core2 Quad) and I get the following

(Without CPUTYPE?=native in /etc/make) feathers$ make -V MACHINE_CPU -DCPUTYPE=native amd64 sse2 sse

(With CPUTYPE?=native) feathers$ make -V MACHINE_CPU -DCPUTYPE=native unknown amd64 sse2 sse mmx

(For both) feathers$ gcc -v -x c -E -mtune=native /dev/null -o /dev/null 2>&1 | grep mtune /usr/libexec/cc1 -E -quiet -v -D_LONGLONG /dev/null -o /dev/null -mtune=generic

hmm...that's odd indeed. i finally was able to do some debugging. i've attached two files:

running gcc -v -x c -E -mtune=native /dev/null and gcc -v -x c -E -mtune=nocona /dev/null

Peg

Both the commands that your showing the output of in the attached output are using gdb when the options that were presented are for gcc.

`gdb -v -x c -E -mtune=native /dev/null`

Should probably be: `gcc -v -x c -E -mtune=native /dev/null`

Right ?

Regards,

--

jhell

_______________________________________________ free@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free@freebsd.org"