[MacPorts] #32602: virtualbox: gcc-apple-4.0: not found
MacPorts
noreply at macports.org
Mon Dec 19 23:41:13 PST 2011
#32602: virtualbox: gcc-apple-4.0: not found
--------------------------------------+-------------------------------------
Reporter: ryandesign@… | Owner: royliu@…
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: ports | Version: 2.0.3
Resolution: | Keywords:
Port: virtualbox |
--------------------------------------+-------------------------------------
Changes (by ryandesign@…):
* status: closed => reopened
* resolution: fixed =>
Comment:
Now the patch just fails to apply:
{{{
patching file Config.kmk
Hunk #2 FAILED at 1781.
1 out of 5 hunks FAILED -- saving rejects to file Config.kmk.rej
}}}
Even if it had succeeded in applying, you would now be running "gcc-
apple-4.2"; Xcode doesn't provide a program by that name either. The name
of the program is "gcc-4.2", and ideally you would be running it by its
full path, /usr/bin/gcc-4.2, as contained in the CC environment variable
at configure time.
My question was not why the portfile patches virtualbox; I had not
actually realized before that we were doing that. My question was why the
virtualbox build process, as shipped, does not make use of the usual
environment variables, or why we are not patching it so that it would do
so.
--
Ticket URL: <https://trac.macports.org/ticket/32602#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list