[vbox-dev] FreeBSD build

Desmond Chapman que_deseja at hotmail.com
Tue Oct 14 11:42:25 GMT 2008

Mr St. Osmunden.
I do not consider it a simple problem. here is why:

MASTER_SITES=	ftp://ftp.netlabs.org/pub/kbuild/

COMMENT=	Makefile framework

# XXX: This case is not handled by USE_AUTOTOOLS as kmk bootstrap involves
# running these directly.
BUILD_DEPENDS=	automake-1.9:${PORTSDIR}/devel/automake19 \

BROKEN=		changes permissions on already installed binaries


I am the one working on this port. I need the patches to fix it. This is not spam.
Any BSD release- whether it be Free, Net, Open, or Dragonfly- is not going to compromise
it's security for a binary or a build system. If the source code was released to where it wasn't 
dependent upon a certain build system, it would have already been added to the FreeBSD ports and the kernel driver would be
an ongoing and active project.

Because of the lack of documentation about build process and errors AND the lack of developers who are willing to submit changes and patches to the public
in the form of such documentation, I have to ask constantly for help. WE both are aware that neither part of the previous statement should be true but it is.
I post the patches for the community to see, not hide them.

Back to the original post:

kBuild needs to be patched to where it doesn't compromise security. If the configure script had an "NO_KBUILD" option,
and produced a normal Makefile, the porting- as already said- would have been done.

You would not going to compromise your code if automake was a possible security issue.
The same applies to FreeBSD and kBuild.

Ladies and gentlemen, I need those patches for kBuild-0.1.3 and kBuild-0.1.4 and VirtualBox-2.0.0.
The source code in a non-kBuild-dependent form would also be nice.

> ------------------------------
> Message: 6
> Date: Mon, 13 Oct 2008 18:37:31 +0200
> From: "Knut St. Osmundsen" <bird at sun.com>
> Subject: Re: [vbox-dev] FreeBSD build
> To: "VirtualBox developer's list" <vbox-dev at virtualbox.org>
> Message-ID: <48F3794B.3010203 at sun.com>
> Content-Type: text/plain; charset=windows-1252
> Mr. Chapman,
> some people are starting to get annoyed here at vbox-dev.
> You have been told several times, both directly and indirectly, that
> what we are *not* looking help getting things building on FreeBSD
> because this is a very easy task. We are rather for someone to pick up
> the kernel driver (stop it from crashing, make the memory part work
> (this is the main problem) and make the whole product usable).  Now, if
> someone steps up that has the required skill and is willing to spend
> some time helping with this, I will personally make sure the tree is in
> a building state on FreeBSD.  If I do it myself it'll probably take less
> than two hours.
> Two hours is a small amount of time, which is why it simply doesn't make
> sense for us to spend time on verifying and applying build patches.  The
> same thing goes for reading about FreeBSD build errors and very basic
> build questions, not to mention answering them.  Summing up the time
> consumed by just Klaus, Frank and me on these exchanges, I'm pretty
> certain we're close to 2 hours already.  That is 2 hours not spent
> getting the FreeBSD port working, well and some other stuff.
> So, please, would you kindly *stop* posting simple beginners questions
> here.  You can post all you like to vbox-users.
> Kind Regards,
>  knut
> PS. It would've helped if you were less spam like in your approach, esp.
> after having it pointed out several times.
> Desmond Chapman wrote:
> > Users:Look on the forums for build instructions.
> > Developers:Need help with following problem:
> > @gcc -c -O2 -pipe -ansi -Wall -Wno-unused -I/usr/local/include/libIDL-2.0
> > Problem links to src/libs/xpcom18a4 subdirectory in VirtualBox-2.0.0
> > 

Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20081014/b831d1c5/attachment.html>

More information about the vbox-dev mailing list