[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: printing problems because of memory consumption of gs
From: |
Daniel J Sebald |
Subject: |
Re: printing problems because of memory consumption of gs |
Date: |
Sun, 04 Jan 2015 19:47:24 -0600 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 01/04/2015 04:07 PM, Daniel J Sebald wrote:
The problems I'm having stem from failure to build documentation, such
as the following example:
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed:
(connection->initialization_error == NULL)
octave exited with signal 6
../../run-octave -f -q -H -p
/home/sebald/octave/octave/octave/doc/interpreter --eval "splineimages
('splinefit1', 'pdf');"
I am building the executable outside the source tree, and the account
doing the building doesn't have the GUI framework active (i.e., gnome).
Hence the "GLib-GIO:ERROR:gdbusconnection.c" error. If I activate the
GUI framework, then all compilation passes and the "help xyz" now works.
I'm inclined to think of that as a bug. That is, building and
installing shouldn't require an active GUI toolkit or framework. What
if some system maintainer wants to remotely login and build/install octave?
Something else I notice is that "make install" seems to take much longer
than it once did. I've separated the stdout and stderr messages. Here
are the warnings:
Makefile:2764: warning: overriding recipe for target `check'
Makefile:2331: warning: ignoring old recipe for target `check'
Makefile:2764: warning: overriding recipe for target `check'
Makefile:2331: warning: ignoring old recipe for target `check'
libtool: install: warning: relinking `liboctinterp.la'
libtool: install: warning: relinking `dldfcn/__delaunayn__.la'
libtool: install: warning: relinking `dldfcn/__dsearchn__.la'
libtool: install: warning: relinking `dldfcn/__eigs__.la'
libtool: install: warning: relinking `dldfcn/__fltk_uigetfile__.la'
libtool: install: warning: relinking `dldfcn/__glpk__.la'
libtool: install: warning: relinking `dldfcn/__init_fltk__.la'
libtool: install: warning: relinking `dldfcn/__init_gnuplot__.la'
libtool: install: warning: relinking `dldfcn/__magick_read__.la'
libtool: install: warning: relinking `dldfcn/__voronoi__.la'
libtool: install: warning: relinking `dldfcn/amd.la'
libtool: install: warning: relinking `dldfcn/ccolamd.la'
libtool: install: warning: relinking `dldfcn/chol.la'
libtool: install: warning: relinking `dldfcn/colamd.la'
libtool: install: warning: relinking `dldfcn/convhulln.la'
libtool: install: warning: relinking `dldfcn/dmperm.la'
libtool: install: warning: relinking `dldfcn/fftw.la'
libtool: install: warning: relinking `dldfcn/qr.la'
libtool: install: warning: relinking `dldfcn/symbfact.la'
libtool: install: warning: relinking `dldfcn/symrcm.la'
libtool: install: warning: relinking `dldfcn/tsearch.la'
libtool: install: warning: relinking `liboctgui.la'
Makefile:2764: warning: overriding recipe for target `check'
Makefile:2331: warning: ignoring old recipe for target `check'
Makefile:2764: warning: overriding recipe for target `check'
Makefile:2331: warning: ignoring old recipe for target `check'
Makefile:2497: warning: overriding recipe for target `check'
Makefile:2091: warning: ignoring old recipe for target `check'
Makefile:2497: warning: overriding recipe for target `check'
Makefile:2091: warning: ignoring old recipe for target `check'
Makefile:2497: warning: overriding recipe for target `check'
Makefile:2091: warning: ignoring old recipe for target `check'
Makefile:2764: warning: overriding recipe for target `check'
Makefile:2331: warning: ignoring old recipe for target `check'
Makefile:2764: warning: overriding recipe for target `check'
Makefile:2331: warning: ignoring old recipe for target `check'
The peculiar thing is that "make install" has the following message in
its trace twice:
Octave successfully built. Now choose from the following:
./run-octave - to run in place to test before installing
make check - to run the tests
make install - to install (PREFIX=/usr/local)
From what I can tell, it happens with the "/interpreter" subdirectory
in both locations. It's as though the trace is exactly the same in two
locations.
Dan