From owner-freebsd-questions@FreeBSD.ORG Thu Oct 2 07:45:15 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF9F51065686 for ; Thu, 2 Oct 2008 07:45:14 +0000 (UTC) (envelope-from que_deseja@hotmail.com) Received: from blu0-omc4-s32.blu0.hotmail.com (blu0-omc4-s32.blu0.hotmail.com [65.55.111.171]) by mx1.freebsd.org (Postfix) with ESMTP id A74548FC1C for ; Thu, 2 Oct 2008 07:45:14 +0000 (UTC) (envelope-from que_deseja@hotmail.com) Received: from BLU126-W14 ([65.55.111.137]) by blu0-omc4-s32.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 2 Oct 2008 00:45:14 -0700 Message-ID: X-Originating-IP: [98.192.204.41] From: Desmond Chapman To: , Date: Thu, 2 Oct 2008 07:45:14 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 02 Oct 2008 07:45:14.0222 (UTC) FILETIME=[CE3C40E0:01C92462] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: vbox building and freebsd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2008 07:45:15 -0000 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=2C target= machine: freebsd.amd64=2C OK. Checking for kBuild: found=2C OK. Checking for gcc: found version 4.2.1=2C OK. Checking for as86: found version 0.16.17=2C OK. Checking for bcc: found version 0.16.17=2C OK. Checking for iasl: found version 20070320=2C OK. Checking for xslt: found=2C OK. Checking for pthread: found=2C OK. /libexec/ld-elf.so.1: Shared object "libc.so.6" not found=2C required by "k= mk_sed" Checking for libxml2: /libexec/ld-elf.so.1: Shared object "libc.so.6" not f= ound=2C required by "kmk_sed" xml2 not found at -L/usr/local/lib -lxml2 -lpthread or xml2 headers no= t found Check the file /usr/home/moleque/sdk/bindings/configure.log for detailed = error information. =3D=3D=3D> Installing for libxml2-2.6.32 =3D=3D=3D> libxml2-2.6.32 depends on executable: pkg-config - found =3D=3D=3D> Generating temporary packing list =3D=3D=3D> Checking if textproc/libxml2 already installed =3D=3D=3D> 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=2C 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 ho= sts. I was asked to share it. from:walt (w41ter@gmail.com) "Desmond Chapman wrote: > Thanks for offering the help. How do I apply the patch that you sent? =20 My pleasure. The 'patch' program has a zillion confusing options because it has morphed many times from its original incarnation=2C but the '-p' fla= g is the main one to understand. =20 I didn't make the patch I posted=2C but this is how I would have done it: =20 #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=2C 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 =20 Now=2C look at the beginning of mynewpatch: =20 --- 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 =20 That's important because it tells you I made the patch from the top of the source directory=2C but that's a tradition that not everyone obeys. =20 Applying a patch is the mirror image of making a patch=2C so you need to know where to be in the source directory before you apply it. Hence=2C the -p flag is critical. =20 This is how I would apply this particular patch: =20 #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!) =20 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=2C you would use -p1 instead of -p0. =20 That's just a clue. You need to read the patch manpage for the rest! =20 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=2C forgive me if I am a bit confusing=3B but=2C I am divin= g head first into a development environment I have little experience with. How do I solve the xml2 conflict listed above the patch? =20 _________________________________________________________________ Want to do more with Windows Live? Learn =9310 hidden secrets=94 from Jamie= . http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!5= 50F681DAD532637!5295.entry?ocid=3DTXT_TAGLM_WL_domore_092008=