Mail Archives: djgpp-workers/2001/06/19/08:34:47
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.
Hm... but doesn't it only do that if building of *shared* libraries is
active? Since those are a non-issue for DJGPP anyway, can't we just
disable that whole branch of it once and for all, for a DJGPP port
(effictively forcing the --disable-shared option for all DJGPP builds)? At
least to me, that seems like the obvious thing to do.
> An obvious fix is to simply edit ltconfig to not use this option; I've
> also mailed a report to Mark & Andris, but I'm not sure if this is something
> that should be handled in binutils (ie add support to bfd) or gcc (ie
> disallow -fPIC for a djgpp host).
That would be another possibility, indeed. We don't need PIC, so there
wouldn't be any harm done by turning it off completely already at the GCC
stage. But even so, it'd be a waste of CPU time and porting effort to try
and support the shared-library building parts of libtool in DJGPP.
> Otherwise, libtool 1.4 seems to work very well (at least with autoconf 2.50
> and a cvs automake).
Which currently is a big stumbling block, IMHO. It's somewhat silly for
a released version of one tool to require a (hacked) CVS-only version of
some other to work properly. gnu.utils.bug is currently discussing this.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -