[vbox-dev] vbox-dev Digest, Vol 24, Issue 8::make(1) Error 2 after an invalid Unix command seems to have been run on FreeBSD (was: New Build) (Jason Spiro)

[Desmond Chapman]

> Message: 3
> Date: Tue, 7 Oct 2008 10:01:40 -0400
> From: "Jason Spiro" <jasonspiro2 at gmail.com>
> Subject: [vbox-dev] make(1) Error 2 after an invalid Unix command
> 	seems to	have been run on FreeBSD (was: New Build)
> To: "VirtualBox developer's list" <vbox-dev at virtualbox.org>
> Message-ID:
> 	<c241693f0810070701o6142285occ77c5e65454dd04 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> 2008/10/7 Desmond Chapman <que_deseja at hotmail.com> wrote:
> > VISIBILITY_ATTRIBUTE=1 -DHAVE_VA_LIST_AS_ARRAY -DHAVE_VA_COPY
> > -DVA_COPY\(a\,b\)=__builtin_va_copy\(a\,b\)
> > -Wp,-MD,/usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o.dep
> > -Wp,-MT,/usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o
> > -Wp,-MP -o
> > /usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o
> > /usr/home/moleque/VirtualBox-2.0.0/src/libs/xpcom18a4/xpcom/typelib/xpidl/xpidl.c
> > kmk[3]: Leaving directory
> > `/usr/home/moleque/VirtualBox-2.0.0/src/libs/xpcom18a4'
> > kmk[2]: *** [pass_bldprogs_before] Error 2
> > kmk[2]: Leaving directory `/usr/home/moleque/VirtualBox-2.0.0/src/libs'
> > kmk[1]: *** [pass_bldprogs_before] Error 2
> > kmk[1]: Leaving directory `/usr/home/moleque/VirtualBox-2.0.0/src'
> > kmk: *** [pass_bldprogs_before] Error 2
> >
> >
> > I found part of the howto/build on a Russian FreeBSD site.
> > http://www.bsdportal.ru/viewtopic.php?t=18808&sid=c0a8b366efa1d8496aa764be393bc53a
> >
> > Is there something I am missing in my environment?
> >
> 
> The command
> 
> {{begin quote}}
> VISIBILITY_ATTRIBUTE=1 -DHAVE_VA_LIST_AS_ARRAY -DHAVE_VA_COPY
> -DVA_COPY\(a\,b\)=__builtin_va_copy\(a\,b\)
> -Wp,-MD,/usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o.dep
> -Wp,-MT,/usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o
> -Wp,-MP -o /usr/home/moleque/VirtualBox-2.0.0/out/freebsd.amd64/release/obj/src/libs/xpcom18a4/xpidl/xpcom/typelib/xpidl/xpidl.o
> /usr/home/moleque/VirtualBox-2.0.0/src/libs/xpcom18a4/xpcom/typelib/xpidl/xpidl.c
> {{end quote}}
> 
> is not a valid Unix command.  Maybe you did not copy and paste
> starting on a valid line boundary.  Every time you email us, please
> tell us your OS version, compiler version, and what you typed to do
> the build.  In this case, it would've helped if you told us more of
> the output.  50 lines of output is always fine.  In this case, please
> also use the "script" command to make a log of everything you type and
> everything that happens starting from right after you decompress
> VirtualboxOSE.tar.gz, rename it to typescript.txt, and attach it.
> 
> Also:  I improved the subject line for you.  :)
> 
> Another thing:  VirtualBox does not work on FreeBSD.  How much C / C++
> experience do you have?  Could you point us to samples of your
> contributions to the open source community, if any?  If I am going to
> be helping you build vbox on a platform it was never made to build on,
> I want to know that you will be able to fix the incompatibilities that
> also stop it from *working* on FreeBSD in the first place.  :)
> 
> Cheers,
> -Jason
> 
> -- 
> Jason Spiro: software/web developer, trainer, IT consultant. I support
> Linux, UNIX, Windows, and more. Contact me to discuss your needs.
> 613-668-6096 / info at jspiro.com
> 
> 
> 

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? 
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.

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.

_________________________________________________________________
See how Windows Mobile brings your life together—at home, work, or on the go.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20081008/3299b3ac/attachment.html>