On 03/24/2012 04:22 AM, Diego Elio Pettenò wrote: > The shared object versioning on the library (soname) was completely wrong, > as the ABI doesn't seem to be guaranteed between one version and the other, > so proposing all of them as .so.0 is very wrong. > > Furthermore you generally want lxc-init static so that you don't have to add > (or have a compatible version of) libcap and liblxc within a container you > want to use lxc-execute with. > > To solve the issue, use the good old libtool to take care of the library > building, and pass -all-static to the lxc-init linking stage. > > Also drop the manual rpath handling, and leave it to libtool to manage. > > Signed-off-by: Diego Elio Pettenò<flamee...@flameeyes.eu> > ---
Hi Diego, I tried to apply your patches but it seems they are not in the right format. They appears correctly in the mailer but it is encoded in the source. Is it possible you fix it and resend ? Thanks -- Daniel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
