[Bug 218378] devel/libsigc++20 fails on an upgrade
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Apr 4 17:00:29 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218378
Bug ID: 218378
Summary: devel/libsigc++20 fails on an upgrade
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: rotkap at gmx.de
Hi,
devel/libsigc++20 fails on an upgrade:
====> Compressing man pages (compress-man)
===>>> Starting check for runtime dependencies
===>>> Gathering dependency list for devel/libsigc++20 from ports
===>>> No dependencies for devel/libsigc++20
===> Installing for libsigc++-2.10.0
===> Checking if libsigc++ already installed
===> Registering installation for libsigc++-2.10.0
pkg-static: Unable to access file
/usr/ports/devel/libsigc++20/work/stage/usr/local/share/devhelp/books/libsigc++-2.0/libsigc++-2.0.devhelp2:No
such file or directory
*** Error code 74
Stop.
make[1]: stopped in /usr/ports/devel/libsigc++20
*** Error code 1
Stop.
make: stopped in /usr/ports/devel/libsigc++20
===>>> Installation of libsigc++-2.10.0 (devel/libsigc++20) failed
===>>> Aborting update
===>>> There are messages from installed ports to display,
but first take a moment to review the error messages
above. Then press Enter when ready to proceed.
===>>> pkg-message for perl5-5.24.1_1
Always:
The /usr/bin/perl symlink has been removed starting with Perl 5.20.
For shebangs, you should either use:
#!/usr/local/bin/perl
or
#!/usr/bin/env perl
The first one will only work if you have a /usr/local/bin/perl,
the second will work as long as perl is in PATH.
===>>> Done displaying pkg-message files
===>>> Upgrade of perl5-5.24.1 to perl5-5.24.1_1 complete
===>>> You can restart from the point of failure with this command line:
portmaster <flags> devel/libsigc++20
This command has been saved to /tmp/portmasterfail.txt
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list