Ticket #650 (closed enhancement: fixed)
Opened 3 years ago
Last modified 7 months ago
VirtualBox additions need a bep
| Reported by: | kallisti5 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | default | Version: | |
| Severity: | normal | Keywords: | vbox |
| Cc: |
Description
The VirtualBox? Haiku additions have been accepted upsteam..
Attached is an *early* non-working bep (don't commit it yet). It seems the Haiku stuff isn't working upstream 100% yet... and some important stuff is missing from the Vbox 4.2.2 source release archive.
Attachments
Change History
Changed 3 years ago by kallisti5
- attachment vbox_additions-4.2.2_r1.bep added
comment:1 Changed 3 years ago by kallisti5
- Summary changed from vbox additions need a bep to VirtualBox additions need a bep
comment:2 Changed 3 years ago by richienyhus
Quoting Agmsmith from the haiku forum:
When HaikuPorter ran the ./configure script, didn't recognise the OS. I manually ran the commands on a newer version of the source obtained from SVN, and ./configure recognised Haiku but stopped with a complaint about a missing IASL compiler (which theoretically could be built from the source code Intel provides). I got it to go further by using ./configure --build-headless --disable-python --disable-java --nofatal, which was good enough to get to the actual compilation started with kmk VBOX_ONLY_ADDITIONS=1 VBOX_WITH_ADDITION_DRIVERS=1 VBOX_USE_GCC4=1 all That then failed with the same problem I had before in kDefs.h. Looks like a little bit of source code fixing is actually needed.
comment:3 Changed 7 months ago by diver
- Resolution set to fixed
- Status changed from new to closed
r1