This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
problems with libgcc.a
- To: egcs at cygnus dot com
- Subject: problems with libgcc.a
- From: Jochen Kuepper <jochen at uni-duesseldorf dot de>
- Date: Wed, 7 Jan 1998 11:05:46 +0100
- Reply-To: jochen at uni-duesseldorf dot de
*** egcs-1.0.1 on alphaev5-dec-osf4.0b ***
Hi,
I do have problems with multiple defined symbols from libgcc.a.
First I create a shared library, then I compile my program, which needs that library.
The only way it is working, is:
- link the library with
-nostdlib -lXext -lX11 -lstdc++ -lc
this gives me unresolved symbols in the library (the ones form libgcc.a)
- now I can link my program against that library, everything is fine.
Is there a good way to solve that problem ?
gcc-2.7.2 does not show that problem (but so many others).
How should I handle this ? Can I link the shared library againt libgcc in a way
that the symbols get resolved, but are not external ?
So I would include the code twice into programs, but well, I would prefer it
to the momentary solution.
Somehing different: Where do I find documetation on "-frepo" for egcs-1.0.1 ?
My program only links when using that flag on compilation; I would like to understand
why this is.
Greetings,
Jochen