Re: KDE 3.5.5 autoconf errors

[Matthew Woehlke]

(The autoconf side of this thread seems resolved, please drop them when 
replying unless you have a reason not to.)

Ralf Wildenhues wrote:
> * Matthew Woehlke wrote on Thu, Jan 11, 2007 at 01:01:09AM CET:
> > Actually, looking in e.g. 
> > http://websvn.kde.org/branches/KDE/3.5/kdelibs/configure.in.in?rev=526641&view=markup 
> > I see "AC_INIT(acinclude.m4)". I'm not sure what this means...?
>
> That's the old-style AC_INIT:
> <http://www.gnu.org/software/autoconf/manual/html_node/Obsolete-Macros.html#index-AC_005fINIT-1477>
> as opposed to the new-style AC_INIT:
> <http://www.gnu.org/software/autoconf/manual/html_node/Initializing-configure.html#index-AC_005fINIT-22>
> (where "new" means: supported by all Autoconf versions released in the
> last 5 years).

Ok, thanks...

Hello? KDE people? If autoconf-2.59 is being used for distributions (and 
e.g. considering autoconf-2.59 is still shipping with FC6 isos), maybe 
this should be updated? So that the release-stable tarballs have a 
meaningful address instead of this "bug"?

> > Ok, so autoconf-2.60 on my computer generates the same bad-ness from the 
> > same input. Would this be something about "AC_INIT(acinclude.m4)"? I 
> > looked at that file, but I have no clue what it is doing, so I don't 
> > know what it might be missing to set the bug report address.
>
> Hmm.  I tried to reproduce that, but failed.  With 2.60 and newer, I get
> something like this only:
> | checking foobar.h usability... no
> | checking foobar.h presence... yes
> | configure: WARNING: foobar.h: present but cannot be compiled
> | configure: WARNING: foobar.h:     check for missing prerequisite headers?
> | configure: WARNING: foobar.h: see the Autoconf documentation
> | configure: WARNING: foobar.h:     section "Present But Cannot Be Compiled"
> | configure: WARNING: foobar.h: proceeding with the preprocessor's result
> | configure: WARNING: foobar.h: in the future, the compiler will take precedence
>
> That's worse than providing an address, but when we have none to
> provide, at least it shouldn't be confusing for the user.  So if you
> happen to get an output containing the string AC_PACKAGE_NAME, then
> please post a small example to reproduce it.  Thanks.

Ok, wtf, I swear I found autoconf-2.60... now apparently I don't have 
it, so it is indeed autoconf-2.59 to blame. At any rate, I see the same 
as you on this (different) box with autoconf-2.60.

--
Matthew
You are in a dark room. The only exit is a door to the east.
> GO EAST
There's a door in your way. Maybe you should open it first?