X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Sun, 13 May 2001 15:14:05 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	djgpp-workers AT delorie DOT com
cc:	pavenis AT lanet DOT lv
Subject:	Re: [PATCH] linking mkdoc.exe with libstdcxx.a (needed for gcc-3.0)
In-Reply-To:	<3277-Sat12May2001160812+0300-eliz@is.elta.co.il>
Message-ID:	<Pine.LNX.4.10.10105131511270.13180-100000@acp3bf>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sat, 12 May 2001, Eli Zaretskii wrote:

> I've seen that, but I don't understand how would this work.  Isn't
> libstdc++ built for a particular target?  

Yes, of course it is.

> If so, this won't work
> unless there's only one libstdc++ on the host computer, and that
> single libstdc++ was built for DJGPP.  What if I have two or more
> cross-compilers on that host, complete with their respective C++
> libraries?

A correctly installed GCC is supposed to install libraries into
target-dependant paths (i.e. on my aged Digital-Unix/Alpha to DJGPP cross
builds, there's a $prefix/i586-msdos-djgpp/lib where this kind of stuff is
kept. Cross-GCC automatically searches there, first, and thus finds the
correct version.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -