[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: Installation problem - from source - SuSE 10.0 to AMD Athalon 64 300+

At 14:16 10-2-2006, you wrote: 
> Hi - I'm trying to install the gEDA package from source on a computer
> running SuSE 10.0. I'm compiling from source rather than installing
> from RPMs because I've got an AMD 64 processor.
>
> I downloaded geda-install-20060124.iso from the gEDA download page,
> wrote it to a CD, installed the extra packages from the SuSE DVD then
> installed gEDA  into /user/local/gEDA, which appeared to work, but
> while some of the executables - at /usr/local/gEDA/bin - would
> execute, gschem wouldn't
>
> I then tried installing gschem from within the
> /usr/local/gEDA/geschem directory,by typing "./configure" - which
> appeared to work, followed by "make install" which didn't.
>
> I've cut and attached the error messages from this failed attempt,
> starting at "g_funcs.o: In function `g_funcs_print':
> ../noweb/g_funcs.nw:92: undefined reference to `f_print'" which look
> as if they would be informative to someone higher in the Linux
> pecking order than I am.
>
This seems to be missing libgeda library.

The libgeda library seemed to install flawlessly, not that I've tried to get it to execute.

You should install software in following order:
1. build and install libgdeda
2.  build and install libgeda
3. build and install geda-symbols
4. build and install everthing else

I installed from the geda-install-20060124.iso image on a CD-ROM, which should have got the order right. For various reasons, I'd preceded that by installing the libgeda and geda-symbols in their own directories, followed by a first attempt to install gschem from it's directory (libdgeda wasn't listed at all in the release notes - at least not in the section giving the preferred order of installation).

If my skipping the libgdeda installation did create this problem, what do I need to do to get around it? Deleting the /usr/loca/gEDA directory is a perfectly feasible option - I could re-install everything from the CD-ROM in a bout half an hour.

If you have RPMs for your distribution but for other architecture (i386
instead of x86_64 or so) then try to rebuild binary packages from source
packages. Sometimes  even looking into the specfile may help much since some
tricks (and patches) are there.
gEDA software builds correctly on 64-bit Fedora


As I said, I explicitly chose to build from source.

--
Bill Sloman, Nijmegen