Re: gEDA-user: Building from sources

[Daniel Wisehart <dw@xxxxxxxxxxxxx>]

On Sunday 12 February 2006 05:59, Stuart Brorson wrote:
> Well, the documentation needs updating then.  What you download from
> CVS is the developer's package, and you need to run the autotools to
> build configure.  The CVS distribution doesn't have configure built
> yet.  The build proceeds like this:
>
> 1.  make reconfig  =>  this runs autogen in every directory in a
> particular order.
>
> 2.  make config  => this runs ./configure in every directory.
>
> 3.  make install  =>  this does "make && make install" every
> directory.  The order in which you build the various packages is
> important.  That's why Ales created a top level Makefile to manage the
> process.  I belive the symbol files are created & installed first,
> then libgeda.  Afterwards, gschem and gnetlist may be built.

Thanks, Stuart.  By setting the environment variables before 'make config', 
make config ran just fine.  But 'make install' is failing in the same place.


> Check your PKG_CONFIG_PATH variable.  Verify that it points to a
> directory holding the file libgeda.pc.

It does.


> Also verify that you don't have an older version of libgeda (and
> libgeda.pc) hangning around in the PKG_CONFIG_PATH before the new
> libgeda.pc.  A common problem is that your PKG_CONFIG_PATH points to
> the wrong, obsolete libgeda.pc.  That's one reason I always recommend
> that you delete your old gEDA installation before trying to build a
> new one.  Or at least move the directory it lives in off of any search
> path.

I do not.


> Another thought:  Do you have pkg-config installed?  What version?

Yes; 0.15.0.


> Finally, if all this fails, nuke your source directory, re-download
> geda-dev from CVS, and try again, starting from "make reconfig".  Make
> sure your PKG_CONFIG_PATH is clean before trying again.

Running now...

Daniel