On Tuesday 07 December 2010 16:16:05 Sylvain Joyeux wrote:
> On 12/07/2010 03:59 PM, Peter Soetens wrote:
> > When trying to fit log4cpp in my layout, this:
> >
> > autotools_package "log4cpp"
> >
> > does not work because it invokes configure with the --no-create flag. The
> > log4cpp configure step complains with:
> >
> > ...
> > checking for dot... /usr/bin/dot
> > configure: creating log4cpp-config.in
> > configure: creating log4cpp.pc.in
> > configure: creating ./config.status
> > creating include/log4cpp/config.h - prefix LOG4CPP for include/config.h
> > defines configure: error: input file does not exist, skip
> > generating include/log4cpp/config.h
> >
> > and all stops.
> >
> > Why is --no-create given, and how can we override that ?
>
> I have to admit that I don't know why --no-create is given at configure
> time and ./config.status runs at build time ...
>
> This is from autobuild's very beginning, so the reason is probably
> somewhere in a CVS repository somewhere at LAAS. It worked fine for all
> that time, so I really have no clue.
>
> Anyway, I'm testing a small patch to autobuild that will disable this
> behaviour by default (since I have no recollection as to why it is so
> ... it is probably lost in old CVS history somewhere at LAAS), and allow
> to get it back by setting a flag in the autobuild file.

I'm in a kind-of urgent need for this patch. I believed I solved the problem,
but the config.status step is not generating one of the config.h files, so it's
still broken.

I have tarballs on the website of the 2.2.0 release, but an 'autoproj build'
will fail immediately on the log4cpp build (it's in the manifest file). If
there is a quick hack on disabling this --no-create flag, I'll be happy to
know.

I'm out of office the next two days, so I'll pull the release again from the
website. And try to re-release next monday, or this friday if I'm back early.

>
> Do you have an idea as to *why* it fails ? Running ./configure
> --no-create is fairly normal procedure in autotools. It is even done by
> automake itself when it detects that a reconfiguration is needed ...

Broken config.h generation by log4cpp. They worked around config.status, so that
file will eventually run out-of sync.

Peter

On Tuesday 07 December 2010 16:16:05 Sylvain Joyeux wrote:
> On 12/07/2010 03:59 PM, Peter Soetens wrote:
> > When trying to fit log4cpp in my layout, this:
> >
> > autotools_package "log4cpp"
> >
> > does not work because it invokes configure with the --no-create flag. The
> > log4cpp configure step complains with:
> >
> > ...
> > checking for dot... /usr/bin/dot
> > configure: creating log4cpp-config.in
> > configure: creating log4cpp.pc.in
> > configure: creating ./config.status
> > creating include/log4cpp/config.h - prefix LOG4CPP for include/config.h
> > defines configure: error: input file does not exist, skip
> > generating include/log4cpp/config.h
> >
> > and all stops.
> >
> > Why is --no-create given, and how can we override that ?
>
> I have to admit that I don't know why --no-create is given at configure
> time and ./config.status runs at build time ...
>
> This is from autobuild's very beginning, so the reason is probably
> somewhere in a CVS repository somewhere at LAAS. It worked fine for all
> that time, so I really have no clue.
>
> Anyway, I'm testing a small patch to autobuild that will disable this
> behaviour by default (since I have no recollection as to why it is so
> ... it is probably lost in old CVS history somewhere at LAAS), and allow
> to get it back by setting a flag in the autobuild file.
>
> Do you have an idea as to *why* it fails ? Running ./configure
> --no-create is fairly normal procedure in autotools. It is even done by
> automake itself when it detects that a reconfiguration is needed ...

One of the *custom* m4 macro's the log4cpp people wrote assumed that a certain
config.h file was always generated, ruling out the use of --no-create. They also
assumed no build dir was used. I fixed that macro and pushed everything on
master.

I also added a manifest.xml to log4cpp.

Peter