On Thu, 2006-10-12 at 00:05 +0200, Thomas Schwinge wrote: > Hello! > > On Wed, Oct 11, 2006 at 05:48:12AM +0200, Ralf Corsepius wrote: > > On Tue, 2006-10-10 at 16:15 +0200, Thomas Schwinge wrote: > > > On Sun, May 14, 2006 at 06:09:10AM +0200, Ralf Wildenhues wrote: > > > > http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=automake&pr=492 > > > > We were talking about the issue why Automake doesn't emit proper rules > > > for compiling (pre processed) Assembler files (the .S ones) when using > > > `AM_INIT_AUTOMAKE([subdir-objects])'. > > > > > > When using code file `libfoo_a_SOURCES = somewhere/a.S', Automake > > > currently assembles `somewhere/a.S' and puts `a.o' into the current > > > directory (as opposed to `somewhere/a.o'), but when creating `libfoo.a' > > > it wants to add `somewhere/a.o', which will then obviously fail. > > > > This is a known issue (reported > 2 years ago) and supposed to be fixed > > in automake-cvs (me and somebody else contributed patches to implement > > this behavior) > > Indeed I can confirm that this isn't a problem anymore with the cvs > version of Automake. Someone might close this bug report now. > > > > Unfortunately so far, there had not been a new automake release since > > then. > > Is there already an estimation possible when this will happen?
I wish I know that, at least I am eagerly waiting for it, because we (rtems.org) can't avoid to ship a patched/hacked version of automake, exactly because of this problem :( Ralf
