RE: variables containing newline characters

[James Willenbring]

Ralf,

Thanks for your latest comments.  I plan to integrate your suggestions into
the Trilinos autotools setup when I get a chance to do so.

Some error on my part or within the Trilinos autotools setup could certainly
be causing this.  I went back to verify that I have the proper line
continuation setup for the arguments I am passing to configure.  I still had
the same problem.  

What type of machine did you attempt to configure and build on?  I have run
into the same problem on 4 different Linux machines.  On one of the machines
I took the same configure arguments and passed them to the current version
of Trilinos that uses AC 2.59 and AM 1.8.2, and that build worked just fine.
Again, for the build that didn't work I am attempting to use AC 2.61 and AM
1.10.

I have also tried to run a script with values that span multiple lines on
Sun, OSX, AIX, and Cygwin.  All four of these machines worked fine using the
version of Trilinos based on AC 2.61 and AM 1.10.

Thanks

Jim

-->verified broken on mel with 2.61/1.10, worked with 2.59/1.8.2

-----Original Message-----
From: 'Ralf Wildenhues' [mailto:address@hidden 
Sent: Wednesday, May 09, 2007 3:26 AM
To: James Willenbring
Cc: address@hidden
Subject: Re: variables containing newline characters

Hello James,

* James Willenbring wrote on Mon, May 07, 2007 at 06:48:20PM CEST:
> 
> "If the failure comes from a substituted value with newlines, then I
> wonder how that could have worked before:  Autoconf before 2.60 wasn't
> able to deal with newlines in substituted values."
> 
> That is surprising because we have used Autoconf 2.59 for years and
> have never had trouble with newlines in substituted values.  Here is
> an example of the arguments we might pass to configure:
[...]

> (Note that the lines that run over the end of a line without a new
> character are one line in my file, but are too long for a line in my
> email editor.)

Well, it's too bad, because exactly this difference is crucial.  If I
take your configure invocation, escape all newlines properly, then I can
configure and execute 'make' successfully, with both using Autoconf
2.59/Automake 1.9.6 as well as Autoconf 2.61/Automake 1.10.  Are you
sure you did not by chance forget to escape one of those newline
characters?

Unrelated, please consider the patch below to fix some minor buglets in
your build system (do not use an absolute path in AC_CONFIG_SRCDIR; drop
unneeded AC_C_CONST; use ACLOCAL_AMFLAGS).

Cheers,
Ralf

--- configure.ac        2006-09-06 19:58:24.000000000 +0200
+++ configure.ac        2007-05-08 19:15:22.000000000 +0200
@@ -53,7 +53,7 @@
 # preferably one that is unlikely to be removed or renamed.
 
 # #np# - file name below
-AC_CONFIG_SRCDIR(/src/Teuchos_LAPACK.hpp)
+AC_CONFIG_SRCDIR([src/Teuchos_LAPACK.hpp])
 
 # Specify directory for auxillary build tools (e.g., install-sh,
 # config.sub, config.guess) and M4 files.
@@ -263,7 +263,6 @@
 fi
 
 # Checks for typedefs, structures, and compiler characteristics.
-AC_C_CONST
 AC_C_INLINE
 
 # ------------------------------------------------------------------------
--- Makefile.am 2006-08-08 19:58:44.000000000 +0200
+++ Makefile.am 2007-05-08 19:13:00.000000000 +0200
@@ -34,7 +34,7 @@
 ## #######################################################################
 ## Aclocal command (rarely used - don't worry about it)
 ## #######################################################################
-ACLOCAL        = aclocal -I config
+ACLOCAL_AMFLAGS = -I config
 
 #
 #       I believe that by switching to AUX_DIR(../../config) one