* [gentoo-embedded] crossdev: glibc: CC wrong, which CHOST in config.site
@ 2011-03-19 21:21 Jan Kobler
2011-03-20 6:57 ` Mike Frysinger
0 siblings, 1 reply; 4+ messages in thread
From: Jan Kobler @ 2011-03-19 21:21 UTC (permalink / raw
To: gentoo-embedded
Hi,
1. I have tried today
crossdev --target powerpc-unknown-linux-gnu
and got the error message:
configure:2114: checking for powerpc-unknown-linux-gnu-gcc
configure:2141: result: x86_64-pc-linux-gnu-gcc
checking whether x86_64-pc-linux-gnu-gcc -pipe -freorder-blocks -O2
-fno-strict-aliasing supports -mabi=ibmlongdouble... no
configure: error: this configuration requires -mlong-double-128 IBM
extended format support
* ERROR: cross-powerpc-unknown-linux-gnu/glibc-2.13-r2 failed (compile
phase):
* failed to configure glibc
2. After looking at
/tmp/portage/cross-powerpc-unknown-linux-gnu/glibc-2.13-r2/work/glibc-2.13/configure
I found out that the environment variable CC is wrong.
This command worked:
crossdev --lenv "CC=powerpc-unknown-linux-gnu-gcc" --target
powerpc-unknown-linux-gnu
3. Is this a correct behavior that I need to set CC on the commandline?
4. I have a question about the loading of /usr/share/config.site
in glibc-2.13/configure
crossdev --lenv "CC=powerpc-unknown-linux-gnu-gcc" --target
powerpc-unknown-linux-gnu
>>> Compiling source in
/tmp/portage/cross-powerpc-unknown-linux-gnu/glibc-2.13-r2/work/glibc-2.13
...
* ABI: default
* CBUILD: x86_64-pc-linux-gnu
* CHOST: x86_64-pc-linux-gnu
* CTARGET: powerpc-unknown-linux-gnu
* CBUILD_OPT:
* CTARGET_OPT:
* CC: powerpc-unknown-linux-gnu-gcc
* CFLAGS: -pipe -freorder-blocks -O2 -fno-strict-aliasing
* Manual CC: powerpc-unknown-linux-gnu-gcc
configure: loading site script /usr/share/config.site
When the script /usr/share/config.site is executed, the above value
CHOST=x86_64-pc-linux-gnu
is used to find the site script files in /usr/share/crossdev/include/site.
Is this correct?
Is it looking for the definitions of the build system or the target system?
I am using sys-devel/crossdev-20110310
Best regards
Jan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-embedded] crossdev: glibc: CC wrong, which CHOST in config.site
2011-03-19 21:21 [gentoo-embedded] crossdev: glibc: CC wrong, which CHOST in config.site Jan Kobler
@ 2011-03-20 6:57 ` Mike Frysinger
2011-03-20 22:40 ` Mike Frysinger
0 siblings, 1 reply; 4+ messages in thread
From: Mike Frysinger @ 2011-03-20 6:57 UTC (permalink / raw
To: gentoo-embedded
[-- Attachment #1: Type: Text/Plain, Size: 596 bytes --]
On Saturday, March 19, 2011 17:21:49 Jan Kobler wrote:
> checking whether x86_64-pc-linux-gnu-gcc -pipe -freorder-blocks -O2
> -fno-strict-aliasing supports -mabi=ibmlongdouble... no
> configure: error: this configuration requires -mlong-double-128 IBM
> extended format support
> * ERROR: cross-powerpc-unknown-linux-gnu/glibc-2.13-r2 failed (compile
> phase):
> * failed to configure glibc
you didnt say what step this was exactly. is it the glibc headers step or is
it glibc itself ?
> 3. Is this a correct behavior that I need to set CC on the commandline?
no
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-embedded] crossdev: glibc: CC wrong, which CHOST in config.site
2011-03-20 6:57 ` Mike Frysinger
@ 2011-03-20 22:40 ` Mike Frysinger
2011-03-21 0:22 ` Jan Kobler
0 siblings, 1 reply; 4+ messages in thread
From: Mike Frysinger @ 2011-03-20 22:40 UTC (permalink / raw
To: gentoo-embedded
[-- Attachment #1: Type: Text/Plain, Size: 675 bytes --]
On Sunday, March 20, 2011 02:57:54 Mike Frysinger wrote:
> On Saturday, March 19, 2011 17:21:49 Jan Kobler wrote:
> > checking whether x86_64-pc-linux-gnu-gcc -pipe -freorder-blocks -O2
> > -fno-strict-aliasing supports -mabi=ibmlongdouble... no
> > configure: error: this configuration requires -mlong-double-128 IBM
> > extended format support
> >
> > * ERROR: cross-powerpc-unknown-linux-gnu/glibc-2.13-r2 failed (compile
> >
> > phase):
> > * failed to configure glibc
>
> you didnt say what step this was exactly. is it the glibc headers step or
> is it glibc itself ?
if it's the actual libc build (not the headers), it should work now
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-embedded] crossdev: glibc: CC wrong, which CHOST in config.site
2011-03-20 22:40 ` Mike Frysinger
@ 2011-03-21 0:22 ` Jan Kobler
0 siblings, 0 replies; 4+ messages in thread
From: Jan Kobler @ 2011-03-21 0:22 UTC (permalink / raw
To: gentoo-embedded; +Cc: Mike Frysinger
Hi Mike,
the step has been
* Emerging cross-glibc ...
The new version of glibc can be built now without problems.
Thank your for fixing it this fast.
Jan
on 20.03.2011 23:40 Mike Frysinger said the following:
> On Sunday, March 20, 2011 02:57:54 Mike Frysinger wrote:
>> On Saturday, March 19, 2011 17:21:49 Jan Kobler wrote:
>>> checking whether x86_64-pc-linux-gnu-gcc -pipe -freorder-blocks -O2
>>> -fno-strict-aliasing supports -mabi=ibmlongdouble... no
>>> configure: error: this configuration requires -mlong-double-128 IBM
>>> extended format support
>>>
>>> * ERROR: cross-powerpc-unknown-linux-gnu/glibc-2.13-r2 failed (compile
>>>
>>> phase):
>>> * failed to configure glibc
>>
>> you didnt say what step this was exactly. is it the glibc headers step or
>> is it glibc itself ?
>
> if it's the actual libc build (not the headers), it should work now
> -mike
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-03-21 1:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-19 21:21 [gentoo-embedded] crossdev: glibc: CC wrong, which CHOST in config.site Jan Kobler
2011-03-20 6:57 ` Mike Frysinger
2011-03-20 22:40 ` Mike Frysinger
2011-03-21 0:22 ` Jan Kobler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox