Re: gEDA-user: Upgrading gEDA

["Mike Jarabek" <mjarabek@xxxxxxxxx>]

Hi,

Karel Kulhavy <clock@xxxxxxxxxxxxx> said:

> I had an old installation of gEDA that segfaulted every 5 minutes. I have 
been
> told to upgrade. So I downloaded gschem and it complained about libgeda so 
I
> downloaded libgeda. Compiled and installed libgeda and compiled and 
installed
> gschem. Now gschem doesn't segfault but generates invalid postscript so I
> cannot update the Ronja website because every time I type "make rsync", it
> ends up with an error message during compilation of the schematic into a 
PNG
> through postscript.

This should have worked, unless your system-gschemrc file or one of the 
other system scheme files has gotten corrupted.

> 
> I have been told that this is because something in my installation of gEDA
> is screwed.

Can you run your scripts and retreive the log file that gschem creates when 
you print?  If there is a problem finding the prolog file then there should 
be a message to that effect in the log file.  The postscript file you posted 
is missing the prolog, which gets copied from the geda data directory 
verbatim into the postscript output.  You should have a file 
called 'prolog.ps' somewhere under $prefix/share/gEDA.  This piece of 
postscript is where 'GEDAFont' gets defined. ($prefix is the what you 
supplied to ./configure when you built gschem and libgeda as --prefix=<some 
path>)

Do you have the gedadata enviroment variable set?  If so, perhaps it is 
pointing at an old installation of the system-rc files.  There is a command 
in the current startup guile scripts that sets the path and filename for the 
prolog file.  If this command is missing, because of gschem reading an old 
version of the startup script, then gschem will behave as you have shown.  
Verify in the log file that the system guile files that are being read are 
the ones that you most recently installed, especially if you have used a 
different prefix for your latest installation, compared to the old 
installation. Use the 'find' (or 'locate' if it's available) command on your 
system to find all the copies of the system-gschem files.  If you have more 
than one copy, then you have multiple installations of the tool, and this 
may be the source of your grief, especially if one of the installations 
lives under /usr/ or /, as the shared libraries there will get loaded if the 
LD_LIBRARY_PATH is not set correctly, or you have edited ld.so.conf.

Mike



-- 
--------------------------------------------------
                              Mike Jarabek
                                FPGA/ASIC Designer
   http://www.istop.com/~mjarabek
--------------------------------------------------




_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user