Hi Tim, * Tim Rice wrote on Sun, Oct 30, 2005 at 11:19:30AM CET: > On Sun, 30 Oct 2005, Ralf Wildenhues wrote: > > * Tim Rice wrote on Sun, Oct 30, 2005 at 02:34:18AM CET: > > > > > > --- automake-1.9.6/automake.in.old 2005-06-30 14:17:13.000000000 > > > -0700 > > > +++ automake-1.9.6/automake.in 2005-10-29 18:31:51.565961323 -0700 > > > @@ -691,7 +691,6 @@ > > > 'compile' => '$(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) > > > $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS)', > > > 'compiler' => 'CXXCOMPILE', > > > 'compile_flag' => '-c', > > > - 'output_flag' => '-o', > > > 'libtool_tag' => 'CXX', > > > 'lder' => 'CXXLD', > > > 'ld' => '$(CXX)', > > > > No. :) > > > > Above workaround works only because > > - we do not use subdir-objects; in fact, we do not use subdirs at all, > > - none of the non-libtool objects (i.e., the `.o' ones) use per-target > > flags > > It seems strange that automake's COMPILE section has no 'output_flag' => '-o', > but the CXXCOMPILE does.
Well, Automake currently has its `compile' machinery hard-wired for C. Look where output_flag gets used, they specifically check the language for C. Also, look at automake/m4/minuso.m4 to find out that it needs adjusting for non-C as well. The `compile' script needs adjustment, too, should a solution for it use this as well. I'm not saying it can't be done; all I'm saying is it's a bit more work to solve this than above patch. Also please note that you might break things in users' configure.ac in that they might not expect $CXX to end up containing `path/to/compile $CXX'. (Most people don't expect it for C code either, though.) This really is an Automake question. If you are brave to work on this, you should send your patches to [EMAIL PROTECTED] :) Cheers, Ralf _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
