From: Linas Vepstas <linasvepstas@gmail.com>
To: gcc@gcc.gnu.org, GLIBC Devel <libc-alpha@sourceware.org>,
libc-ports@sourceware.org
Subject: gcc vs. glibc bootstrapping of libgcc_eh.a
Date: Wed, 09 Nov 2011 17:29:00 -0000 [thread overview]
Message-ID: <CAHrUA341B4RAvEFmx5pYOV7jqsLK_p9L9Jy45Y7eWoH15rjN9w@mail.gmail.com> (raw)
I've run into a bootstrapping issue which I'd like to solve
"the right way", instead of continuing to hack around it.
Briefly: I can't build glibc without libgcc_eh.a, which is
provided by gcc. However, libgcc_eh.a is not built, unless
I configure gcc with --enable-shared. But doing so causes
gcc to attempt to build libgcc_s.so, which fails because it
wants to link to libc.so, which hasn't been built yet. And
so it goes....
The "obvious" fix, to me, is to change the libgcc/Makefile.in
to always build libgcc_eh.a (and install it) Would such a
patch be acceptable?
BTW, this is for the "hexagon" architecture, being cross-built.
Perhaps there's some other work-around that I missed...
(our current work-around is to build uClibc first, install
that, and then finish building gcc, then build glibc. Seems
pretty yucky to me.)
--linas
next reply other threads:[~2011-11-09 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 17:29 Linas Vepstas [this message]
2011-11-09 17:53 ` Chris Metcalf
2011-11-10 2:50 ` Mike Frysinger
2011-11-11 21:27 ` Linas Vepstas
2011-11-11 21:43 ` Ian Lance Taylor
2011-11-11 22:23 ` Mike Frysinger
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=CAHrUA341B4RAvEFmx5pYOV7jqsLK_p9L9Jy45Y7eWoH15rjN9w@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).