From: Mike Frysinger <vapier@gentoo.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] where is libgcc_so.1?
Date: Thu, 23 Sep 2010 04:58:52 -0400 [thread overview]
Message-ID: <201009230458.53089.vapier@gentoo.org> (raw)
In-Reply-To: <OFC021B02F.4495A915-ONC12577A7.00267184-C12577A7.0026F181@transmode.se>
[-- Attachment #1: Type: Text/Plain, Size: 871 bytes --]
On Thursday, September 23, 2010 03:05:21 Joakim Tjernlund wrote:
> Mike Frysinger wrote on 2010/09/23 00:05:31:
> > look at the stage list. you have to build a bare compiler (stage1)
> > before you can build the C library (stage3), and you need the C library
> > before you can build shared libraries like libgcc_s.so.1 (stage4).
>
> A bit strange that s3 can build the pthread shared lib then?
no. glibc dlopen's libgcc on the fly. the pthreads source code has some
comments in it explaining why. although this chicken & egg problem is a
pretty damn good reason -- you cant build shared gcc libs without a C library,
so requiring your gcc to have shared libs would be problematic ...
> The help text for S4 only indicates that S4 builds a C++ compiler(which I
> don't need ATM, that is why I skipped s4)
i guess it is a bit misleading
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-09-23 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 20:05 [gentoo-embedded] where is libgcc_so.1? Mike Frysinger
2010-09-22 7:37 ` Joakim Tjernlund
2010-09-22 22:05 ` Mike Frysinger
[not found] ` <OFC021B02F.4495A915-ONC12577A7.00267184-C12577A7.0026F181@transmode.se>
2010-09-23 8:58 ` Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-20 19:01 Joakim Tjernlund
2010-09-20 20:01 ` Mike Frysinger
2010-09-20 20:46 ` Joakim Tjernlund
2010-09-21 10:48 ` Joakim Tjernlund
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=201009230458.53089.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
--cc=joakim.tjernlund@transmode.se \
/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