On Fri, Aug 19, 2005 at 11:29:26PM +0300, Giorgos Keramidas wrote:
: On 2005-08-19 21:26, Jonathon McKitrick <[EMAIL PROTECTED]> wrote:
: >
: > Got it! I recalled something des or phk wrote me a while ago, then I
skimmed
: > the manpage again. I have to put the .a files AFTER the object files wh
On 2005-08-19 21:26, Jonathon McKitrick <[EMAIL PROTECTED]> wrote:
>
> Got it! I recalled something des or phk wrote me a while ago, then I skimmed
> the manpage again. I have to put the .a files AFTER the object files where
> the unresolved symbol is found.
Ah! Yes, of course. I didn't realiz
On 2005-08-19 21:19, Jonathon McKitrick <[EMAIL PROTECTED]> wrote:
>On Fri, Aug 19, 2005 at 11:14:40PM +0300, Giorgos Keramidas wrote:
>: > Doesn't ld *statically* link code from .a archives?
>:
>: 'statically' is such an overloaded term I prefer to avoid using it.
>:
>: The C linker will include t
On Fri, Aug 19, 2005 at 11:14:40PM +0300, Giorgos Keramidas wrote:
: On 2005-08-19 21:03, Jonathon McKitrick <[EMAIL PROTECTED]> wrote:
: >On Fri, Aug 19, 2005 at 10:47:48PM +0300, Giorgos Keramidas wrote:
: >: # flame:/tmp/jcm-lib/foobar$ LD_LIBRARY_PATH=`pwd`/../libbar ./foobar
: >: # libfoo init
On Fri, Aug 19, 2005 at 11:14:40PM +0300, Giorgos Keramidas wrote:
: > Doesn't ld *statically* link code from .a archives?
:
: 'statically' is such an overloaded term I prefer to avoid using it.
:
: The C linker will include the body of functions defined in non-shared
: libraries into every share
On 2005-08-19 21:03, Jonathon McKitrick <[EMAIL PROTECTED]> wrote:
>On Fri, Aug 19, 2005 at 10:47:48PM +0300, Giorgos Keramidas wrote:
>: # flame:/tmp/jcm-lib/foobar$ LD_LIBRARY_PATH=`pwd`/../libbar ./foobar
>: # libfoo initialized at 0x80062a8a0
>: # libbar initialized at 0x4004e4
>: # flame:/tmp/
On Fri, Aug 19, 2005 at 10:47:48PM +0300, Giorgos Keramidas wrote:
: # flame:/tmp/jcm-lib/foobar$ LD_LIBRARY_PATH=`pwd`/../libbar ./foobar
: # libfoo initialized at 0x80062a8a0
: # libbar initialized at 0x4004e4
: # flame:/tmp/jcm-lib/foobar$
Hmmm. I'm using my own makefile setup rather than the
On 2005-08-19 20:13, Jonathon McKitrick <[EMAIL PROTECTED]> wrote:
>
> I have a binary that links to a shared object library. That .so calls a
> routine in an archive library (.a). When I link the main app with -lar-a it
> works fine, even though the function is actually called in the .so. But w
I have a binary that links to a shared object library. That .so calls a
routine in an archive library (.a). When I link the main app with -lar-a it
works fine, even though the function is actually called in the .so. But when
I link the .so with -lar-a, the linker doesn't resolve the symbol!
So
