virtualbox.org

I have a fairly new Dell desktop running Debian 4.0. Just tried to build VirtualBox-1.6.4 and get the following error part way through the process. Does anyone know how to fix this? Also, assuming it can be made to work, has anyone been successful running XP as the guest system on a debian box similar to mine? I am looking into this as an alternative to vmware but need something that will work (networking, external devices, etc.) robustly:

kBuild: Compiling dyngen - dyngen.c
kBuild: Linking dyngen
kmk[2]: Leaving directory `/usr/local/VirtualBox-1.6.4/src/recompiler'
kmk[2]: Entering directory `/usr/local/VirtualBox-1.6.4/src/apps'
kmk[2]: pass_bldprogs: No such file or directory
kmk[2]: *** No rule to make target `pass_bldprogs'. Stop.
kmk[2]: Leaving directory `/usr/local/VirtualBox-1.6.4/src/apps'
kmk[1]: *** [pass_bldprogs_before] Error 2
kmk[1]: Leaving directory `/usr/local/VirtualBox-1.6.4/src'
kmk: *** [pass_bldprogs_before] Error 2

Forgive for asking, but why are you trying to compile it? The PUEL Edition has some nice features that are left of out the OSE version. You don't need to compile the PEUL Edition.

Hi,
I've got the same that DjG has described. Any idea about how to fix it ?
th

Perhaps you could start by answering the Qs that I asked djg. Read the posting guide

I have the same problem during compilation

TerryE wrote:Forgive for asking, but why are you trying to compile it? The PUEL Edition has some nice features that are left of out the OSE version. You don't need to compile the PEUL Edition.

It's simple: because the sources are available, that's all, don't argue with that, we just want to compile OSE version, that's how things works in Opensource World:):-) We just want to know why this error appears and how to fix it:)

Hummnn, I am not sure at all about "that's how it works in the FLOSS" world. I build OpenOffice.org and this is about 5 times the size of VBox and not nearly so well structured. Getting the config for OOo to work is absolutely a black art. Yes, you are free to build the source, but the general assumption is that if you want to go down that route then you are an experienced developer that can trouble-shoot this sort of platform specific gremlin yourself.

It's just an issue of understanding how the Kbuild process works, looking at the kmk files, looking at the detailed build logs and working out why that target stalls: a switch not set; something not pathed in or whatever. This is a straightforward activity for any C++ developer. Because of the variations of configuration, these issues are release sensitive. If I had your Debian build then it wouldn't take me long to work out why this doesn't build, but I don't: I have Ubuntu which is similar because it is a Debian derivative.

So unless the Sun/VBox guys pick this up then you are on your own. (And unless you haven't noticed the Sun guys have been remarkably silent since last Friday. )

I was hoping that devs will notice this post:-)
You're wrong in one thing, i'm not on my own, certainly i'm only one who have problems with that, im sure someone will fix that. I mean package managers willing to provide new wersion to their distro or homebrew hackers who just want to compile their favourite vm:-)
"that's how it works in the FLOSS world":-)

Well, I hope that you can hold your breath for a very long time. Good luck.

With the two makefiles the compilation works fine now.
thank Kido

Four days. Maybe you were right after all

Terry, may I note that your replies have been totally unhelpful.

For example: So if someone is compiling a million lines of code, they've got a reason. Wether it's for fun ("because you can") or there is a reason behind it, doesn't matter. So questioning wether to compile at all is not really useful. Stupid things like "are you using gnu make and not bsd make?" is useful, just attacking the premises for the question is not.

Thanks Kido, my tree is now building along....

I think attack is the wrong verb here. I didn't attack you. I just said that there is a pain-free option which is the PUEL route. I wasn't trying to criticise you for electing to go down the self-build OSE route if you want. It's just that if anyone elects to go down such a difficult route then they should equip themselves with the core competencies that they need first.

Incidentally you probably stand a better chance of help and guidance if you post to the developers mailing list rather than a forum primarily aimed at VBox users

Send vbox-dev mailing list submissions to

• vbox-dev@virtualbox.org

To subscribe or unsubscribe via the World Wide Web, visit

• http://vbox.innotek.de/mailman/listinfo/vbox-dev

or, via email, send a message with subject or body 'help' to

• vbox-dev-request@virtualbox.org

rewolff wrote:Terry, may I note that your replies have been totally unhelpful.....

Thats what I discoverd too!
I Miss some "/ignore" like on IRC-Chats. He is not Mr. Importend even if he likes to be one.

Madd

Madd, maybe I should just take a couple of weeks off and you take over answering the Qs. It shouldn't take more than 4 or so hours of your time a day. More seriously, I do try to answer the Qs in detail and honestly. I think that it is lot better than just telling the original posters what they want to hear, true or false.