Libcaca build error

[giby_the_kid@…]

Hi,

One more time upgrading my mac port one port failed...

sth-dw399:~ benjaminleduc$ sudo port upgrade outdated
--->  Computing dependencies for libcaca
--->  Building libcaca
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for libcaca is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_libcaca/libcaca/main.log
Error: Unable to upgrade port: 1
To report a bug, see <http://guide.macports.org/#project.tickets>
sth-dw399:~ benjaminleduc$ 

Thanks

[ryandesign (Ryan Carsten Schmidt)]

Remember to use WikiFormatting, fill in the Port field, and Cc the port's maintainer.

Please clean and try again ("sudo port clean libcaca") and if it fails again, attach the new main.log (the main.log you attached is incomplete).

Both this an #30641 look like a problem with mono. Perhaps you need to rebuild mono ("sudo port -n upgrade --force mono").

[giby_the_kid@…]

log of the bug

[giby_the_kid@…]

here is the new one

and I'm rebuilding mono

[ryandesign (Ryan Carsten Schmidt)]

So both here and in #30641 the complaint is:

:info:build ** (/opt/local/lib/mono/1.0/mcs.exe:13569): CRITICAL **: _wapi_shm_file_open: shared file [/var/empty/.wapi/shared_data-sth-dw399.rhi.hi.is-Darwin-i386-312-12-0] open error: No such file or directory

I'll bet this relates to MacPorts 2.0's new macports user concept: /var/empty is that user's home directory, so this "mcs.exe" is apparently trying to write to the home directory, failing to do so because it does not have permission to write to /var/empty, then experiencing this critical error when unable to read the file it previously failed to write. Perhaps modifying the port to set $HOME to something inside ${workpath} would be a workaround.

[nerdling (Jeremy Lavergne)]

Another solution is adding build.asroot yes to the Portfile. I've recommended this to people in IRC that have run into this specific problem.

[phw@…]

I have changed the default behaviour to "build.asroot yes" to fix the problem

[ryandesign (Ryan Carsten Schmidt)]

Setting HOME to something inside workpath would be better if it works. See also #31827. We'd rather not build as root; that's why the privilege-dropping code was added to MacPorts in the first place.

[ryandesign (Ryan Carsten Schmidt)]

No longer build as root as of r133310, since #31827 has been fixed.