[lxc-devel] [PATCH 1/4] lxc-init: use lxc_mainloop

[Daniel Lezcano]

On 12/05/2011 12:43 PM, Greg Kurz wrote:
> On Sun, 2011-12-04 at 11:33 +0100, Daniel Lezcano wrote:
>> On 11/08/2011 12:49 PM, Greg Kurz wrote:
>>> The goal here is to be able to multiplex several event sources in
>>> lxc-init. It will be a lot easier to add I/O driven features: for
>>> example, a rexec-like service to start extra commands in a
>>> container.
>>>
>>> Signed-off-by: Greg Kurz <gkurz at fr.ibm.com>
>>> Signed-off-by: Cedric Le Goater <clg at fr.ibm.com>
>>> ---
>> Hi Greg,
>>
>> the compilation fails with:
>>
>> gcc -I../../src -DLXCROOTFSMOUNT=\"/usr/lib/lxc/rootfs\"
>> -DLXCPATH=\"/var/lib/lxc\" -DLXCINITDIR=\"/usr/lib/lxc\" -g -O2 -Wall
>> -lutil  -o lxc-init lxc_init.o liblxc.so -lcap
>> /usr/bin/ld: lxc_init.o: undefined reference to symbol
>> 'login_tty@@GLIBC_2.0'
>> /usr/bin/ld: note: 'login_tty@@GLIBC_2.0' is defined in DSO
>> /usr/lib/gcc/i686-linux-gnu/4.6.1/../../../i386-linux-gnu/libutil.so so
>> try adding it to the linker command line
>> /usr/lib/gcc/i686-linux-gnu/4.6.1/../../../i386-linux-gnu/libutil.so:
>> could not read symbols: Invalid operation
>> collect2: ld returned 1 exit status
>>
> Daniel,
>
> Thanks for giving a try to lxc-rexec. I do have a warning about
> login_tty() when compiling on fedora but not a link issue like what you
> get. I suggest we first kill the real culprit src/lxc/utmp.h, so that we
> can *really* include the utmp.h system header. Is that okay for you ? Do
> you want me to respin a new patchset ?

AFAICS, you already killed the utmp.h with the rexec V2 patchset.
Maybe the liblxc is not linked with libutil ?