From: Jim Wilson <wilson@cygnus.com>
To: Geoff Keating <geoffk@cygnus.com>
Cc: hjl@lucon.org, jason@redhat.com, wilson@cygnus.com,
aoliva@cygnus.com, gcc-patches@gcc.gnu.org,
binutils@sourceware.cygnus.com
Subject: Re: $(build_tooldir)/lib (was Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html)
Date: Fri, 21 Jul 2000 11:54:00 -0000 [thread overview]
Message-ID: <200007211854.LAA21292@wilson.cygnus.com> (raw)
In-Reply-To: <200007211746.KAA00571@localhost.cygnus.com>
There are certainly differences in the build process. HJ doesn't like to use
the --with-headers= and --with-libs= options that we recommend. I believe he
prefers to build gcc and glibc at the same time, kind of like we do with
newlib, but a lot more complicated.
If we are to make any progress on this, H.J. has to document his build process
sufficiently for others to reproduce it. The last time I asked this question,
H.J. reported what gcc configure command he was using, but didn't explain
where binutils came from, or where glibc came from. I haven't tried using
his gcc configure command, but perhaps there was enough info there if someone
has time to try it. See
http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01291.html
I suspect that the real problem might be at configuration time. HJ tends to
use a lot of configure options that we don't use. HJ uses --enable-shared a
lot more often than we do. Perhaps he built and installed a shared library in
$tooldir/lib and needs a -B option pointing there so that the shared library
will be found?
Jim
next prev parent reply other threads:[~2000-07-21 11:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000520093135A.mitchell@codesourcery.com>
[not found] ` <orhfbt9nwh.fsf@tamanduatei.dcc.unicamp.br>
[not found] ` <20000520095133R.mitchell@codesourcery.com>
2000-05-20 22:10 ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html H . J . Lu
2000-05-21 16:44 ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html Alexandre Oliva
2000-05-21 16:51 ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html H . J . Lu
2000-05-22 15:54 ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html Jim Wilson
2000-05-22 17:54 ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html H . J . Lu
2000-05-22 18:47 ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html Jim Wilson
2000-05-22 20:06 ` http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html H . J . Lu
2000-07-21 1:17 ` $(build_tooldir)/lib (was Re: http://gcc.gnu.org/ml/gcc-patches/2000-05/msg01104.html) Jason Merrill
2000-07-21 7:49 ` H . J . Lu
2000-07-21 10:38 ` Geoff Keating
2000-07-21 10:54 ` H . J . Lu
2000-07-21 11:54 ` Jim Wilson [this message]
2000-07-21 12:12 ` H . J . Lu
2000-07-21 14:19 ` Jason Merrill
2000-07-21 14:48 ` Geoff Keating
2000-07-21 14:53 ` H . J . Lu
2000-07-21 15:05 ` Jim Wilson
2000-07-21 15:12 ` H . J . Lu
2000-07-21 15:12 ` Geoff Keating
2000-07-21 15:49 ` H . J . Lu
2000-07-21 15:33 ` Angela Marie Thomas
2000-07-21 15:28 ` Jim Wilson
2000-07-21 17:15 ` Jason Merrill
2000-07-21 17:41 ` Jim Wilson
2000-07-21 18:01 ` Jason Merrill
2000-07-21 19:15 ` Alexandre Oliva
2000-07-21 19:20 ` Jason Merrill
2000-07-21 20:08 ` Alexandre Oliva
2000-07-21 20:26 ` H . J . Lu
2000-07-21 21:53 ` Jason Merrill
2000-07-21 22:29 ` Alexandre Oliva
2000-07-22 0:58 ` Jason Merrill
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=200007211854.LAA21292@wilson.cygnus.com \
--to=wilson@cygnus.com \
--cc=aoliva@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=geoffk@cygnus.com \
--cc=hjl@lucon.org \
--cc=jason@redhat.com \
/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).