From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Adrian Alonso <aalonso00@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: pseudo native build fails on Fedora 14
Date: Thu, 23 Dec 2010 18:59:48 +0000 [thread overview]
Message-ID: <1293130788.17519.217.camel@rex> (raw)
In-Reply-To: <AANLkTim9iax+7aW3tmBUtmCdjtgAr0nT5U0nhwi+j2Ay@mail.gmail.com>
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
next prev parent reply other threads:[~2010-12-23 19:00 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 [this message]
2010-12-23 22:37 ` Mark Hatle
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=1293130788.17519.217.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=aalonso00@gmail.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