gcc49: ../../scripts/check_jni_methods.sh: line 14: /tmp/check-jni-methods.75098.1: Permission denied

[mgs0lid_sn4ke@…]

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.

[mgs0lid_sn4ke@…]

main.log

[petrrr]

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

[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

[larryv (Lawrence Velázquez)]

Cc Me!

[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

[larryv (Lawrence Velázquez)]

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.

[mgs0lid_sn4ke@…]

/tmp/check-jni-methods.75098.1 was not in /tmp.

I tried rebooting, /tmp/check-jni-methods.75098.1 was still not in /tmp. I cleaned and reinstalled gcc49... and I got the same output.

[mgs0lid_sn4ke@…]

main.3.log

[ryandesign (Ryan Carsten Schmidt)]

Hmm, yes, the new log says basically the same thing:

:info:build ../../scripts/check_jni_methods.sh: line 14: /tmp/check-jni-methods.10465.1: Permission denied

It is strange that permission would be denied to write into /tmp. What are the permissions of /tmp on your system? You can find out by running:

ls -ld /tmp/

Ideally, the check-jni-methods.sh script would create its temporary files in the directory identified by the variable $TMPDIR; MacPorts sets this to an appropriate value. It would be reasonable to file a bug report with the developers of gcc asking them to use $TMPDIR instead of /tmp. However, /tmp should work too, and I haven't heard of this problem happening to anyone else when building gcc.