conflicts with -march= switch

[ng@piments.com]

On 04/22/10 09:11, ng@piments.com wrote:
> On 04/21/10 21:19, ng@piments.com wrote:
>> Hi again.
>>
>> using 1.6.0 I get some odd messages about "-march= switch"
>>
>>
>> [WARN ] /back/ts/ct-ng/targets/src/gcc-4.3.4/gcc/gcc.c:2990: warning:
>> format not a string literal and no format arguments
>> [WARN ] Saving state to restart at step 'libc_headers'...
>> [WARN ] configure: WARNING: you should use --build, --host, --target
>> [WARN ] configure: WARNING: In the future, Autoconf will not detect
>> cross-tools
>> [WARN ] *** WARNING: Are you sure you do not want to use the `nptl'
>> [WARN ] Saving state to restart at step 'libc_start_files'...
>> [WARN ] Removing "-pipe" for use with glibc>=2.6
>> [WARN ] configure: WARNING: In the future, Autoconf will not detect
>> cross-tools
>> [WARN ] checking whether ranlib is necessary... conftest.c:1: warning:
>> switch -mcpu=ep9312 conflicts with -march= switch
>>
>> It's only a warning but if there is a conflict it needs to be resolved:
>> which value is taking precendence in this "conflict"?
>>
>> I did not set switch so I'm not clear where this came from . why is
>> there a problem specifying a the cpu when using ct-ng?
>>
>> thanks.
>>
>> --
>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>
>>
>
> OK, I found a thread on nabble where a similar problem was fixed by
> ct-ng distclean.
>
> I'll assume that fixes it and start again.
>
> regards.
>

Oh well. I spoke too soon.

Even with a disclean and new tarballs I'm still getting both the nptl 
and a ton of -march conficts in gcc.

[WARN ]    /back/ts/ct-ng/targets/src/gcc-4.3.4/gcc/collect2.c:2135: 
warning: format not a string literal and no format arguments
[WARN ]    /back/ts/ct-ng/targets/src/gcc-4.3.4/gcc/gcc.c:2990: warning: 
format not a string literal and no format arguments
[WARN ]  Saving state to restart at step 'libc_headers'...
[WARN ]    configure: WARNING: you should use --build, --host, --target
[WARN ]    configure: WARNING: In the future, Autoconf will not detect 
cross-tools
[WARN ]    *** WARNING: Are you sure you do not want to use the `nptl'
[WARN ]  Saving state to restart at step 'libc_start_files'...
[WARN ]    Removing "-pipe" for use with glibc>=2.6
[WARN ]    configure: WARNING: In the future, Autoconf will not detect 
cross-tools
[WARN ]    checking whether ranlib is necessary... conftest.c:1: 
warning: switch -mcpu=ep9312 conflicts with -march= switch
[WARN ]    cc1: warning: switch -mcpu=ep9312 conflicts with -march= switch
[WARN ]    cc1: warning: switch -mcpu=ep9312 conflicts with -march= switch
[WARN ]    <stdin>:1: warning: switch -mcpu=ep9312 conflicts with 
-march= switch
[WARN ]    <stdin>:1: warning: switch -mcpu=ep9312 conflicts with 
-march= switch


however from the build.log:

[DEBUG]    CT_LIBC_SUPPORT_NPTL=y
[DEBUG]    CT_LIBC_SUPPORT_LINUXTHREADS=y
[DEBUG]    CT_THREADS="nptl"
[DEBUG]    CT_THREADS_NPTL=y
[DEBUG]    # CT_THREADS_LINUXTHREADS is not set
[DEBUG]    # CT_THREADS_NONE is not set



[DEBUG]    CT_ARCH_ARCH="armv4t"
[DEBUG]    CT_ARCH_CPU="ep9312

So why is ct-ng apparently not passing my NPTL and ARCH to configure ?

thanks.


--
For unsubscribe information see http://sourceware.org/lists.html#faq