Re: Autoconf/automake support for preprocessable Fortran

2005-07-27 Thread Alexandre Duret-Lutz
Norman == Norman Gray [EMAIL PROTECTED] writes: [...] Norman (copyright paperwork has been a right pain in the Norman tender bits). Do you mean it's completed, almost done, or yet to do? (I can't see you in the FSF records right now.) Norman This is a preliminary heads-up while I

Re: Autoconf/automake support for preprocessable Fortran

2005-07-27 Thread Norman Gray
Alexandre, On 2005 Jul 27 , at 07.30, Alexandre Duret-Lutz wrote: Norman (copyright paperwork has been a right pain in the Norman tender bits). Do you mean it's completed, almost done, or yet to do? (I can't see you in the FSF records right now.) For me, (b) -- the paperwork should be in

Re: Autoconf/automake support for preprocessable Fortran

2005-07-27 Thread Stepan Kasal
Hello, On Wed, Jul 27, 2005 at 09:11:16AM +0100, Norman Gray wrote: :ext:[EMAIL PROTECTED]:/cvsroot/autoconf :ext:[EMAIL PROTECTED]:/cvsroot/automake right. Stepan Kasal

FYI: a cosmetic change in _AT_CHECK

2005-07-27 Thread Stepan Kasal
Hi, FYI, I committed the following cosmetic change. Stepan 2005-07-27 Stepan Kasal [EMAIL PROTECTED] * lib/autotest/general.m4 (_AT_CHECK): Cosmetic changes to the case $at_status command. Index: lib/autotest/general.m4

FYI: spare pushdef in autotest removed

2005-07-27 Thread Stepan Kasal
Hello, I spotted a place where at_reason was pushed twice, while popped only once. I committed the fix, as attached to this mail. Stepan 2005-07-27 Stepan Kasal [EMAIL PROTECTED] * lib/autotest/general.m4 (_AT_DECIDE_TRACEABLE): The symbol at_reason was pushdef'ed twice while

Re: checking for Berkley db 4.2 -- 4.3 upgrade

2005-07-27 Thread Mike Castle
In article [EMAIL PROTECTED], Sam Steingold [EMAIL PROTECTED] wrote: Berkley db changed prototypes for functions that are struct members. how do I check for that? The official word from Sleepycat is that it's much better to statically link against a known version of BDB that you ship with your

Re: enable/disable configure options for subpackages

2005-07-27 Thread Stepan Kasal
Hello, On Tue, Jul 26, 2005 at 08:55:30PM -0400, Bob Rossi wrote: Does autoconf only pass the explicit arguments down to the lower confurations? or if I have a --enable-shared=no defaulted option, would that work? it passes the options as they were given on the cmdline. So if you don't give

Checking for interpreter libraries

2005-07-27 Thread Tommy Nordgren
I want to find out if there is any autoconf macros for checking for the presence of various scripting language interpreters, and the libraries for extending/embedding them. I want to check for as many as possible and reasonable of the scripting languages supported by Swig, and compile and

Re: Checking for interpreter libraries

2005-07-27 Thread Stepan Kasal
Hello, On Wed, Jul 27, 2005 at 01:21:14PM +0200, Tommy Nordgren wrote: I want to find out if there is any autoconf macros for checking for the presence of various scripting language interpreters, and the libraries for extending/embedding them. I don't think there is an instant support for

Re: checking for Berkley db 4.2 -- 4.3 upgrade

2005-07-27 Thread Sam Steingold
* Mike Castle [EMAIL PROTECTED] [2005-07-26 23:52:30 -0700]: In article [EMAIL PROTECTED], Sam Steingold [EMAIL PROTECTED] wrote: Berkley db changed prototypes for functions that are struct members. how do I check for that? The official word from Sleepycat is that it's much better to

Quieten move-if-change?

2005-07-27 Thread Ben Elliston
move-if-change currently outputs file is unchanged when it does nothing. This adds undue noise in GCC builds. Would it be possible to give it more natural behaviour like mv(1) and output nothing, regardless of whether it moves the file? Ben signature.asc Description: OpenPGP digital

Re: enable/disable configure options for subpackages

2005-07-27 Thread Bob Rossi
On Fri, Jul 15, 2005 at 12:14:44PM +0200, Stepan Kasal wrote: Of course some hacks are possible: 1) fiddle with ac_args before AC_OUTPUT. Of course this solution may easily break with future versions of autoconf. 2) Read what AC_CONFIG_SUBDIRS does (how it propagates the

Re: Mac OS X library path woes / issues / complaints

2005-07-27 Thread Noah Misch
On Tue, Jul 26, 2005 at 02:57:29PM -0400, tom fogal wrote: Of course, the user has the option of specifying LDFLAGS=/opt/local/lib (or whatever) on their ./configure line, and then the configure script finishes. I am of the opinion (and correct me if I'm wrong) that unless the user jumped

Re: Mac OS X library path woes / issues / complaints

2005-07-27 Thread Bob Friesenhahn
On Wed, 27 Jul 2005, Noah Misch wrote: On Tue, Jul 26, 2005 at 02:57:29PM -0400, tom fogal wrote: Of course, the user has the option of specifying LDFLAGS=/opt/local/lib (or whatever) on their ./configure line, and then the configure script finishes. I am of the opinion (and correct me if I'm

Re: [GNU Autoconf 2.59] testsuite: 66 67 68 69 70 71 72 73 failed

2005-07-27 Thread Stepan Kasal
Hello, On Tue, Jul 26, 2005 at 10:45:37AM -0700, Mel Lester Jr. wrote: see attachment thank you for your bug report. These tests failed: 66: fortran.at:52 GNU Fortran 77 67: fortran.at:77 GNU Fortran 68: acfortran.at:12AC_F77_MAIN 69: acfortran.at:13

autoconf-2.59b fails to include correct X11R6 paths in configure scripts on AMD64 systems

2005-07-27 Thread Nelson H. F. Beebe
The latest release of autoconf-2.59b, dated 28-Dec-2005, fails to include correct X11R6 paths in configure scripts on AMD64 systems running GNU/Linux. Those machines support both a 32-bit world and a default 64-bit world. For the latter, libraries are found in directories that end in 64: /lib64,