[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gcc3.1 on Redhat 7.3
From: |
Stefan Böhringer |
Subject: |
Re: gcc3.1 on Redhat 7.3 |
Date: |
27 May 2002 18:41:17 +0200 |
Thanks so far and sorry for not RTFM.
I have carefully removed all remnants from gcc2.96 libobjc and the 3.1
lib is in place. I now come up with the following for any app I try to
launch with openapp:
$ openapp Ink.app
/Disks/ext/src/gnustep/gnustep/usr-apps/examples/gui/Ink/Ink.app/ix86/linux-gnu/gnu-gnu-gnu/Ink:
Uncaught exception NSInternalInconsistencyException, reason: read unknown type
info - 0
Thanks,
Stefan
On Mon, 2002-05-27 at 07:35, e.sammer wrote:
> Stefan Böhringer wrote:
> > However only a static libobjc is generated (libobjc.a; also libobjc.la
> > is produced: what is this for?).
>
> The libobjc.la file is produced by ltmain.sh (automake / libtool) and
> used by libtool to make linking easier for itself. It keeps some meta
> information about the library and a way for libtool to find libraries
> and the like. Generally, you do not need to change or touch these files.
>
> > Does anybody know how to force a shared
> > library in the gcc compilation process?
>
> When you configure gcc, add the option '--enable-shared' which will make
> all support libraries (libobjc, libgcc_s, libstdc++, etc.) shared. Keep
> in mind that sometimes 'configure --help' does not show all of the
> options available because it calls other configure scripts internally.
> In other words, you should always read the install docs no matter what.
>
> Hope that helps...