[MacPorts] #60747: perl5.28 fails to build
MacPorts
noreply at macports.org
Wed Jul 1 22:32:21 UTC 2020
#60747: perl5.28 fails to build
------------------------------+----------------------
Reporter: programmingkidx | Owner: mojca
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: perl5.28 |
------------------------------+----------------------
Comment (by kencu):
Thanks. it is a bit of a strange error you're seeing, but then there are
not too many people building Tiger software on an 8 core machine (not even
me).
{{{
538 :info:build make[1]: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_perl5/perl5.28/work/perl-5.28.3/ext
/Devel-Peek'
539 :info:build make: *** read jobs pipe: Resource temporarily
unavailable. Stop.
540 :info:build make: *** Waiting for unfinished jobs....
}}}
At first blush, I'm not exactly sure what this error is. To factor it,
we're going to simplify things to remove some variables.
One common thing that happens is race conditions, where one part of the
software build is looking for something, but it hasn't been finished being
built yet by another part of the build. These are hard to debug, but easy
to find once you think of them -- just disable that.
In your Portfile, put
{{{
use_parallel_build no
}}}
or, alternatively, you can set it perhaps more easily in
{{{/opt/local/etc/macports/macports.conf}}} where you find line that specs
the build jobs and set it to "1".
Once that is done, you should clean, and then try the build again:
{{{
sudo port clean perl5.28
sudo port -v build perl5.28
}}}
if it fails the same way again, then you know it's not that issue.
The next most common thing is the old {{{/usr/bin/make}}} on Tiger causes
lots of problems. To fix that, install {{{gmake}}} (probably is installed}
and then set the build to use it. In the portfile, put
{{{
build.cmd gmake
}}}
and then clean and try your build again.
If neither of those things gets past your error, put up a new log with the
results of those mods, and we'll take a look.
I doubt you will be able to complete a build anyway, due to [ticket:60740]
but at least you should be able to get to that error (which we have a fix
for, just deciding how best to implement it).
--
Ticket URL: <https://trac.macports.org/ticket/60747#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list