Opened 12 years ago
Closed 11 years ago
#35755 closed defect (worksforme)
evince @2.30.3 build failure
Reported by: | Jacques.Laminie@… | Owned by: | dbevans (David B. Evans) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.2 |
Keywords: | Cc: | ||
Port: | evince |
Description (last modified by neverpanic (Clemens Lang))
new-host:~ jlam$ sudo port selfupdate Password: ---> Updating MacPorts base sources using rsync MacPorts base version 2.1.2 installed, MacPorts base version 2.1.2 downloaded. ---> Updating the ports tree ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated new-host:~ jlam$ sudo port upgrade outdated Password: ---> Computing dependencies for policykit ---> Fetching archive for policykit ---> Attempting to fetch policykit-0.103_2.darwin_10.x86_64.tbz2 from http://packages.macports.org/policykit ---> Attempting to fetch policykit-0.103_2.darwin_10.x86_64.tbz2.rmd160 from http://packages.macports.org/policykit ---> Installing policykit @0.103_2 ---> Cleaning policykit ---> Computing dependencies for policykit ---> Deactivating policykit @0.103_1 ---> Cleaning policykit ---> Activating policykit @0.103_2 ---> Cleaning policykit ---> Computing dependencies for evince ---> Building evince Error: org.macports.build for port evince returned: command execution failed Please see the log file for port evince for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_evince/evince/main.log Error: Unable to upgrade port: 1 To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets new-host:~ jlam$
Attachments (1)
Change History (7)
Changed 12 years ago by Jacques.Laminie@…
comment:1 Changed 12 years ago by neverpanic (Clemens Lang)
Description: | modified (diff) |
---|---|
Keywords: | evince removed |
Owner: | changed from macports-tickets@… to devans@… |
Port: | evince added; vince removed |
comment:2 Changed 12 years ago by neverpanic (Clemens Lang)
Description: | modified (diff) |
---|
It seems there's a problem with python, because the logfile says
:info:build /bin/sh: /opt/local/bin/xml2po: /opt/local/bin/python2.7: bad interpreter: No such file or directory
Cleaning and re-running configure should pick up a version of python that works. If it doesn't a dependency on python27 should probably be added to the evince port.
comment:3 Changed 12 years ago by neverpanic (Clemens Lang)
Actually, /opt/local/bin/xml2po
from the gnome-doc-utils
port specifies an interpreter of /opt/local/bin/python2.7
that's not where it should be.
The evince
port has a dependency on gnome-doc-utils
, which has a library dependency on python2.7
, which should provide /opt/local/bin/python2.7
. Do you have python27
installed? What do
port -v installed python27 # and port contents python27 | grep 'python2.7$'
print?
comment:4 Changed 12 years ago by jmroot (Joshua Root)
Summary: | Error: org.macports.build for port evince returned: command execution failed → evince @2.30.3 build failure |
---|
comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Is this still a problem? If so please answer the questions above.
comment:6 Changed 11 years ago by dbevans (David B. Evans)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I think this is probably irrelevant since the current version of evince is now 3.10.3. Please update your ports tree if you haven't already and if you have any problems with the current version, submit a new ticket with the appropriate details.
Since the new port works well for me, I am closing this ticket with that status.
Please use WikiFormatting and remember to cc/assign to the maintainer, if any.
Your logfile shows your build of evince was not a clean attempt:
Please run
and try again. Attach the new main.log, if it fails again.