On 2/21/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Hi Christopher, > > * Christopher Hulbert wrote on Tue, Feb 21, 2006 at 03:15:42PM CET: > > Attached is the test outputs. > > Thanks. Unfortunately, I was not precise enough: > Please configure Libtool with the Portland compilers, so that they are > tested. E.g., like > ./configure CC=pgcc CXX=pgCC F77=pgf77 FC=pgf95
duh, I feel braindead :)! > > Sorry about that. :-( > > Please note that the tarball you sent did not contain > tests/testsuite.log. It appears make_check_local was misplaced: there > is a duplicate, packed copy of make_check in there. It'd be great if > you could send the testsuite.log file as well, and the other output with > the above configuration. Yeah, got an error that I couldn't append to a compressed tar archive so that didn't make it :/. Not that it mattered since I used the wrong C compiler. > > But also see below: > > > I looked at the failure for fcdemo. It > > looks like autoconf's AC_FC_LIBRARY_LDFLAGS is not picking up the PGI > > libraries because they are wrapped in single quotes, i.e. > > '-Lc:\Program Files\PGI/nt86/6.0/lib'. > > Hmpf. That'll be difficult to get both fixed in _AC_PROG_FC_V_OUTPUT > and also all the way through Autoconf and Libtool so the embedded space > isn't killed (or the path broken in two arguments). Not sure what's going on here. I use the AC_FC_LIBRARY_LDFLAGS in my configure.ac and I don't get that problem. libtool's configure must be quoting each of these arguments??? I should note that I had to patch fortran.m4 (a long time ago) to handle a case where the library was butted up against a single quote such as 'blah blah -lm'. I thought I sent that info to the autoconf list a while ago??? > > Probably it would currently be best (for Fortran users) to > - either install the compiler under a path not containing spaces, or > - create a config.site file for this compiler/system combination, with > ac_cv_fc_libs pre-seeded with the right flags for Fortran, and > alternate non-space path representations; on your system, that would > be something like > > ac_cv_fc_libs='-Lc:/Progra~1/PGI/nt86/6.0/mingw/lib > -Lc:/Progra~1/PGI/nt86/6.0/mingw/mingw32/lib > -Lc:/Progra~1/PGI/nt86/6.0/mingw/lib/gcc-lib/mingw32/2.95.3-5 > -Lc:/Progra~1/PGI/nt86/6.0/lib -lpgf90 -lpgf90_rpm1 -lpgf902 -lpgf90rtl > -lpgftnrtl -lpgc -lmingw32 -lgcc -lmoldname -lmsvcrt -luser32 -lkernel32 > -ladvapi32 -lshell32' > > all on one line. See the Autoconf docs for config.site files. > - Or do both of the above. > > Also I think we need to stick `-Mnomain' in Fortran archive_cmds > otherwise fcdemo will fail again. Well, that depends on how you link. I link my C code against the archived fortran code separately so without forcing automake to use LD=$(FC), it uses the C compiler, so I don't need -Mnomain (hence the use of AC_FC_LIBRARY_LDFLAGS). > > Cheers, > Ralf > > > On 2/18/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > > > > The patch is ok, could you be bothered to run the testsuite once, > > > verbosely > > > make check VERBOSE=x TESTSUITE_FLAGS=-V > > > make check-local > > > > > > and send (packed) the output and tests/testsuite.log, so we could hash > > > out any other simple issues for decent support? >