#33085: boost: support building for a different SDK --------------------------------------+------------------------------------- Reporter: ryandesign@… | Owner: adfernandes@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: wontfix | Keywords: haspatch Port: boost | --------------------------------------+------------------------------------- Comment(by bayoubengal@…): Replying to [comment:9 adfernandes@…]:
Uhh...I thought you were joking. No, I'm not going to zip up gigabytes and upload them anywhere.
I ''have'' attached a list of my installed ports, including my macports.conf and variants.conf, if those help.
It could even be that the use of the `+debug` flag resets the compiler flags to what they should be. `bjam` does things like that.
All I know is that, through my own testing, is that the correct `jamfiles` get used and (supposedly) the Darwin toolset is used. We're all using Mac OS 10.7.2 and Xcode 4.2.1 with LLVM-GCC-4.2.1.
No. I'm not joking. I have considerable experience digging into the guts of macports and resolving problems. I've gotten boost to compile in macports for 3 different platforms and 5 OS versions. I'll look at your attachments and see if I see anything interesting. the +debug option can certainly cause additional compiler options to be passed in, but in my test, it didn't pass in the ones you cited. So, it must be something else. If you want to troubleshoot it yourself, you can do three things... 1) put a "puts" statement right before the line in question in the portfile and dump all the variables involved to the console so you can see what they are. 2) look at the resulting user-config.jam and see if the line in it is exactly as follows. I don't recall for sure, but I think the whitespace is also important. using darwin : : g++ -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk ; NOTE: My developer directory is "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/" because I'm using Xcode 4.3. Yours may still be in /Developer. 3) put the do the build in verbose mode and see exactly what data is being passed to the compiler on the command line. -- Ticket URL: <https://trac.macports.org/ticket/33085#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS