Subtitle: It's hard to make things foolproof, because fools are so clever...
OK, Justus put me on the track of this. It is clearly stated in the autoconf Web site, that the Alpha/Beta versions of autoconf are EVIL! EVIL! and should not be used in production systems. This applies to the various things they supply as well: config.sub and config.guess So, guess what the latest versions of libtool and automake use? libtool/libtool-1.4.2/config.sub timestamp='2001-09-07' autoconf/autoconf-2.52/config/config.sub timestamp='2001-06-08' autoconf/automake-1.5/lib/config.sub timestamp='2001-08-13' libtool/libtool-1.4.2/config.guess timestamp='2001-09-04' autoconf/autoconf-2.52/config/config.guess timestamp='2001-07-12' autoconf/automake-1.5/lib/config.guess timestamp='2001-08-21' OOOPSSS!!! So now what do we do if we use autconf/automake AND libtool? I would suspect the latest version, right? So I should use the latest versions. Now of course, this means that I cannot use the 'off the shelf' configuration tools any more, and have the check to see what the latest versions are... and update this for the distribution. And then check to make sure that autoconf still works the config.guess, and other stuff. So what do I need to do? Right. Update the installed files in /usr/local/share/autoconf,libtool, etc. with the latest versions. GRRHHHH Now of course, libtoolize, autoconf, and autoheader will battle it out for 'correct version'. Patrick > From [EMAIL PROTECTED] Thu Feb 21 10:38:02 2002 > From: [EMAIL PROTECTED] > To: Patrick Powell <[EMAIL PROTECTED]> > Date: Thu, 21 Feb 2002 13:37:45 -0500 > Subject: Re: LPRng: Configure/Compile bugs in LPRng-3.8.5 and ifhp-3.5.3 > > > > I have little experience with Autoconf (configure) , but it appears to me that > the current version is 2.52. A quick look at 2.52 shows that it has a new > config.sub (timestamp=2001-08-13) that resolves the Alphaev6 issue. The > config.sub you are distributing does not match the one that installs with the > 2.52 version of autoconf. Maybe you just need to distribute the new config.sub? > > Thanks - Justus > -- > Think to the future...and beyond. > /** Justus J. Addiss Email: [EMAIL PROTECTED] **\ > <*** 3M Health Information Systems Phone: 203-949-0303 x6414 ***> > \** Wallingford, CT 06492 FAX: 203-949-6455 or 6331 **/ > > > > |--------+-------------------------> > | | Patrick Powell | > | | <papowell@astar| > | | t.com> | > | | | > | | 02/20/2002 | > | | 21:21 | > | | | > |--------+-------------------------> > >----------------------------------------------------------------------------| > | | > | To: Justus J. Addiss/HI-Healthinfo/3M/US@3M-Corporate | > | cc: | > | Subject: Re: LPRng: Configure/Compile bugs in LPRng-3.8.5 and | > | ifhp-3.5.3 | > >----------------------------------------------------------------------------| > > > > > > can you get the 'configure' folks to update the configure stuff? > > This would help me tremendously... > > Patrick > > > > > ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
