conflicts with -march= switch

[ng@piments.com]

On 04/22/10 11:27, Yann E. MORIN wrote:
> NG, All,
>
> On Thursday 22 April 2010 095707 ng at piments dot com wrote:
>>>> [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'...
>
> This step is not _gcc_, it's the C library headers step.
>
>>>> [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'...
>
> And this one is the C library start files step.
>
> Oh, and by the way, sending only the WARNings is not very usefull. What is,
> is the full build.log file.
>
>>>> [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"?
>
> Forget it. glibc is wrong. I hate glibc. Period.
>
>> Even with a disclean and new tarballs I'm still getting both the nptl
>> and a ton of -march conficts in gcc.
> [--SNIP--]
>> So why is ct-ng apparently not passing my NPTL and ARCH to configure ?
>
> Look in the code, there is an explanation for this (Hint: search the
> code for the glibc headers install step. Hint-2: NPTL is a threading
> implementation, as linuxthreads is).

Hi Yann,

thanks very much for the pointer but I only find a comment in the 
opposite sense:

     # Set --build so maybe we don't have to specify 
"cross-compiling=yes" below (haven't tried yet)
     # Note: the warning
     # "*** WARNING: Are you sure you do not want to use the `linuxthreads'"
     # *** add-on?"
     # is ok here, since all we want are the basic headers at this point.


Is that what you were thinking of?

Also I was a bit surprised to see SUPPORT_LINUXTHREADS when I had 
selected nptl. In fact I thought that recent glibc no longer recognised 
linuxthreads.

It does not seem to be possible to unset this from menuconfig.

CT_LIBC_SUPPORT_LINUXTHREADS=y
# CT_THREADS_LINUXTHREADS is not set

Is that an oversight or an necessary evil.

best regards, Peter.


>
> Regards,
> Yann E. MORIN.
>


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