On Wed, Feb 28, 2007 at 06:48:25AM +0100, Ralf Wildenhues wrote: > A couple more comments. > > * Ben Pfaff wrote on Mon, Feb 26, 2007 at 03:27:42AM CET: > > Content-Description: gnulib diff versus gettext > > --- gettext/build-aux/install-reloc 2006-11-09 06:26:40.000000000 -0800 > > +++ gnulib.relocatable/build-aux/install-reloc 2007-02-19 > > 22:31:39.000000000 -0800 > > > +func_verbose $compile_command -I"$builddir" -I"$srcdir" -I"$config_h_dir" > > -DHAVE_CONFIG_H -DIN_RELOCWRAPPER -DNO_XMALLOC > > -D"INSTALLPREFIX=\"$prefix\"" -D"INSTALLDIR=\"$installdir\"" > > -D"LIBPATHVAR=\"$library_path_var\"" -D"LIBDIRS=$libdirs" > > -D"EXEEXT=\"$exeext\"" "$srcdir"/relocwrapper.c "$srcdir"/progname.c > > "$srcdir"/progreloc.c "$srcdir"/xreadlink.c "$srcdir"/readlink.c > > "$srcdir"/canonicalize-lgpl.c "$srcdir"/allocsa.c "$srcdir"/relocatable.c > > "$srcdir"/setenv.c "$srcdir"/strerror.c "$srcdir"/c-ctype.c -o > > "$destprog.wrapper$exeext" || exit $? > > Do you have some data or experience on how portable it is wrt. the > compiler to list several source files in one compile command? Can > some compiler create intermediate files in the current directory? > Because if yes, that would prevent parallel 'make install'. > Or it could leave behind object files? Sorry, so far I wasn't able > to see easily in which directory this compilation command would be > executed.
And, if $compile_command can be libtool, you'll definitely run into problems, especially on AIX with -export-dynamic. -- albert chin ([EMAIL PROTECTED])
