Opened 11 years ago

Last modified 11 years ago

#40758 closed defect

ld64 @136_2 Build error under Mavericks — at Version 2

Reported by: panayotis@… Owned by: jeremyhu@…
Priority: Normal Milestone:
Component: ports Version: 2.2.0
Keywords: Cc:
Port: ld64

Description (last modified by ryandesign (Ryan Carsten Schmidt))

I am trying to use some packages depending on ld64, but it seems to have some issues.

# port clean ld64
--->  Cleaning ld64
root@temp2:/opt/local/var/macports/sources/rsync.macports.org/release/tarballs# port install ld64
--->  Computing dependencies for ld64
--->  Fetching archive for ld64
--->  Attempting to fetch ld64-136_2+llvm33.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/ld64
--->  Attempting to fetch ld64-136_2+llvm33.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ld64
--->  Attempting to fetch ld64-136_2+llvm33.darwin_13.x86_64.tbz2 from http://packages.macports.org/ld64
--->  Fetching distfiles for ld64
--->  Verifying checksums for ld64
--->  Extracting ld64
--->  Applying patches to ld64
--->  Configuring ld64
--->  Building ld64
Error: org.macports.build for port ld64 returned: command execution failed
Please see the log file for port ld64 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port ld64 failed

Change History (3)

Changed 11 years ago by panayotis@…

Attachment: main.log added

comment:1 Changed 11 years ago by mattbrocklehurst@…

Missing include file

312	:info:build #include <unordered_set>

Think this is something to do with switching compilers on Mavericks from Gcc to lvmm

Last edited 11 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Owner: changed from macports-tickets@… to jeremyhu@…
Note: See TracTickets for help on using tickets.