I'm posting this to two mailing lists because of the environment. # /home/moleque/VirtualBox-2.0.0/./configure Checking for environment: Determined build machine: freebsd.amd64, target machine: freebsd.amd64, OK. Checking for kBuild: found, OK. Checking for gcc: found version 4.2.1, OK. Checking for as86: found version 0.16.17, OK. Checking for bcc: found version 0.16.17, OK. Checking for iasl: found version 20070320, OK. Checking for xslt: found, OK. Checking for pthread: found, OK. /libexec/ld-elf.so.1: Shared object "libc.so.6" not found, required by "kmk_sed" Checking for libxml2: /libexec/ld-elf.so.1: Shared object "libc.so.6" not found, required by "kmk_sed"
xml2 not found at -L/usr/local/lib -lxml2 -lpthread or xml2 headers not found Check the file /usr/home/moleque/sdk/bindings/configure.log for detailed error information. ===> Installing for libxml2-2.6.32 ===> libxml2-2.6.32 depends on executable: pkg-config - found ===> Generating temporary packing list ===> Checking if textproc/libxml2 already installed ===> libxml2-2.6.32 is already installed You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of textproc/libxml2 without deleting it first, set the variable "FORCE_PKG_REGISTER" in your environment or the "make install" command line. *** Error code 1 Stop in /usr/ports/textproc/libxml2. There seems to be a conflict here. I also want to post a patch sent to me for bin86. I don't know the original source but would like to see it added. It will help x86 builds on amd64 hosts. I was asked to share it. from:walt ([EMAIL PROTECTED]) "Desmond Chapman wrote: > Thanks for offering the help. How do I apply the patch that you sent? My pleasure. The 'patch' program has a zillion confusing options because it has morphed many times from its original incarnation, but the '-p' flag is the main one to understand. I didn't make the patch I posted, but this is how I would have done it: #cd /tmp (or wherever you prefer) #tar -xvzf /path/to/bin86-0.16.17.tar.gz #cd bin86-0.16.17 (customary to generate patches from the top directory) #cp ld/x86_aout.h ld/x86_aout.h.orig (the usual naming, but arbitrary) #vi ld/x86_aout.h (make the needed changes and save them) #diff -u ld/x86_aout.h.orig ld/x86_aout.h > /tmp/mynewpatch Now, look at the beginning of mynewpatch: --- ld/x86_aout.h.orig 2003-01-28 17:17:14.000000000 -0500 +++ ld/x86_aout.h 2005-05-07 22:40:05.000000000 -0400 That's important because it tells you I made the patch from the top of the source directory, but that's a tradition that not everyone obeys. Applying a patch is the mirror image of making a patch, so you need to know where to be in the source directory before you apply it. Hence, the -p flag is critical. This is how I would apply this particular patch: #cd /tmp (see the mirror image process already?) #tar -xvzf /path/to/bin86-0.16.17.tar.gz #cd bin86-0.16.17 #patch -p0 < /path/to/mynewpatch (there's that -p flag at last!) That -p0 tells 'patch' that you are now in the same directory where the patch was first generated. If you instead chose to be in the /tmp/bin86-0.16.17/ld directory when applying the patch, you would use -p1 instead of -p0. That's just a clue. You need to read the patch manpage for the rest! Please do pass this post on to anyone/everyone you think needs help. That's what opensource is all about. Let me know if you're still confused." On my own behalf, forgive me if I am a bit confusing; but, I am diving head first into a development environment I have little experience with. How do I solve the xml2 conflict listed above the patch? _________________________________________________________________ Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008_______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"