Sender: tim AT picard DOT skynet DOT be
Message-ID: <3B1E259D.8024CBC5@falconsoft.be>
Date: Wed, 06 Jun 2001 14:44:13 +0200
From: Tim Van Holder <tim DOT vanholder AT falconsoft DOT be>
Organization: Anubex N.V.
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.16-3 i686)
X-Accept-Language: en, nl-BE, nl
MIME-Version: 1.0
To: Maurice Lombardi <Maurice DOT Lombardi AT ujf-grenoble DOT fr>, djgpp AT delorie DOT com
Subject: Re: problems with autoconf 2.50
References: <3B1D011D DOT 5070500 AT ujf-grenoble DOT fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Maurice Lombardi wrote:
> 
> I have updated to the last autoconf to 2.50 today from simtelnet (acnf250b.zip
> time stamp 20010603), together with the last m4-14b.zip (time stamp 20010526)
> (previously I used acnf213b)
> I use autoconf routinely to recompile gcc 2.953/gpc for new gpc snapshots.
> There is now a failure while gcc-path.sh of gcc2953s2 runs autoconf on
> configure.in in the libiberty directory (of gcc-2.95.3.tar.gz) for missing three
> functions:
> AC_PROG_CC_WORKS
> AC_PROG_CC_G
> AC_PROG_CC_GNU
> With the previous version I see that these functions are used or defined in the
> files
> %djgpp%/share/autoconf/acspecific.m4
>                         autoconf.m4f
>                         autoheader.m4f
> With this version I see them nowhere.
> What to do?  are these functions obsolete ? supply values in config.site ?

Those macros were _internal_ to autoconf (though they were indeed
(incorrectly)
used in many thrid-party macro's and configure.in's).  They are no
longer used
by the current compiler checks.
In most cases where these are used, they're intended to help with
cross-compiling;
for autoconf 2.50 this is less of an issue.  It should be ok to simply
remove
these macros from configure.in.  If that still causes problems, please
send a
message to bug-autoconf AT gnu DOT org.  I'm sure at least one person on that
list will
have adjusted the libiberty config for 2.50.

For other such macro problems, a good start would be to run the
autoupdate script;
this will look for things it knows how to change and updates your
configure.in to
match 2.50's style (it backs up your original to configure.in~, so don't
worry).
But in this case, that won't help (it doesn't even try to update uses of
internal
macros, as users are not supposed to be using them).

-- 
Tim Van Holder - Anubex N.V.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This message was posted using plain text. I do not endorse any
products or services that may be hyperlinked to this message.