From: Mark Hatle <mark.hatle@windriver.com>
To: poky@yoctoproject.org
Subject: Re: pseudo native build fails on Fedora 14
Date: Thu, 23 Dec 2010 16:37:47 -0600 [thread overview]
Message-ID: <4D13CF3B.3030501@windriver.com> (raw)
In-Reply-To: <1293130788.17519.217.camel@rex>
Form the pastebin, it appears to have been building the 32-bit portions. If
this is a 64-bit Fedora.. it looks like you have a partial 32-bit run-time
environment installed. The system detected this and attempted to build a 32-bit
wrapper (as well as the 64-bit version). Likely you are missing the 32-bit gcc
or libgcc package. (Sorry I don't know the actual name of the package.)
(We have to build both a 64-bit and 32-bit version of pseudo, if we detect
32-bit on the system, because we have no way of knowing what applications will
be loaded. The apps executed MAY be either 32-bit or 64-bit, so we need a
wrapper library for each available... even if the system's primary applications
and libraries are 64-bit.)
--Mark
On 12/23/10 12:59 PM, Richard Purdie wrote:
> On Thu, 2010-12-23 at 12:27 -0600, Adrian Alonso wrote:
>> I start a build from scratch and pseudo-native fails to build
>> at link stage:
>>
>>
>> ...
>> /usr/bin/ld: skipping
>> incompatible /usr/lib/gcc/x86_64-redhat-linux/4.5.1/libgcc_s.so when
>> searching for -lgcc_s
>> | /usr/bin/ld: cannot find -lgcc_s
>> | collect2: ld returned 1 exit status
>> ....
>
> What kind of machine is this? Mixed 32 bit and 64 bit userspace? 64 or
> 32 bit kernel?
>
> To me, this looks like you have half a 32 or 64 bit toolchain alongside
> the "correct" one and its preferring that for some reason.
>
> Cheers,
>
> Richard
>
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2010-12-23 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 18:27 pseudo native build fails on Fedora 14 Adrian Alonso
2010-12-23 18:59 ` Richard Purdie
2010-12-23 22:37 ` Mark Hatle [this message]
2010-12-27 16:20 ` Adrian Alonso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D13CF3B.3030501@windriver.com \
--to=mark.hatle@windriver.com \
--cc=poky@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox