gEDA-user: gschem cvs repo issue FC6

[Craig Niederberger]

Thanks super, Stuart.  I discovered that export
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/opt/geda/lib was haunting my system, and
sure enough, upon removal of that def, the yum install for gschem now
works.  But being the inquisitive "cvs repo I'd like to use the geda part"
that I am, I'd *still* like to be able to compile the repo for geda/gaf for
FC6 that I did for FC5 (which annoyingly still happily works).  What I don't
understand is this: if I set

# export LD_LIBRARY_PATH=/opt/geda/lib:$LD_LIBRARY_PATH
# export PATH=/opt/geda/bin:${PATH}
# export PKG_CONFIG_PATH=/opt/geda/lib/pkgconfig:$PKG_CONFIG_PATH

as instructed by the make script, why doesn't

# make
# export LD_LIBRARY_PATH=/opt/geda/lib:$LD_LIBRARY_PATH
# export PATH=/opt/geda/bin:${PATH}
# export PKG_CONFIG_PATH=/opt/geda/lib/pkgconfig:$PKG_CONFIG_PATH
# make install

work?

Especially since /opt/geda/lib is happily populated by
libgeda.a  libgeda.la  libgeda.so  libgeda.so.28  libgeda.so.28.0.0
pkgconfig

??

Many TIA,
Craig



On 5/6/07, Stuart Brorson <sdb at cloud9.net> wrote:
>
> On Sun, 6 May 2007, Craig Niederberger wrote:
>
> > ...and ironically enough, trying to yum install geda-* on this FC6
> system,
> > installs just fine, but
> >
> > $ gschem &
> > [1] 18029
> > [craign at localhost archive]$ gEDA/gschem version 20070216
> > gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more
> details.
> > This is free software, and you are welcome to redistribute it under
> certain
> > conditions; please see the COPYING file for more details.
> >
> >
> > [1]+  Segmentation fault      gschem
>
> This happens when you have a version of libgeda already installed on
> your box, then you install a different version of gEDA.  Running the
> second version of gschem finds the first version of libgeda when
> you run it, causing an immediate segfault.
>
> You need to clean out the cruft left behind from previous gEDA
> installations, then re-install.
>
> > I'd love to be able to get the cvs repo install working, anyone have any
> > ideas about
> > configure: error: libgeda detection error: No package 'libgeda' found
>
> Yes, you need to set some environment variables before you try to
> build gEDA.  Here's the helpful spew generated by "make":
>
> ----------------------  <spew>  ------------------------
> Before executing any of the above targets, set the below shell
> variables.  The build process _will fail_ if you do not set
> these variables!  You will also need to set these variables to
> run the programs.
>
> gEDA/gaf will be installed into /usr/local/geda
>
> For vanilla bourne shells:
> LD_LIBRARY_PATH=/usr/local/geda/lib:$LD_LIBRARY_PATH
> export LD_LIBRARY_PATH
> PATH=/usr/local/geda/bin:${PATH}
> export PATH
> PKG_CONFIG_PATH=/usr/local/geda/lib/pkgconfig:$PKG_CONFIG_PATH
> export PKG_CONFIG_PATH
>
> For bash:
> export LD_LIBRARY_PATH=/usr/local/geda/lib:$LD_LIBRARY_PATH
> export PATH=/usr/local/geda/bin:${PATH}
> export PKG_CONFIG_PATH=/usr/local/geda/lib/pkgconfig:$PKG_CONFIG_PATH
>
> For csh/tcsh shell:
> setenv LD_LIBRARY_PATH /usr/local/geda/lib:$LD_LIBRARY_PATH
> setenv PATH /usr/local/geda/bin:$PATH
> setenv PKG_CONFIG_PATH /usr/local/geda/lib/pkgconfig:$PKG_CONFIG_PATH
> ----------------------  </spew>  ------------------------
>
> Finally, I'd say that you should get rid of old gEDA sos and
> executables before trying a new install.  Besides the place where you
> tried to install the build you make, make sure you look into /lib,
> /usr/lib, and /usr/local/lib to find and remove any old gEDA files.
>
> HTH,
>
> Stuart
>
>
> _______________________________________________
> geda-user mailing list
> geda-user at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.seul.org/pipermail/geda-user/attachments/20070506/f585b731/attachment-0001.html