Dear list readers,
I am doing initial work on a software project that is likely
to be closed source for a while.
One of the tasks is setting up the build process.
I would love to use the widely used toolset consisting
of autoconf, automake, libtool and also gettext for
this project.
My question
Hi,
I just discovered a nasty problem with the latest CVS Autoconf on Red
Hat Linux v7 (default setup, i.e. with g++ 2.96). In short, the
AC_TRY_COMPILE in the configure.in script below will fail:
->8-->8--->8-->8--->8-->8--->8-->8--->8-->8--->8-->8--->8-->8--
AC_INIT(configure.in)
AC_LANG_CPLU
[EMAIL PROTECTED] would probably be a better list to use. people
claim the problem is fixed at this point; send mail to postmaster if
there are still problems
Robert Boehne <[EMAIL PROTECTED]> writes:
> For me this is getting ridicilous, I'm getting from 2 to 7 copies of
> each postin
I'm checking in an update of libtool scripts, that, among other minor
things, fixes a subtle problem caused by a bug in Solaris' /bin/sh.
Basically, libtool used to set a variable cached in config.cache to a
string containing `}'. This `}' character got Solaris' /bin/sh
confused when the affected
