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