From: Robert S. <ro...@sc...> - 2002-01-22 06:56:40
|
Hi, I just gave the CVS version of plplot a try. This is mostly a SuSE 7.2 system. If I understand the instructions correctly I have to run autoconf in the cf/ directory to generate the configure script. But autoconf breaks here: ----------8<----------8<----------8<----------8<---------- callisto:/usr/local/plplot/cf # autoconf /usr/bin/m4: configure.in: 362: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 365: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 368: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 371: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 374: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 377: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 380: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 383: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 386: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 389: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 392: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 395: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 400: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 403: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 406: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 409: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 412: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 415: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 418: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 421: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 424: Non-numeric argument to built-in `divert' /usr/bin/m4: configure.in: 474: Bad regular expression `[[[\([[`""]]\)]]]': Unmatched ) or \) [configure.in:474[: error: [[[back quotes and double quotes should not be escaped in: [[$as_me:__oline__: result: $prefix]]]]]] ]/usr/bin/m4: configure.in: 474: ERROR: Recursion limit of 1024 exceeded, use -L<N> to change it callisto:/usr/local/plplot/cf # ----------8<----------8<----------8<----------8<---------- automake: Version 1.5 autoconf: Version 2.52 aclocal: Version 1.5 m4: Version 1.4o Robert -- +--------------------------------------------------------+ | Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de | | Pengutronix - Linux Solutions for Science and Industry | | Braunschweiger Str. 79, 31134 Hildesheim, Germany | | Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4 | +--------------------------------------------------------+ |
From: Maurice L. <mj...@ga...> - 2002-01-22 07:59:36
|
Robert Schwebel writes: > Hi, > > I just gave the CVS version of plplot a try. This is mostly a SuSE 7.2 > system. > > If I understand the instructions correctly I have to run autoconf in the > cf/ directory to generate the configure script. But autoconf breaks here: > > ----------8<----------8<----------8<----------8<---------- > callisto:/usr/local/plplot/cf # autoconf > /usr/bin/m4: configure.in: 362: Non-numeric argument to built-in `divert' > ... > automake: Version 1.5 > autoconf: Version 2.52 > aclocal: Version 1.5 > m4: Version 1.4o Wow, big changes in autoconf-land. On my RedHat 7.1 I have ged$ autoconf --version Autoconf version 2.13 The bit of plplot code that's implicated is pretty ancient. So I figure it's a compatibility problem with the latest autoconf.. checking it out, thanks. BTW I noticed the autoconf 2.52 .m4 files look really great in xemacs font-lock mode (for the first time ever IIRC). -- Maurice LeBrun mj...@ga... |
From: Maurice L. <mj...@ga...> - 2002-01-22 08:08:43
|
Robert Schwebel writes: > automake: Version 1.5 > autoconf: Version 2.52 > aclocal: Version 1.5 > m4: Version 1.4o Please let me know what you get back from "m4 --version". E.g. on my system: $ m4 --version GNU m4 1.4.1 -- Maurice LeBrun mj...@ga... |
From: Maurice L. <mj...@ga...> - 2002-01-22 08:22:03
|
Maurice LeBrun writes: > Robert Schwebel writes: > > automake: Version 1.5 > > autoconf: Version 2.52 > > aclocal: Version 1.5 > > m4: Version 1.4o > > Please let me know what you get back from "m4 --version". E.g. on my system: > > $ m4 --version > GNU m4 1.4.1 Well, probably doesn't matter. I've verified the problem on my system when using autoconf 2.52. Shouldn't take long to find the cause (famous last words :). -- Maurice LeBrun mj...@ga... |
From: Robert S. <ro...@sc...> - 2002-01-22 08:28:12
|
On Tue, 22 Jan 2002, Maurice LeBrun wrote: > Please let me know what you get back from "m4 --version". E.g. on my system: > > $ m4 --version > GNU m4 1.4.1 callisto:/usr/local/rrdtool-1.0.33 # m4 --version GNU m4 1.4o Robert -- +--------------------------------------------------------+ | Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de | | Pengutronix - Linux Solutions for Science and Industry | | Braunschweiger Str. 79, 31134 Hildesheim, Germany | | Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4 | +--------------------------------------------------------+ |
From: Alan W. I. <ir...@be...> - 2002-01-22 09:03:17
|
On Tue, 22 Jan 2002, Robert Schwebel wrote: > automake: Version 1.5 > autoconf: Version 2.52 > aclocal: Version 1.5 > m4: Version 1.4o Robert, one possible workaround is your SuSe distribution may have a compatibility mode for autoconf version 2.1.3. My distribution, Debian woody, is in the middle of a transition from 2.1.3 to 2.5.2. Apparently it is a quite large transition, and it appears I am getting a compatibility mode 2.1.3 if I just specify autoconf on the command line. Obviously SuSe will have some different arrangement, but if there is a compatibility mode for autoconf 2.1.3 please give that a try (especially if Maurice has problems finding a quick fix for 2.5.2). Alan |
From: Maurice L. <mj...@ga...> - 2002-01-22 09:21:45
|
Alan W. Irwin writes: > On Tue, 22 Jan 2002, Robert Schwebel wrote: > > > automake: Version 1.5 > > autoconf: Version 2.52 > > aclocal: Version 1.5 > > m4: Version 1.4o > > Robert, one possible workaround is your SuSe distribution may have a > compatibility mode for autoconf version 2.1.3. My distribution, Debian > woody, is in the middle of a transition from 2.1.3 to 2.5.2. Apparently it > is a quite large transition, and it appears I am getting a compatibility > mode 2.1.3 if I just specify autoconf on the command line. Obviously SuSe > will have some different arrangement, but if there is a compatibility mode > for autoconf 2.1.3 please give that a try (especially if Maurice has problems > finding a quick fix for 2.5.2). Well so far I've: found and fixed the original bug found and fixed a second bug found the third and if I don't reach the end soon I'm quitting.. -- Maurice LeBrun mj...@ga... |
From: Robert S. <ro...@sc...> - 2002-01-22 10:11:27
|
Alan, On Tue, 22 Jan 2002, Alan W. Irwin wrote: > Robert, one possible workaround is your SuSe distribution may have a > compatibility mode for autoconf version 2.1.3. Argh, this comes from every package wanting another version of the autotools. I've had a more detailed look at it again and the distro has originally 2.13 installed (2.52 came from /usr/local). With this version it works. But fine if I've discovered a bug, anyway :-) Robert -- +--------------------------------------------------------+ | Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de | | Pengutronix - Linux Solutions for Science and Industry | | Braunschweiger Str. 79, 31134 Hildesheim, Germany | | Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4 | +--------------------------------------------------------+ |
From: Maurice L. <mj...@ga...> - 2002-01-22 11:39:55
|
Robert Schwebel writes: > Alan, > > On Tue, 22 Jan 2002, Alan W. Irwin wrote: > > Robert, one possible workaround is your SuSe distribution may have a > > compatibility mode for autoconf version 2.1.3. > > Argh, this comes from every package wanting another version of the > autotools. I've had a more detailed look at it again and the distro has > originally 2.13 installed (2.52 came from /usr/local). With this version > it works. But fine if I've discovered a bug, anyway :-) Not bona fide bugs, but compatibility bugs. If 2.13 is in the default distro, then I won't worry too much about it. Of course, 2.52 compatibility will be an issue eventually, and I'd like to fix these problems, but it's starting to look iffy for a quick fix (i.e. before the release). -- Maurice LeBrun mj...@ga... |
From: Robert S. <ro...@sc...> - 2002-01-23 08:44:00
|
On Tue, 22 Jan 2002, Maurice LeBrun wrote: > Not bona fide bugs, but compatibility bugs. If 2.13 is in the default > distro, then I won't worry too much about it. Of course, 2.52 > compatibility will be an issue eventually, and I'd like to fix these > problems, but it's starting to look iffy for a quick fix (i.e. before > the release). Ok - could you place a hint to the documentation in cf/ which version of the autotools have been tested? Robert -- +--------------------------------------------------------+ | Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de | | Pengutronix - Linux Solutions for Science and Industry | | Braunschweiger Str. 79, 31134 Hildesheim, Germany | | Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4 | +--------------------------------------------------------+ |
From: Maurice L. <mj...@ga...> - 2002-01-22 12:06:25
|
Maurice LeBrun writes: > Robert Schwebel writes: > > Alan, > > > > On Tue, 22 Jan 2002, Alan W. Irwin wrote: > > > Robert, one possible workaround is your SuSe distribution may have a > > > compatibility mode for autoconf version 2.1.3. > > > > Argh, this comes from every package wanting another version of the > > autotools. I've had a more detailed look at it again and the distro has > > originally 2.13 installed (2.52 came from /usr/local). With this version > > it works. But fine if I've discovered a bug, anyway :-) > > Not bona fide bugs, but compatibility bugs. If 2.13 is in the default distro, > then I won't worry too much about it. Of course, 2.52 compatibility will be > an issue eventually, and I'd like to fix these problems, but it's starting to > look iffy for a quick fix (i.e. before the release). I take it back! I just fixed the 3rd problem and it was the last. I've about had it for tonight but tomorrow will see if these fixes work under 2.31.. I think they probably will. -- Maurice LeBrun mj...@ga... |
From: Maurice L. <mj...@ga...> - 2002-01-22 12:20:00
|
Maurice LeBrun writes: > Maurice LeBrun writes: > > Robert Schwebel writes: > > > Alan, > > > > > > On Tue, 22 Jan 2002, Alan W. Irwin wrote: > > > > Robert, one possible workaround is your SuSe distribution may have a > > > > compatibility mode for autoconf version 2.1.3. > > > > > > Argh, this comes from every package wanting another version of the > > > autotools. I've had a more detailed look at it again and the distro has > > > originally 2.13 installed (2.52 came from /usr/local). With this version > > > it works. But fine if I've discovered a bug, anyway :-) > > > > Not bona fide bugs, but compatibility bugs. If 2.13 is in the default distro, > > then I won't worry too much about it. Of course, 2.52 compatibility will be > > an issue eventually, and I'd like to fix these problems, but it's starting to > > look iffy for a quick fix (i.e. before the release). > > I take it back! I just fixed the 3rd problem and it was the last. I've about > had it for tonight but tomorrow will see if these fixes work under 2.31.. I > think they probably will. Just can't seem to put this problem down and go to bed. It all checks out under 2.13, give it a try.. -- Maurice LeBrun mj...@ga... |
From: Robert S. <ro...@sc...> - 2002-01-23 08:44:02
|
On Tue, 22 Jan 2002, Maurice LeBrun wrote: > Just can't seem to put this problem down and go to bed. It all checks > out under 2.13, give it a try.. Works now! Thanks! Robert -- +--------------------------------------------------------+ | Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de | | Pengutronix - Linux Solutions for Science and Industry | | Braunschweiger Str. 79, 31134 Hildesheim, Germany | | Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4 | +--------------------------------------------------------+ |