Re: gEDA-dev: Intalling repo code on Ubuntu 8.10

[Stuart Brorson <sdb-at-NOSPAMcloud9_dot_net>]

> So I go into gaf/gschem and look into the config.log file and it shows:
>
> configure:7603: $PKG_CONFIG --exists --print-errors "libgeda >=
> $DATE_VERSION"
> Package libgeda was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libgeda.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'libgeda' found
> configure:7606: $? = 1
> configure:7621: $PKG_CONFIG --exists --print-errors "libgeda >=
> $DATE_VERSION"
> Package libgeda was not found in the pkg-config search path.
> Perhaps you should add the directory containing `libgeda.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'libgeda' found
> configure:7624: $? = 1
> No package 'libgeda' found
> configure:7652: result: no
> configure:7669: error: libgeda detection error: No package 'libgeda' found
>
> I checked to see where libgeda.pc is on my file system and it is in
> /usr/local/geda/lib/pkgconfig which is on my PKG_CONFIG_PATH.
>
> I am at a total impass at this point so if anyone has further
> suggestions, I am all ears.

Note that pkg-config not only looks for libgeda, but also checks the
version and barfs if the version of libgeda found is incorrect.  Some
suggestions:

*  Run pkg-config from the command line and see what results.  Here's
the magic command:

pkg-config --modversion libgeda

If the version reported is different from the one you think it is,
then either your libgeda hasn't been updated in your build for some
reason, or your PKG_CONFIG_PATH has a different libgeda somewhere
earlier in the search path.

* You can also look inside your .so to see what version it is using
brute force.  In your lib directory do this:

strings libgeda.so | grep 200

This will print out any strings with a "200" in them, including the
date code.  Ignore the other spew; the date code (something like
20070708 or hopefully later) is what you want.

If you have the wrong libgeda, then try nuking the lib directory under
the target (or maybe just the entire target directory tree) and
doing a full rebuild.

HTH,

Stuart


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