From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: Re: Package of libtool?
Date: Tue, 19 Jun 2001 18:04:03 +0200
Message-ID: <CAEGKOHJKAAFPKOCLHDIMEIBCEAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <Pine.SUN.3.91.1010619115840.7390Q-100000@is>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
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
Precedence: bulk

> On Mon, 18 Jun 2001, Tim Van Holder wrote:
> 
> > From my attempts at building cvs gettext (which now uses 1.4) 
> there should
> > be no problem, save one.  ltconfig uses -fPIC as compiler option to
> > produce PIC code.  gcc happily accepts this option and 
> generates assembler
> > code our as can't grok (bfd assertions get thrown).
> 
> libtool used not to do that with DJGPP (IIRC, the -fPIC test was
> present in libtool for quite some time).  What changed?

I don't know - all I know is that the case structure that decides on
the flag to use no longer mentions msdosdjgpp*, so it falls back on
the default (-fPIC).  Still, that shouldn't be a problem as the
compiler handles the option just fine - it's just the assembler that
has a problem (and, judging from the particular error, it's either
a simple configuration error or a problem that affects the entire
coff-i386 portion of BFD).  I expect it would not be to hard to have
as ignore the extra thing gcc generates (basically, it appends @GOTOFF
or @PLT to some symbols; not much else seems to change).
I'll try and take a look over the weekend.