#32174 closed defect (fixed)
gnudatalanguage install fails with "shell command failed"
Reported by: | bonomo@… | Owned by: | tenomoto (Takeshi Enomoto) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | Cc: | slayoo@… | |
Port: | gnudatalanguage |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
After all "dependencies" are installed, the installation of the package/port gnudatalanguage fails with a "shell command failed" error. I did not find the log file illuminating. Installation attempt on Mac Powerbook Pro (Intel) running Mac OS 10.5.8. Screen dialog:
Last login: Mon Nov 21 07:47:11 on console Aquinas-195:~ bonomo$ sudo port clean gnudatalanguage Password: Sorry, try again. Password: ---> Cleaning gnudatalanguage Aquinas-195:~ bonomo$ sudo port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.0.3 installed, MacPorts base version 2.0.3 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 Aquinas-195:~ bonomo$ sudo port install gnudatalanguage ---> Computing dependencies for curl-ca-bundle ---> Fetching archive for curl-ca-bundle ---> Attempting to fetch curl-ca-bundle-7.23.1_0.darwin_9.noarch.tbz2 from http://packages.macports.org/curl-ca-bundle ---> Fetching curl-ca-bundle ---> Attempting to fetch curl-7.23.1.tar.bz2 from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/curl ---> Verifying checksum(s) for curl-ca-bundle ---> Extracting curl-ca-bundle ---> Applying patches to curl-ca-bundle ---> Configuring curl-ca-bundle ---> Building curl-ca-bundle ---> Staging curl-ca-bundle into destroot ---> Installing curl-ca-bundle @7.23.1_0 ---> Cleaning curl-ca-bundle ---> Deactivating curl-ca-bundle @7.23.0_0 ---> Cleaning curl-ca-bundle ---> Activating curl-ca-bundle @7.23.1_0 ---> Cleaning curl-ca-bundle ---> Computing dependencies for curl ---> Fetching archive for curl ---> Attempting to fetch curl-7.23.1_0+ssl.darwin_9.i386.tbz2 from http://packages.macports.org/curl ---> Fetching curl ---> Verifying checksum(s) for curl ---> Extracting curl ---> Applying patches to curl ---> Configuring curl ---> Building curl ---> Staging curl into destroot ---> Installing curl @7.23.1_0+ssl ---> Cleaning curl ---> Computing dependencies for curl ---> Deactivating curl @7.23.0_0+ssl ---> Cleaning curl ---> Activating curl @7.23.1_0+ssl ---> Cleaning curl ---> Computing dependencies for gnudatalanguage ---> Fetching archive for gnudatalanguage ---> Attempting to fetch gnudatalanguage-0.9.2_0.darwin_9.i386.tbz2 from http://packages.macports.org/gnudatalanguage ---> Fetching gnudatalanguage ---> Verifying checksum(s) for gnudatalanguage ---> Extracting gnudatalanguage ---> Configuring gnudatalanguage ---> Building gnudatalanguage Error: Target org.macports.build returned: shell command failed (see log for details) Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> Aquinas-195:~ bonomo$
Attachments (3)
Change History (11)
Changed 13 years ago by bonomo@…
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | slayoo@… added |
---|---|
Description: | modified (diff) |
Keywords: | installation shell command failure removed |
Owner: | changed from macports-tickets@… to takeshi@… |
Changed 13 years ago by bonomo@…
Attachment: | main.2.log added |
---|
comment:2 Changed 13 years ago by bonomo@…
Hello! I am quite new at Macports, and am not yet familiar with the conventions (for example, in what manner to use WikiFormattin). How may I identify the maintainers of a port I have not yet installed? Is a list maintained on Macports? I was also suprised that MacPorts did not note the location of the log file. Please note this screen dump: * screen output *
Last login: Mon Nov 21 22:15:36 on console Aquinas-195:~ bonomo$ sudo port logfile gnudatalanguage Password: Sorry, try again. Password: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_gnudatalanguage/gnudatalanguage/main.log Aquinas-195:~ bonomo$ NOTE further screen output: Last login: Mon Nov 21 22:59:58 on ttys000 Aquinas-195:~ bonomo$ cd /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_gnudatalanguage/gnudatalanguage/ Aquinas-195:gnudatalanguage bonomo$ ls main.log Aquinas-195:gnudatalanguage bonomo$ less main.log Aquinas-195:gnudatalanguage bonomo$ pwd /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_gnudatalanguage/gnudatalanguage Aquinas-195:gnudatalanguage bonomo$ ls main.log Aquinas-195:gnudatalanguage bonomo$ Aquinas-195:gnudatalanguage bonomo$ cat main.log version:1 :debug:main epoch: in tree: 1 installed: 1 :debug:main autoconf 2.68_2 exists in the ports tree :debug:main autoconf 2.68_2 is the latest installed :debug:main autoconf 2.68_2 is active :debug:main Merging existing variants into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/autoconf :debug:main OS darwin/9.8.0 (Mac OS X 10.5) arch i386 :debug:main org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided :debug:main org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided
skipping to nearer the end....
:msg:clean ---> Activating curl-ca-bundle @7.23.1_0 :debug:clean Using /usr/bin/tar :debug:clean Using /usr/bin/bzip2 :info:clean ./ :info:clean ./+COMMENT :info:clean ./+CONTENTS :info:clean ./+DESC :info:clean ./+PORTFILE :info:clean ./+STATE :info:clean ./opt/ :info:clean ./opt/local/ :info:clean ./opt/local/share/ :info:clean ./opt/local/share/curl/ :info:clean ./opt/local/share/curl/curl-ca-bundle.crt :debug:clean activating directory: / :debug:clean activating directory: /opt :debug:clean activating directory: /opt/local :debug:clean activating directory: /opt/local/share :debug:clean activating directory: /opt/local/share/curl :debug:clean activating file: /opt/local/share/curl/curl-ca-bundle.crt :debug:main Executing org.macports.main (curl-ca-bundle) :debug:clean clean phase started at Mon Nov 21 07:50:33 CST 2011 :notice:clean ---> Cleaning curl-ca-bundle :debug:clean Executing org.macports.clean (curl-ca-bundle) :info:clean ---> Removing work directory for curl-ca-bundle :debug:clean Removing directory: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_curl-ca-bundle/curl-ca-bundle :debug:clean delete: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_curl-ca-bundle/curl-ca-bundle :debug:clean No work directory found to remove at /Users/bonomo/.macports/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_curl-ca-bundle/curl-ca-bundle :debug:clean Removing symlink: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/net/curl-ca-bundle/work :debug:clean delete: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/net/curl-ca-bundle/work :debug:clean Removing directory: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_curl-ca-bundle/curl-ca-bundle :debug:clean delete: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_curl-ca-bundle/curl-ca-bundle Aquinas-195:gnudatalanguage bonomo$ Aquinas-195:gnudatalanguage bonomo$ grep gnudatalanguage main.log Aquinas-195:gnudatalanguage bonomo$
end of screen output
The file main.log in the specified log directory is oddly unconcerned with gnudatalanguage. I believe this is indeed the file I had attached earlier. I am re-attaching it, from the noted directory.
BTW, I downloaded gnudatalanguage -- a number of days before I started attempting to put in on an Intel Mac -- onto a G5 tower running MacOS 10.5.8 without any incident at all.
Rich
comment:3 Changed 13 years ago by bonomo@…
Ah! I have finally realized how to identify the maintainer. Thank you for adding him to the cc list.
Changed 13 years ago by bonomo@…
Attachment: | main.3.log added |
---|
comment:4 Changed 13 years ago by bonomo@…
I ran "sudo port clean curl-ca-bundle", and tried to re-install curl-ca-bundle. I got some strange messages, but it seems to have installed. I attempted to clean and reinstall gnudatalanguage and had the same failure as before. I think did another cycle of clean and re-install of gnudatalanguage, this time with the -d option. This led to more useful results. The log file is posted.
comment:5 Changed 13 years ago by tenomoto (Takeshi Enomoto)
I looked at the log. The linker seems to have a problem finding cm2in defined in DevicePS class in deviceps.hpp. This header is included from graphics.cpp so it should be available. I need a few days to set up a clean Leopard installation, which is no longer officially supported.
comment:6 Changed 13 years ago by gnw3
I have the same error for gnudatalanguage on Leopard (intel) using "sudo port upgrade outdated". As an experiment, I deleted src/gdl-graphics.o
and tried:
make CXXFLAGS='-m32 -O2' LDFLAGS='-L/opt/local/lib -m32 -L/opt/local/lib -L/opt/local/lib -L/opt/local/lib -L/opt/local/lib' CXX=/opt/local/bin/g++-mp-4.6
Then did "sudo install gnudatalanguage
". The program runs, but I don't have time to test further.
comment:7 Changed 13 years ago by tenomoto (Takeshi Enomoto)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Committed in r87602.
Please remember to use WikiFormatting and to Cc the maintainer(s) of the affected port.
The main.log you attached has nothing to do with gnudatalanguage; it's about curl-ca-bundle. Please attach gnudatalanguage's main.log so we can see what went wrong. The command:
should show you where it is. I am confused that your screen output above does not include the location of the logfile. MacPorts should have printed that.