On 04/01/13 09:52, Tobias Gasser wrote: > Am 03.01.2013 23:23, schrieb Armin K.: >> On 01/03/2013 11:03 PM, Tobias Gasser wrote: >>> >>> any hint what else i can try to build 1.0.1? >>> >>> >>> thanks for any help >>> tobias >>> >> >> As you see, libtirpc is not yet ready to take over RPC stuff. That's why >> Glibc developers introduced --enable-obsolete-rpc switch if an user >> wants to enable RPC API/ABI once again. It is not used in LFS, but few >> of us asked for Glibc's RPC interface to be re-enabled. No one had luck >> with convincing the devs. :P > > libvirt 0.9.3 compiles fine with the glibc / tirpc mixup > > the new 1.0.1 fails (maybe i should try 1.0.0) > >> You can try (again) convincing them lfs-dev mailing list to enable >> Glibc's RPC interface by default (Good luck with that) :-) > > maybe that's why libvirt was dropped from the book > > as 0.9.3 can be compiled with tirpc and even the 1.0.1 configure > checks for libtirpc, i guess the libvirt people are to be blamed. > > meanwhile all packages where i need rpc switched from sunrpc to tirpc, > thus for me the book is ok. > > until a patch from a distro is available, or a fixed version is > published i'll go on with the 0.9.3 > > as google was no help, i just wanted to ask wether someone here has a > solution... > > tobias >
FYI, I've built libvirt 1.0.0 with no issues as per my previous email. It is on a 64bit (x86_64) system. I'm wondering if its a environment/architecture issue? Regards, Wayne. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
