Hi Vasily, Your patch worked like a charm! I am in your debt, as this issue has dragged on for months. This is the commit I made to the MacPorts trunk.
http://trac.macports.org/changeset/101907 Also, please find the relevant patch attached. It's basically your fix, with the LLVMGCC42 to APPLEGCC42 replacement done in place. Does it look OK to you? I have a lingering question about the addition of the two lines in kLdrModMachO.c and mach-o.h. What is their purpose, in light of using Apple GCC 4.2 instead of the LLVM toolchain? Thanks again and regards, Roy On Thu, Jan 17, 2013 at 7:46 PM, Vasily Levchenko < [email protected]> wrote: > Hi, Roy, > Could you please check whether the attached patch fixes issue for you? > Note: > it also required specifying > > VBOX_GCC_TOOL=APPLEGCC42 > VBOX_GXX_TOOL=APPLEGCC42 > TEMPLATE_VBOXBLDPROG_TOOL=APPLEGCC42 > in kmk <command line> or in LocalConfig.kmk > > On Jan 18, 2013, at 12:47 AM, Roy Liu <[email protected]> wrote: > > Hi, > > I reported on this issue a while back, and we seem to have made some > progress on the issue. > > > http://trac.macports.org/ticket/36910 > > The culprit seems to be a recent version of the ld64 linker. I am curious: > What compiler toolchain is the official Mac OS X distribution of VirtualBox > built with? > > > Your suspicious looks right. And Config.xml code contains the check > whether version of Xcode is lower than 4.2. > > This information may help us pinpoint the source of the issue. > > -Roy > > > _______________________________________________ > vbox-dev mailing list > [email protected] > https://www.virtualbox.org/mailman/listinfo/vbox-dev > > > >
patch-apple-gcc42.diff
Description: Binary data
_______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
