Opened 9 years ago
Closed 4 years ago
#50622 closed update (fixed)
virtualbox: update to 5.1.2
| Reported by: | 1-61803 | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | myint (Steven Myint) | |
| Port: | virtualbox virtualbox-extension-pack virtualbox-guest-additions |
Description
currently v5.0.14, v4.2.16 fails to build
Change History (14)
comment:1 follow-up: 6 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | virtualbox 5 → virtualbox: update to 5.0.14 |
|---|---|
| Type: | request → update |
comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
See also #40786 with a partial update to an earlier version.
comment:6 Changed 8 years ago by ctreleaven (Craig Treleaven)
Replying to ryandesign:
Patches are accepted. This port currently has no maintainer.
I was curious whether the current version of VirtualBox was easier to build on OS X. It is not:
Per https://www.virtualbox.org/ticket/15004 (Dec 2015)
You can't use Xcode versions newer than 4.1.x to build VirtualBox. This might change eventually, but it's not expected for the foreseeable future.
There are instructions how to extract Xcode 4.1.x on newer OSX releases (the installer refuses to run), so I don't think this is a showstopper."
The port has multiple, extensive patches that were required to build version 4.2.16. Many hunks now fail to apply if attempting to build 5.1.14. It will be a non-trivial amount of work to update the patches and account for other changes in the build process. All to build with a very old toolchain. Too much work for me.
comment:8 Changed 8 years ago by myint (Steven Myint)
| Cc: | myint added |
|---|
comment:9 Changed 6 years ago by socratisk (Socratis)
Hey everyone, just joined in to say that I have a set of instructions on how to build 5.1.2 (and later) on 10.9 up to 10.13 (no 10.14 available macports yet). What is it required to do a proper MacPorts build? I could take over this, since I've been building my own VirtualBox with MacPorts for quite some time now...
The instructions for building VirtualBox from the source are in Build VirtualBox ≥ 5.1.2 on OSX ≥ 10.9, with the discussion in (Discussion) Build VirtualBox ≥ 5.1.2 on OSX ≥ 10.9.
If it's a matter of keeping things up to date, I could help with that. Just let me know how to coordinate it...
comment:10 Changed 6 years ago by mf2k (Frank Schima)
| Port: | virtualbox-extension-pack virtualbox-guest-additions added |
|---|---|
| Summary: | virtualbox: update to 5.0.14 → virtualbox: update to 5.1.2 |
@socratisk: Please submit submit a pull request with your Portfile changes.
comment:11 Changed 6 years ago by kencu (Ken)
I think it would be very cool to have the ability to build virtualbox again in MacPorts. If you're looking for encouragement, consider this it!
comment:12 Changed 6 years ago by socratisk (Socratis)
@mf2k
I will need some help here to understand what the process/procedure is. What I've done is to use the official VirtualBox SVN repository and build a VirtualBox app out of it with the help of MacPorts. It's not 100% working, in the sense that it's not self-contained (yet, I still haven't solved the linking problem with the MacPorts libraries). Which means that if you want to run it on a Mac, you got to have the MacPorts installed. Which I guess it wouldn't be a problem, right? ;)
Somebody over at IRC pointed me to this ticket, and I thought I could somehow help, I just need to know "how" I could do that.
Now, I don't know what a "pull request" would mean, as I said I'm as n00b as they come, trust me. I'll have to hit the books, which is fine by me, but a bit slower. On the other hand, I wouldn't mind a "take a left here, speed bump in 50m" instructions and helping hand... ;)
And I really don't have a clue what "Portfile changes" is...
BTW, I noticed in your comment, that there are two additional ports listed: Extension Pack (ExtPack) and Guest Additions (GAs). I *cannot* build the ExtPack, it's closed-source, and I haven't built the GAs (yet, but I'm optimistic). Just a binary OSX app, which BTW, is at 5.2.18, not 5.1.2. I started at 5.1.2, but the current 5.2.18 builds just fine as well...
@kencu
Thanks, appreciated!
PS. In a n00b mistake, I forgot to turn on Notifications, that's why I didn't reply earlier. Issue was addressed.
comment:13 Changed 6 years ago by 1-61803
comment:14 Changed 4 years ago by chrstphrchvz (Christopher Chavez)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Patches are accepted. This port currently has no maintainer.