Re: Problem with libtool 1.3.2 (Was: No configure script...)

That may fix your problem.  However, I was not even getting to libtool
myself.  The problem that I was encountering was a failure to build a
complete ./configure script.

-bryan

   References: <199906081330.JAA23062@server.internal.cog-tech.com>
   From: Steinar Bang <sb@metis.no>
   Date: 08 Jun 1999 15:33:47 +0200
   Lines: 29
   User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) XEmacs/20.4 (Emerald)
   MIME-Version: 1.0
   Content-Type: text/plain; charset=us-ascii
   Resent-From: www-lib@w3.org
   X-Mailing-List: <www-lib@w3.org> archive/latest/2285
   X-Loop: www-lib@w3.org
   Sender: www-lib-request@w3.org
   Resent-Sender: www-lib-request@w3.org
   Precedence: list

   >>>>> "Bryan B. Thompson" <bryan@cog-tech.com>:

   > These were the versions that I installed on a RedHat 4.2 system and they
   > DID NOT work:

   > 	automake	1.4
   > 	autoconf	2.13
   > 	libtool		1.3
   > 	make		3.74 (GNU)
   > 	gcc		2.7.2.1

   > Using Suse 6.1, the following versions of the relevant software were
   > installed by default, and WERE successful in compiling libwww:

   > 	automake	1.4
   > 	autoconf	2.13
   > 	libtool		1.2b
   > 	make		3.76.1 (GNU)
   > 	egcs		2.91.66

   > The problem seems to have been in automake/autoconf.  However, it
   > may be that there were problems in the versions of automake/autoconf
   > that I compiled on the RedHat 4.2 version, i.e., in the compiler
   > version, c library version, etc.

   Hm... maybe...

   One difference is the libtool version.  I think I will try downgrading 
   to 1.2something instead of 1.3.

Received on Tuesday, 8 June 1999 09:46:58 UTC