<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
<br><br><br>> Message: 3<br>> Date: Tue, 7 Oct 2008 10:01:40 -0400<br>> From: "Jason Spiro" <jasonspiro2@gmail.com><br>> Subject: [vbox-dev] make(1) Error 2 after an invalid Unix command<br>> seems to have been run on FreeBSD (was: New Build)<br>> To: "VirtualBox developer's list" <vbox-dev@virtualbox.org><br>> Message-ID:<br>> <c241693f0810070701o6142285occ77c5e65454dd04@mail.gmail.com><br>> Content-Type: text/plain; charset=ISO-8859-1<br>> <br>> 2008/10/7 Desmond Chapman <que_deseja@hotmail.com> wrote:<br>> > VISIBILITY_ATTRIBUTE=1 -DHAVE_VA_LIST_AS_ARRAY -DHAVE_VA_COPY<br>> > -DVA_COPY\(a\,b\)=__builtin_va_copy\(a\,b\)<br>> > -Wp,-MD,/usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o.dep<br>> > -Wp,-MT,/usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o<br>> > -Wp,-MP -o<br>> > /usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o<br>> > /usr/home/moleque/VirtualBox-2.0.0/src/libs/xpcom18a4/xpcom/typelib/xpidl/xpidl.c<br>> > kmk[3]: Leaving directory<br>> > `/usr/home/moleque/VirtualBox-2.0.0/src/libs/xpcom18a4'<br>> > kmk[2]: *** [pass_bldprogs_before] Error 2<br>> > kmk[2]: Leaving directory `/usr/home/moleque/VirtualBox-2.0.0/src/libs'<br>> > kmk[1]: *** [pass_bldprogs_before] Error 2<br>> > kmk[1]: Leaving directory `/usr/home/moleque/VirtualBox-2.0.0/src'<br>> > kmk: *** [pass_bldprogs_before] Error 2<br>> ><br>> ><br>> > I found part of the howto/build on a Russian FreeBSD site.<br>> > http://www.bsdportal.ru/viewtopic.php?t=18808&sid=c0a8b366efa1d8496aa764be393bc53a<br>> ><br>> > Is there something I am missing in my environment?<br>> ><br>> <br>> The command<br>> <br>> {{begin quote}}<br>> VISIBILITY_ATTRIBUTE=1 -DHAVE_VA_LIST_AS_ARRAY -DHAVE_VA_COPY<br>> -DVA_COPY\(a\,b\)=__builtin_va_copy\(a\,b\)<br>> -Wp,-MD,/usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o.dep<br>> -Wp,-MT,/usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o<br>> -Wp,-MP -o /usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o<br>> /usr/home/moleque/VirtualBox-2.0.0/src/libs/xpcom18a4/xpcom/typelib/xpidl/xpidl.c<br>> {{end quote}}<br>> <br>> is not a valid Unix command. Maybe you did not copy and paste<br>> starting on a valid line boundary. Every time you email us, please<br>> tell us your OS version, compiler version, and what you typed to do<br>> the build. In this case, it would've helped if you told us more of<br>> the output. 50 lines of output is always fine. In this case, please<br>> also use the "script" command to make a log of everything you type and<br>> everything that happens starting from right after you decompress<br>> VirtualboxOSE.tar.gz, rename it to typescript.txt, and attach it.<br>> <br>> Also: I improved the subject line for you. :)<br>> <br>> Another thing: VirtualBox does not work on FreeBSD. How much C / C++<br>> experience do you have? Could you point us to samples of your<br>> contributions to the open source community, if any? If I am going to<br>> be helping you build vbox on a platform it was never made to build on,<br>> I want to know that you will be able to fix the incompatibilities that<br>> also stop it from *working* on FreeBSD in the first place. :)<br>> <br>> Cheers,<br>> -Jason<br>> <br>> -- <br>> Jason Spiro: software/web developer, trainer, IT consultant. I support<br>> Linux, UNIX, Windows, and more. Contact me to discuss your needs.<br>> 613-668-6096 / info@jspiro.com<br>> <br>> <br>> <br><br>I'm going into this blindly. This is how I learn. For your other suggestion, I'm keeping FreeBSD. Qemu has changed, virtualization on amd64 for FreeBSD is different. I may not be a developer but I am aware that there is something missing in the install environment. I've asked before if anyone has compared a Linux build to a build on FreeBSD. Move both of those to the amd64 architecture. Are the libraries and binaries installed into the "same" relative places? <br>I appreciate your help but I will refuse any offer of discouragement, I'm going to try even if I fail constantly. My email is available. You can always send me links to howto.<br><br>Back to the subject. Error code 2 seems to refer to access violations. I want to get around that. Is this a security level issue? Or is it a Makefile issue? C an C++ doesn't get around the set security level on FreeBSD.<br><br /><hr />See how Windows Mobile brings your life together—at home, work, or on the go. <a href='http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/' target='_new'>See Now</a></body>
</html>