This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: updating binutils/configure


On Wed, Apr 14, 2004 at 12:58:50PM +0200, Maciej W. Rozycki wrote:
> On Wed, 14 Apr 2004, Ben Elliston wrote:
> 
> > I've regenerated binutils/configure using Autoconf 2.59, as has been
> > done for gas.  Is there anything I should be looking for to discover
> > if anything has broken?  autoconf completed without complaint.
> 
>  Running `autoconf -Wall' may show dubious or obsolete constructs.  They 
> need not necesarrily be fixed immediately, but they are worth looking at.
> 
>  Also there's a bug in autoconf 2.59 that was still present in the head a
> few days ago.  Under certain conditions macros that are pulled by
> AC_REQUIRE are expanded too early, possibly leading to certain
> initialization steps being executed after bits that depend on them.  
> Finding them may be difficult, requiring a thorough study of the generated
> script, or sometimes a strange error at the configuration time may be a
> hint.  One example is expanding AC_CANONICAL_BUILD before
> AC_CONFIG_AUX_DIR -- this leads to an attempt to use $ac_config_sub before
> it's initialized.  I've filed a bug report -- no response yet.
> 
>  The bug shouldn't affect binutils -- I've been using autoconf 2.5x
> (including 2.59) for all directories for some time now with no problems (a
> few patches are needed, but not related to the bug).

In that case, would you mind posting these patches?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]