Hi Frank! Am 2013-10-09 11:33, schrieb Frank Mehnert: > Peter, > > On Tuesday 08 October 2013 13:39:20 Peter Gsellmann wrote: >> error messages are: >> undefined reference to `dlopen' ( and other functions of libdl ) >> /home/peter/VirtualBox/vbox/src/VBox/Runtime/r3/xml.cpp:402: undefined >> reference to `xmlSetExternalEntityLoader' ( and other functions of libxml2 >> ) >> >> The failing command: >> @g++ '-Wl,-rpath,$(VBOX_ORIGIN)' -static >> -Wl,-z,noexecstack -Wl,--as-needed -Wl,-z,origin -m64 -o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/vbox-img >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/vbox-img. >> o /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/VD.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/VDVfs. >> o /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/VDI.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/VMDK.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/VHD.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/DMG.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/Parall >> els.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/ISCSI. >> o /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/RAW.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/QED.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/QCOW.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/VHDX.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/VCICac >> he.o >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/obj/vbox-img/dt/VDIfVf >> s.o /home/peter/VirtualBox/vbox/out/linux.amd64/release/lib/RuntimeR3.a >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/lib/VBox-liblzf.a -lz >> -lcrypt >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/lib/RuntimeR3.a >> /home/peter/VirtualBox/vbox/out/linux.amd64/release/lib/VBox-liblzf.a >> -lz -lcrypt -lpthread -lm -lrt -ldl -lssl -lcrypto >> >> >> both libraries are present as static and dynamic, 32 and 64: >> /usr/lib/libdl.a /usr/lib64/libdl.a /usr/lib/libdl-2.15.so >> /usr/lib64/libdl-2.15.so and associated softlinks >> >> I can successfully compile 48851 and 4.2.18, installed also packages >> libvpx-devel, libxml2-static, openssl-static >> >> Guessing: -static > > which SVN version did you try? I think we already fixed this problem, > can you try to update your tree and compile again? It is/was 48962. This is what i get with svn up -r HEAD , even today. I tried a bisection between last official release and HEAD and it stopped at 48852; BTW: the log message of 48852 shows someone has checked in in full awareness of breaking something. My suspicion: the set of available static variants of some libraries is different on my Fedora 17/18 then on the actual developer machine. For example: i have only the 64bit static libxml2-library no 32bit.
>> How can i fetch the SVN version corresponding do Release 4.2.18_88780 ? >> Obviously not by svn update -r88780 >> Also not by svn switch http://www.virtualbox.org/svn/vbox/tags/88780 >> Also svn log | grep 88780 doesnt reveal. >> Is there a public document of the relation of the Build-number to >> SVN-number ? > > We don't publish the SVN repository for the branch releases, too much Not even a small text file with the last build number in root-directory? > maintenance effort, sorry. Just use the tarball which is part of every > release. This means, eventually the release tarball is patched and eventually not existent in the SVN repository? So another question: if my intention is to deliver a patch upstream is it better to base it on SVN or on tarball? ( svn diff is a much simpler way to produce a patch ) Grüße, Peter _______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
