Re: build failures after stdlib update

On Tue, 23 Mar 2010 06:40, alexbestms_at_ 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