Opened 12 years ago

Closed 11 years ago

#36010 closed defect (worksforme)

ghostscript upgrade failing

Reported by: bpabbott@… Owned by: takanori@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: ghostscript

Description (last modified by ryandesign (Ryan Carsten Schmidt))

After a selfupdate upgrading ghostscript fails with automake 1.12, but succeeds after automake @1.11.5_0 is activated.

$ port installed automake
The following ports are currently installed:
  automake @1.11.1_0
  automake @1.11.2_0
  automake @1.11.3_0
  automake @1.11.5_0
  automake @1.12_0
  automake @1.12.1_0
  automake @1.12.2_0
  automake @1.12.3_0 (active)

$ sudo port upgrade pstoedit
--->  Computing dependencies for ghostscript
--->  Fetching archive for ghostscript
--->  Attempting to fetch ghostscript-9.06_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/ghostscript
--->  Attempting to fetch ghostscript-9.06_1.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/ghostscript
--->  Fetching distfiles for ghostscript
--->  Verifying checksum(s) for ghostscript
--->  Extracting ghostscript
--->  Applying patches to ghostscript
--->  Configuring ghostscript
Error: org.macports.configure for port ghostscript returned: autoreconf failure: command execution failed
Please see the log file for port ghostscript for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

Activating automake @1.11.5_0 fixes the problem.

$ sudo port activate automake @1.11.5_0
--->  Computing dependencies for automake
--->  Deactivating automake @1.12.3_0
--->  Cleaning automake
--->  Activating automake @1.11.5_0
--->  Cleaning automake
Bens-MacBook-Pro:Development bpabbott$ sudo port upgrade ghostscript--->  Computing dependencies for ghostscript
--->  Configuring ghostscript
--->  Building ghostscript
--->  Staging ghostscript into destroot
--->  Installing ghostscript @9.06_1
--->  Cleaning ghostscript
--->  Computing dependencies for ghostscript
--->  Deactivating ghostscript @9.05_2
--->  Cleaning ghostscript
--->  Activating ghostscript @9.06_1
--->  Cleaning ghostscript
... <snip> ...

Ben

Attachments (2)

main.log (23.9 KB) - added by bpabbott@… 12 years ago.
config.log (7.3 KB) - added by bpabbott@… 12 years ago.
ghostscript config.log

Download all attachments as: .zip

Change History (12)

comment:1 Changed 12 years ago by bpabbott@…

Cc: bpabbott@… added

Cc Me!

comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added; bpabbott@… removed
Description: modified (diff)
Owner: changed from macports-tickets@… to takanori@…

Please remember to use WikiFormatting.

ghostscript built fine for me with automake 1.12.3. Please attach the main.log file which shows how it failed for you.

comment:3 in reply to:  description Changed 12 years ago by bpabbott@…

I've tried to duplicate the failure so that I might attach the log, but was unsuccessful ... which I suppose is good news.

A new MacPorts user has mentioned the same failure in an email to me. I've asked him to either email me his log file or to post it here.

Changed 12 years ago by bpabbott@…

Attachment: main.log added

comment:4 Changed 12 years ago by bpabbott@…

I've attached the log file from another user (Jon Feldman <jon@…>)

comment:5 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

The log shows:

:info:configure configure: error: C compiler cannot create executables
:info:configure See `config.log' for more details

There are several common reasons why the compiler would be unable to create executables, and we would need to see the config.log file to figure out which one applies in this case.

Changed 12 years ago by bpabbott@…

Attachment: config.log added

ghostscript config.log

comment:6 Changed 12 years ago by bpabbott@…

Jon Feldman emailed me his config.log. I've just attached it.

comment:7 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

The error shown in the config.log is:

configure:2990: /Developer/usr/bin/gcc-4.2 -pipe -O2 -arch x86_64 -isystem/opt/local/include -L/opt/local/lib -arch x86_64 conftest.c  >&5
ld: library not found for -lcrt1.10.6.o

Based on some Google searching, this suggests to me that the command line tools are not properly installed. How you install them depends on what version of Xcode you have. With Xcode 3 and earlier, you have to select the correct option in the installer. With Xcode 4.0 through 4.2 I believe, you have to download the command line tools separately from Apple Developer Connection. With Xcode 4.3 and up, you can do that, or you can use the Downloads section of the Xcode program's Preferences window.

comment:8 Changed 12 years ago by jon@…

So I re-installed the Xcode 3.2.6 System Tools and UNIX Development, re-installed octave using 'sudo port install octave-devel' and everything compiled successfully. I am successfully running Octave 3.6.2, but I get the warning "warning: no graphical display found". I tried running xterm first and then running octave from within the xterm window but that didn't work either. I'm sorry, I'm a newbie. Could someone please explain how to get graphical output using Octave? I'm sure there's something simple that I'm missing. Thanks

comment:9 Changed 12 years ago by bpabbott@…

Jon,

Run gnuplot and try some tests.

$ gnuplot
gnuplot> set term x11
Terminal type set to 'x11'
Options are ' nopersist'
gnuplot> plot sin(x)
gnuplot> set term aqua
Terminal type set to 'aqua'
Options are '0 title "Figure 0" size 846,594 font "Times-Roman,14" noenhanced solid'
gnuplot> plot sin(x)
gnuplot> quit

If everything works, then run the MacPorts version of Octave and type ...

system ("which gnuplot")

... and tell us what it returns.

If it finds /opt/local/bin/gnuplot, try running gnuplot from Octave.

setenv GNUTERM aqua
[status, output] = system ('gnuplot -e "plot sin(x)" --persist')
status = 0
output = 

That should produce a plot and return "status" and "output". Tell us what "status" and "output" return.

Next try x11 ...

setenv GNUTERM x11
[status, output] = system ('gnuplot -e "plot sin(x)" --persist')
status = 0
output = 

... and tell us what "status" and "output" return.

comment:10 Changed 11 years ago by jmroot (Joshua Root)

Resolution: worksforme
Status: newclosed
Note: See TracTickets for help on using tickets.