delorie.com/archives/browse.cgi | search |
From: | "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be> |
To: | <djgpp-workers AT delorie DOT com>, <pavenis AT lanet DOT lv> |
Subject: | RE: [PATCH] linking mkdoc.exe with libstdcxx.a (needed for gcc-3.0) |
Date: | Sat, 12 May 2001 17:52:10 +0200 |
Message-ID: | <CAEGKOHJKAAFPKOCLHDIMEEDCDAA.tim.van.holder@pandora.be> |
MIME-Version: | 1.0 |
X-Priority: | 3 (Normal) |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) |
In-Reply-To: | <3277-Sat12May2001160812+0300-eliz@is.elta.co.il> |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4133.2400 |
Importance: | Normal |
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 |
> I've seen that, but I don't understand how would this work. Isn't > libstdc++ built for a particular target? 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? > > Or am I missing something? > Well, those libraries would then be in /usr/i386-pc-msdosdjgpp/lib or whatever, and i386-pc-msdosdjgpp-gcc would look there first, so I don't see the problem.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |