Opened 11 years ago

Closed 11 years ago

#41129 closed defect (invalid)

llvm-gcc42: build fails

Reported by: chbperso@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: mavericks Cc:
Port: llvm-gcc42

Description

My Mac is running Mavericks and when I tried to install "mp4v2" I have this message:

$ sudo port install mp4v2
--->  Computing dependencies for mp4v2  
--->  Dependencies to be installed: llvm-gcc42
--->  Building llvm-gcc42
Error: org.macports.build for port llvm-gcc42 returned: command execution failed
Error: Failed to install llvm-gcc42
Please see the log file for port llvm-gcc42 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-gcc42/llvm-gcc42/main.log
Error: The following dependencies were not installed: llvm-gcc42
To report a bug, follow the instructions in the guide:
  http://guide.macports.org/#project.tickets
Error: Processing of port mp4v2 failed

Xcode v5.0.1 (5A2053) is installed on my Mac

Attachments (2)

main.log (682.2 KB) - added by chbperso@… 11 years ago.
Log file
main.2.log (13.2 KB) - added by chbperso@… 11 years ago.
Log file (2)

Download all attachments as: .zip

Change History (5)

Changed 11 years ago by chbperso@…

Attachment: main.log added

Log file

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

Keywords: mavericks added
Port: llvm-gcc42 added
Priority: HighNormal
Resolution: invalid
Status: newclosed
Summary: Error: Processing of port mp4v2 failedllvm-gcc42: build fails

The log says:

:info:build The directory that should contain system headers does not exist:
:info:build   /usr/include

Install the Xcode command line tools using xcode-select --install as mentioned in our documentation.

comment:2 in reply to:  1 Changed 11 years ago by chbperso@…

Resolution: invalid
Status: closedreopened

Replying to ryandesign@…:

The log says:

:info:build The directory that should contain system headers does not exist:
:info:build   /usr/include

Install the Xcode command line tools using xcode-select --install as mentioned in our documentation.

I really believe Xcode command line tools was installed. When I check on Xcode/Preferences/Locations the option "Command Line Tools" is set to "Xcode 5.0.1 (5A2053)"

To be sure I run the command xcode-select --install and this time it install the command line.

Now I have another error:

$ sudo port install mp4v2
Password:
--->  Computing dependencies for mp4v2
--->  Dependencies to be installed: llvm-gcc42
--->  Building llvm-gcc42
--->  Staging llvm-gcc42 into destroot
--->  Installing llvm-gcc42 @2336.11_1
--->  Activating llvm-gcc42 @2336.11_1
--->  Cleaning llvm-gcc42
--->  Fetching archive for mp4v2
--->  Attempting to fetch mp4v2-1.9.1_2.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/mp4v2
--->  Attempting to fetch mp4v2-1.9.1_2.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/mp4v2
--->  Attempting to fetch mp4v2-1.9.1_2.darwin_13.x86_64.tbz2 from http://packages.macports.org/mp4v2
--->  Fetching distfiles for mp4v2
Error: mp4v2 does not build on Mavericks or later.
Error: org.macports.fetch for port mp4v2 returned: unsupported platform
Please see the log file for port mp4v2 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_mp4v2/mp4v2/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port mp4v2 failed
Last edited 11 years ago by chbperso@… (previous) (diff)

Changed 11 years ago by chbperso@…

Attachment: main.2.log added

Log file (2)

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

Resolution: invalid
Status: reopenedclosed

One issue per ticket, please. This ticket is about llvm-gcc42 failing to build, and was solved by you installing the command line tools.

The new log is about mp4v2 and it says: "mp4v2 does not build on Mavericks or later." That's handled in #40813.

Note: See TracTickets for help on using tickets.