From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: Bernd Jendrissek <berndfoobar@users.sourceforge.net>
Cc: Alexandre Oliva <aoliva@redhat.com>,
Nathanael Nerode <neroden@twcny.rr.com>,
gcc@gcc.gnu.org, gdb@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: Partial autoconf transition thoughts
Date: Thu, 12 Jun 2003 12:26:00 -0000 [thread overview]
Message-ID: <Pine.GSO.3.96.1030612141547.25948F-100000@delta.ds2.pg.gda.pl> (raw)
In-Reply-To: <20030612140830.C3057@prism.co.za>
On Thu, 12 Jun 2003, Bernd Jendrissek wrote:
> > But libbfd is target-specific, so you can't install it directly in
>
> That sounds like an artificial limitation. Maybe it works best in
> single-target configuration, but I've been using it with --enable-targets=all
> for the last year or two.
Not a limitation, but a configuration choice. I don't want to enable all
targets and I want to keep all target configurations self contained --
suitable for binary packaging.
> > $exec_prefix/$target_alias/$host_alias/lib. Of coures neither
> > $exec_prefix/lib nor $exec_prefix/$target_alias/lib can be used as they
> > (may) hold other versions of libbfd and $exec_prefix/$host_alias cannot
> > be, either, as it would work for a single target only.
>
> What's wrong with $exec_prefix/$target_alias/lib? What "other" versions
> of libbfd?
That's the place for libbfd for the host, e.g. assuming the build system
is i386-linux:
- $exec_prefix/lib/libbfd.la: i386-linux host binary for i386-linux
target,
- $exec_prefix/alpha-linux/lib/libbfd.la: alpha-linux host binary for
alpha-linux target,
- $exec_prefix/i386-linux/alpha-linux/lib/libbfd.la: i386-linux host
binary for alpha-linux target,
- $exec_prefix/i386-linux/mipsel-linux/lib/libbfd.la: i386-linux host
binary for mipsel-linux target
- $exec_prefix/mipsel-linux/lib/libbfd.la: mipsel-linux host binary for
mipsel-linux target.
> Again, $exec_prefix/lib works just fine here with --enable-targets=all'ed
> binutils.
I suppose so, but I don't want such a configuration.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
next prev parent reply other threads:[~2003-06-12 12:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 0:40 Nathanael Nerode
2003-06-10 0:59 ` Alexandre Oliva
2003-06-10 10:59 ` Maciej W. Rozycki
2003-06-10 11:38 ` Andreas Schwab
2003-06-10 12:45 ` Maciej W. Rozycki
2003-06-10 22:06 ` Alexandre Oliva
2003-06-11 11:32 ` Maciej W. Rozycki
2003-06-11 18:04 ` Alexandre Oliva
2003-06-11 19:39 ` Maciej W. Rozycki
2003-06-11 20:39 ` Alexandre Oliva
2003-06-12 11:21 ` Maciej W. Rozycki
2003-06-12 12:10 ` Bernd Jendrissek
2003-06-12 12:26 ` Maciej W. Rozycki [this message]
2003-06-12 21:42 ` Alexandre Oliva
2003-06-13 10:35 ` Maciej W. Rozycki
2003-06-13 14:02 ` Alexandre Oliva
2003-06-13 18:32 ` Maciej W. Rozycki
2003-06-13 19:25 ` Alexandre Oliva
2003-06-13 20:15 ` Maciej W. Rozycki
2003-06-13 20:54 ` Alexandre Oliva
2003-06-14 14:33 ` Maciej W. Rozycki
2003-06-14 15:43 ` Alexandre Oliva
2003-06-14 18:27 ` Maciej W. Rozycki
2003-06-26 7:24 ` Alexandre Oliva
2003-06-28 0:35 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 1:40 Nathanael Nerode
2003-06-10 1:46 ` DJ Delorie
2003-06-09 22:02 Daniel Jacobowitz
2003-06-09 22:17 ` Andrew Cagney
2003-06-09 22:34 ` Alexandre Oliva
2003-06-09 23:14 ` Daniel Jacobowitz
2003-06-10 0:44 ` Alexandre Oliva
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=Pine.GSO.3.96.1030612141547.25948F-100000@delta.ds2.pg.gda.pl \
--to=macro@ds2.pg.gda.pl \
--cc=aoliva@redhat.com \
--cc=berndfoobar@users.sourceforge.net \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.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).