[lxc-devel] [PATCH 0/7] Last minute signal stuff (now in separate mails)

[Ferenc Wagner]

Daniel Lezcano <daniel.lezcano at free.fr> writes:

> On 06/07/2010 12:37 PM, Ferenc Wagner wrote:
>
>> there's another failure I get on my work machine (with my original
>> patchset with the above errors corrected):
>>
>> gcc -I../../src -g -O2 -g -Wall -O2 -Wall -Wl,-E -Wl,-rpath -Wl,/usr/lib/lxc  -o lxc-attach lxc_attach.o liblxc.so
>> liblxc.so: undefined reference to `lxc_sync_init'
>> liblxc.so: undefined reference to `lxc_sync_fini_parent'
>> liblxc.so: undefined reference to `lxc_sync_barrier_parent'
>> liblxc.so: undefined reference to `lxc_sync_fini_child'
>> liblxc.so: undefined reference to `lxc_sync_wake_parent'
>> liblxc.so: undefined reference to `lxc_sync_wait_child'
>> liblxc.so: undefined reference to `lxc_sync_fini'
>> liblxc.so: undefined reference to `lxc_sync_barrier_child'
>> collect2: ld returned 1 exit status
>>
>> Have you got an idea what may be wrong here?  I'll continue
>> investigation after lunch.
>
> Do you have a compilation warning ?

No real compilation warning, only this:

make[2]: Entering directory `/build/wferi-lxc_0.6.6~gitf814275a-1-i386-T7QsnO/lxc-0.6.6~gitf814275a/src'
cd .. && /bin/sh /build/wferi-lxc_0.6.6~gitf814275a-1-i386-T7QsnO/lxc-0.6.6~gitf814275a/config/missing --run autoheader
/build/wferi-lxc_0.6.6~gitf814275a-1-i386-T7QsnO/lxc-0.6.6~gitf814275a/config/missing: line 54: autoheader: command not found
WARNING: `autoheader' is missing on your system.  You should only need it if
         you modified `acconfig.h' or `configure.ac'.  You might want
         to install the `Autoconf' and `GNU m4' packages.  Grab them
         from any GNU archive site.
touch: cannot touch `[src/config.h].in': No such file or directory
rm -f stamp-h1
touch config.h.in

It's probably some unfortunate interaction with the Debian build system.
If I rerun autogen.sh on the build system (the source is prepared on
another system with a different automake version), the build succeeds.

This didn't cause problems before.  Now I switched to treating the git
checkout as the "original source", and the problem disappeared.  Looks
like it's nothing to worry about, after all.
-- 
Thanks,
Feri.