This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: libbfd for cross target II

From: "Svein E. Seldal" <Svein dot Seldal at solidas dot com>
To: Alan Modra <amodra at bigpond dot net dot au>
Cc: binutils at sources dot redhat dot com
Date: Sat, 30 Nov 2002 03:44:52 +0100
Subject: Re: libbfd for cross target II
References: <3DE7378B.9060600@solidas.com> <3DE73D02.30402@solidas.com> <20021130012035.GM949@bubble.sa.bigpond.net.au>

Alan Modra wrote:

On Fri, Nov 29, 2002 at 11:10:10AM +0100, Svein E. Seldal wrote:

>... and I see that it installs libbfd.a under
>'i686-pc-linux-gnu/tic4x/lib'. How can I identify the
>"i686-pc-linux-gnu" string from a shellscript or Makefile?


If you don't specify --host when configuring, then config.guess
chooses the host for you.  Run config.guess from your script.
To force installation of libbfd on a cross host, use
--enable-install-libbfd

Thanks. That answered one of my two question.

The other was not in respect of development, but for users. Maybe I should rephrase myself to say "how can users identify i686-bla-bla from their scripts". Because they/we need the target libbfd.a for applications and we need to know how to access this lib from our makefiles and scripts...

Svein

References:
- libbfd for cross target
  - From: Svein E. Seldal
- libbfd for cross target II
  - From: Svein E. Seldal
- Re: libbfd for cross target II
  - From: Alan Modra

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]