[MacPorts] #33085: boost: support building for a different SDK

[MacPorts]

#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@…):

 I invoked the following port command:

 sudo port -v build boost +debug



 Here is a compiler line from from that build...



     "/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-g++-4.2"
 "-isysroot"
 "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk"
 -ftemplate-depth-128 -O0 -fno-inline -Wall -g -no-cpp-precomp -gdwarf-2
 -fexceptions -arch x86_64  -DBOOST_ALL_NO_LIB=1
 -DBOOST_SYSTEM_STATIC_LINK=1  -I"." -c -o
 "bin.v2/libs/filesystem/build/darwin-4.2.1/debug/address-
 model-64/architecture-x86/link-static/v2/src/v2_operations.o"
 "libs/filesystem/v2/src/v2_operations.cpp"


 which "incorrect options" do you content are being injected by bjam? The
 patch to add isysroot to the compiler invocation in the config file should
 not affect what bjam is injecting into the compiler invocations. It just
 adds an additional compiler option. Please explain why you think adding
 the isysroot option is going to cause the options listed in #33115 to be
 added?  They certainly aren't added in my quick test.

-- 
Ticket URL: <https://trac.macports.org/ticket/33085#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS