From: "Laurynas Biveinis" <lauras AT softhome DOT net>
Date: Tue, 19 Jun 2001 19:40:07 +0200
To: djgpp-workers AT delorie DOT com
Cc: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
Subject: Re: Package of libtool?
Message-ID: <20010619194007.A1802@lauras.lt>
Mail-Followup-To: djgpp-workers AT delorie DOT com,
	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
References: <CAEGKOHJKAAFPKOCLHDIKEHECEAA DOT tim DOT van DOT holder AT pandora DOT be>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAEGKOHJKAAFPKOCLHDIKEHECEAA.tim.van.holder@pandora.be>
User-Agent: Mutt/1.3.18i
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


> 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).
> An obvious fix is to simply edit ltconfig to not use this option; 

This is exactly the problem and the fix I've made with GCC libtool - disable
-fPIC -DPIC on per platform basis. This fix has been accepted upstream, so
IMHO it's the way to go.

As far as GCC is concerned, it might be useful to see what other static-only
targets do with -fPIC. Ignore silently?

Laurynas