I do not believe that this is the correct way to fix the
incompatability between CVS autoconf and libtool on the
multi-language-branch (it should be fixed in Autoconf rather than
libtool), but this is a patch to libtool that gets multi-lingual
libtool users over the hump. If this was the correct
Alexandre,
Libtool (libtool.m4) is checking the variable ac_cv_prog_gcc in order
to determine if the --with-gcc should be passed to ltconfig.
I see this in the Autoconf changelog:
2000-10-16 Akim Demaille <[EMAIL PROTECTED]>
* aclang.m4 (_AC_LANG_COMPILER_GNU): New macro, which unifi
After some spelunking, I find that the reason libtool is not
determining the correct PIC flags under Solaris is that even though
configure determines that the the compiler is the GNU C compiler, this
is not properly picked up by libtool. I see this in the generated
libtool script:
# Is the compi
On Nov 4, 2000, Bob Friesenhahn <[EMAIL PROTECTED]> wrote:
> Using CVS Autoconf & CVS multi-lingual libtool checked out today,
> configure guesses wrong on gcc PIC flags under Solaris 2.6:
Please try with autoconf 2.13. If it works, then bug [EMAIL PROTECTED]
Otherwise, please investigate :-)
Using CVS Autoconf & CVS multi-lingual libtool checked out today,
configure guesses wrong on gcc PIC flags under Solaris 2.6:
checking for gcc option to produce PIC... -KPIC -DPIC
checking if gcc PIC flag -KPIC -DPIC works... yes
checking if gcc static flag -Bstatic works... yes
ltconfig:675:che
