autobuild of automake project fails due to --no-create

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 ?

Peter

autobuild of automake project fails due to --no-create

On Tuesday 07 December 2010 15:59:49 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 ?

Nevermind, the bugs are in the log4cpp config macros...

Peter

autobuild of automake project fails due to --no-create

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 ...

Sylvain

autobuild of automake project fails due to --no-create

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

autobuild of automake project fails due to --no-create

On 12/08/2010 11:32 PM, Peter Soetens wrote:
> 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.
Ah ... Sorry. I thought it was fixed and therefore held the update.

Just published autobuild 1.5.30

> 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.
--no-create is disabled by default now.

autobuild of automake project fails due to --no-create

On Thu, Dec 9, 2010 at 10:42 AM, Sylvain Joyeux <sylvain [dot] joyeux [..] ...> wrote:
> On 12/08/2010 11:32 PM, Peter Soetens wrote:
>>
>> 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.
>
> Ah ... Sorry. I thought it was fixed and therefore held the update.
>
> Just published autobuild 1.5.30
>
>> 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.
>
> --no-create is disabled by default now.

How can existing users upgrade to this version ?

In the meantime, I have fixed the configure.in macros such that the
custom macro is generated with the config.status file. So it will also
work with older autobuild versions.

Peter
--
Orocos-Dev mailing list
Orocos-Dev [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev

autobuild of automake project fails due to --no-create

On 12/09/2010 06:07 PM, Peter Soetens wrote:
> On Thu, Dec 9, 2010 at 10:42 AM, Sylvain Joyeux<sylvain [dot] joyeux [..] ...> wrote:
>> On 12/08/2010 11:32 PM, Peter Soetens wrote:
>>>
>>> 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.
>>
>> Ah ... Sorry. I thought it was fixed and therefore held the update.
>>
>> Just published autobuild 1.5.30
>>
>>> 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.
>>
>> --no-create is disabled by default now.
>
> How can existing users upgrade to this version ?
If they are using the osdeps system, "autoproj update" will upgrade them

Otherwise, they would have to do

gem install autobuild

--
Sylvain Joyeux (Dr. Ing.)
Researcher - Space and Security Robotics
DFKI Robotics Innovation Center
Bremen, Robert-Hooke-Straße 5, 28359 Bremen, Germany

Phone: +49 421 218-64136
Fax: +49 421 218-64150
Email: sylvain [dot] joyeux [..] ...

Weitere Informationen: http://www.dfki.de
--
Orocos-Dev mailing list
Orocos-Dev [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev

autobuild of automake project fails due to --no-create

Hi,

maybe it's an stupid thing, but as you are maintaining modified a log4cpp
version, and orocos is based in cmake, maybe it could be a good idea to
migrate log4cpp to cmake and don't spend any time modifiying autotools code.

I have looked the Makefile.am and it seems a simple thing.

Just an idea ....

Regards,

Leo

autobuild of automake project fails due to --no-create

On 10/12/2010, at 23:57 , Leopold Palomo-Avellaneda wrote:

> Hi,
>
> maybe it's an stupid thing, but as you are maintaining modified a log4cpp
> version, and orocos is based in cmake, maybe it could be a good idea to
> migrate log4cpp to cmake and don't spend any time modifiying autotools code.
>
> I have looked the Makefile.am and it seems a simple thing.
>
> Just an idea ....

They've already done this at the log4cpp project, however, when I built it with our system, the resulting log4cpp libraries caused seg-faults in our code. I did not get around to determining why. It's on my task list with one of my customers to figure this out in January. I will post CMake-happy log4cpp patches then, if someone hasn't deal with this by then ...
S

autobuild of automake project fails due to --no-create

A Divendres 10 Desembre 2010, S Roderick va escriure:
> On 10/12/2010, at 23:57 , Leopold Palomo-Avellaneda wrote:
> > Hi,
> >
> > maybe it's an stupid thing, but as you are maintaining modified a log4cpp
> > version, and orocos is based in cmake, maybe it could be a good idea to
> > migrate log4cpp to cmake and don't spend any time modifiying autotools
> > code.
> >
> > I have looked the Makefile.am and it seems a simple thing.
> >
> > Just an idea ....
>
> They've already done this at the log4cpp project,

who? I have not seen any CMakeLists in gitorious ...

> however, when I built it
> with our system, the resulting log4cpp libraries caused seg-faults in our
> code. I did not get around to determining why. It's on my task list with
> one of my customers to figure this out in January. I will post CMake-happy
> log4cpp patches then, if someone hasn't deal with this by then ... S

if you don't have any problem, send me the patch that I will review it.

Regards,

Leo

autobuild of automake project fails due to --no-create

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