Re: [ooc-compiler] Installation problems on Fedora Core 3

[Michael v. A. <Mic...@de...>]

August <fus...@co...> writes:

> Hello all,
> 
> I have some trouble installing OOC 2.1.7 on Fedora Core 3 Linux. I have
> installed gc6.3 and it seems to work. Any clues?

This problem seems to be a duplicate of a report I got early
December.  Which means that I can duplicate my past answer as well :-)

| Subject: Re: Problems Installing on Fedora Core 3
| References: <110...@cp...>
| From: Michael van Acken <mv...@us...>
| Date: 03 Dec 2004 17:33:57 +0100
| 
| Gregory Gelfond <xx...@yy...> writes:
| 
| > Hello,
| > 
| > I am attempting to install the latest version of oo2c on Fedora Core 3.
| > I already have gc and glibtool installed, and I get an error message
| > when attempting to run the following command:
| > 
| > env "CFLAGS=-O2 -pipe" ./configure
| > 
| > Here are the messages I am getting from configure:
| > 
| > checking for gcc... gcc
| > [...]
| > checking for GC_malloc in -lgc... yes
| 
| It looks like this is a lie, because your config.log says
| 
| configure:4359: ./conftest
| ./conftest: error while loading shared libraries: libgc.so.1: cannot open shared object file: No such file or directory
| 
| You should take a look at the shared library files for gc and check if
| a required link is missing.  On my Debian setup, libgc looks like
| this:
| 
| ~$ ls -l /usr/lib/libgc.*
| -rw-r--r--  1 root root 164912 Mar 26  2002 /usr/lib/libgc.a
| lrwxrwxrwx  1 root root     12 Mar 13  2004 /usr/lib/libgc.so -> libgc.so.6.0
| lrwxrwxrwx  1 root root     12 Mar 13  2004 /usr/lib/libgc.so.6 -> libgc.so.6.0
| -rw-r--r--  1 root root 117540 Mar 26  2002 /usr/lib/libgc.so.6.0
| 
| If these files are fine: There are many ways in which a shared library
| installation may be broken: wrong or missing links, wrong or stale
| search paths, permissions, locations, etc.
| 
| Hope this helps.

In reply to this, I got the message that "Copying the gc library files
to /usr/lib rather than /usr/local/lib fixed the problem."

What the real reason for the link failure was I do not know.

-- mva