Re: parallel builds failing in bfd

[Nicholas Wourms <nwourms@myrealbox.com>]

Daniel Jacobowitz wrote:
> On Wed, May 28, 2003 at 03:01:48PM -0700, David Carlton wrote:
> 
>>Every once in a while, when I do a parallel build from the top level,
>>I get a failure that stems from bfd.h being built incorrectly.  Do
>>other people run into this problem?  I'm not at all familiar with
>>bfd's Makefile.in, so I don't know offhand what might be causing this
>>problem.
> 
> 
> It's an autoconf 2.13 bug unfortunately.  It will be fixed after the
> 2.5x transition, which is starting to gain a little momentum now.
> 

BTW, are there any plans to transition to Automake-1.7.X & 
Libtool-1.5.X, now that they have stabilized?  It sure would be nice to 
finally have a consolidated, streamlined build without all this leftover 
Cygnus tree building crap.  Yes, I dare say to ditch the current cruft 
which is polluting Makefile.in's.  There should be no reason why the 
entire configury can't happen in one shot.  Yes, I am aware that it must 
support mixed trees, which is why one would put conditional guards 
around subproject macros, running them only iff said subproject 
directory is present in the source tree.  It would save time and, for 
some, resources [since repeatedly calling the Autom4te/Automake perl 
functions (when checking for autoheader, etc.) tends to hog resources]. 
  Not to mention the fact that {in-tree,parallel,distcc} building is 
*much* easier to implement and less prone to break with the latest 
versions of these tools.  The biggest advantage, by far, would be to 
bring subproject Makefile templates inline with some sort of general 
standard, which is generally enforced by the current Automake/Autoconf 
macros (whereas previous versions of autoconf/automake were rather lax).

Just my $0.02...  Feel free to disagree :-)

Cheers,
Nicholas