[MacPorts] #36026: ld64 sometimes builds wrong which causes other software to fail to build

[MacPorts]

#36026: ld64 sometimes builds wrong which causes other software to fail to build
-------------------------+------------------------
  Reporter:  jwhowse4@…  |      Owner:  jeremyhu@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.1.2
Resolution:              |   Keywords:
      Port:  ld64        |
-------------------------+------------------------

Comment (by jeremyhu@…):

 Hmm... your preprocessed source files don't seem to match the build ld.  I
 wonder if there is something in the environment (CPATH?) that is causing
 your run to be different than the port install run.

 Please apply this patch to ld64's Portfile for each -tstX prefix:

 {{{
 Index: Portfile
 ===================================================================
 --- Portfile    (revision 98257)
 +++ Portfile    (working copy)
 @@ -29,6 +29,12 @@

  patchfiles              ld64-version.patch ld64-133-no-
 CrashReporterClient.h.patch

 +#compiler.cpath              ""
 +#compiler.library_path       ""
 +configure.cflags-append     -save-temps
 +configure.cxxflags-append   -save-temps
 +configure.objcflags-append  -save-temps
 +
  # We don't set llvmXX as the default variant on Tiger because it would
 introduce a
  # dependency cycle as llvm requires apple-gcc42 and ld64 to build
 correctly.  Users
  # wanting LTO support in ld64 on Tiger can install the +llvm variant
 after llvm
 }}}

 then for each prefix do:
 {{{
 sudo port -v uninstall ld64
 port -v install ld64 +llvm31
 }}}

 Then send me the new ld64 workdirs (no need to send me the whole thing,
 just <prefix>/var/macports/build/*ld64

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