Opened 10 years ago

Last modified 8 years ago

#46168 assigned defect

gcc49 failed to build "command failed" — at Version 5

Reported by: mgs0lid_sn4ke@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: larryv@…
Port: gcc49

Description (last modified by larryv (Lawrence Velázquez))

Hi,

It's my third ticket (#46118, #46126) since I've tried to build gcc49 after reinstalling Macports on my laptop. Looks like there is a problem with build dependencies. gcc49 failed to build. Output :

sudo port install gcc49
--->  Computing dependencies for gcc49
--->  Building gcc49
Error: org.macports.build for port gcc49 returned: command execution failed
Please see the log file for port gcc49 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/gcc49/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port gcc49 failed

Thanks in advance for your help.

Change History (7)

Changed 10 years ago by mgs0lid_sn4ke@…

Attachment: main.log added

main.log

comment:1 Changed 10 years ago by petrrr

Cc: mww@… openmaintainer@… removed
Owner: changed from macports-tickets@… to mww@…

Thanks for reporting. Note that you do not need to CC openmaintainer.

comment:2 in reply to:  description Changed 10 years ago by larryv (Lawrence Velázquez)

There’s no obvious problem from the log, other than that the build phase fails. Could you please clean all ports to make sure nothing’s amiss, then try installing gcc49 again. Attach the new main.log if it fails.

% sudo port clean all
% sudo port install gcc49

comment:3 Changed 10 years ago by larryv (Lawrence Velázquez)

Cc: larryv@… added

Cc Me!

Changed 10 years ago by mgs0lid_sn4ke@…

Attachment: main.2.log added

comment:4 Changed 10 years ago by mgs0lid_sn4ke@…

I did it, new log file is attached.

During the cleaning, I had several times this warning :

Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option

comment:5 in reply to:  4 Changed 10 years ago by larryv (Lawrence Velázquez)

Description: modified (diff)

Replying to mgs0lid_sn4ke@…:

During the cleaning, I had several times this warning :

Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option

You only have to worry about that message if you see it while trying to install or upgrade a port.

From the log:

:info:build /bin/sh ../../scripts/check_jni_methods.sh
:info:build ../../scripts/check_jni_methods.sh: line 14: /tmp/check-jni-methods.75098.1: Permission denied
:info:build make[6]: *** [all-local] Error 1

What are the permissions on /tmp/check-jni-methods.75098.1? I would suggest deleting it and trying again, but there’s another message from earlier…

:msg:archivefetch --->  Attempting to fetch gcc49-4.9.2_1.darwin_14.x86_64.tbz2.rmd160 from http://packages.macports.org/gcc49
:debug:archivefetch failed verification with key /opt/local/share/macports/macports-pubkey.pem
:debug:archivefetch openssl output: couldn't create error file for command: permission denied
:warn:archivefetch Failed to verify signature for archive!

…which makes me suspect that something might be generally wonky with your /private/tmp.

Try rebooting your machine, and verify that check-jni-methods.75098.1 is no longer in /tmp; if it is, delete it. Then clean and install gcc49 again.

Last edited 10 years ago by larryv (Lawrence Velázquez) (previous) (diff)
Note: See TracTickets for help on using tickets.