Very Computer

by **M.L. Ton** » Mon, 12 Mar 2001 03:15:19

Hello,

I'm using Linux and gcc.

I've created a static library, say libx.a, containing the following
file,

/* errorlog.c begins */
...
extern int debug;
...
/* errorlog.c ends */

And there is some other file, say afile.c, that has nothing to do with
the 'debug' variable.

When I 'gcc afile.c libx.a', it does compile and works fine.

But now I turn the library into a shared library, say libx.so.1.0,
and when I 'gcc afile.c libx.so.1.0', the linker complains,

libx.so.1.0: undefined reference to `debug'
collect2: ld returned 1 exit status

How do I solve this?

Thanks.

by **M?ns Rullg?** » Tue, 13 Mar 2001 17:32:17

> Hello,

> I'm using Linux and gcc.

> I've created a static library, say libx.a, containing the following
> file,

> /* errorlog.c begins */
> ...
> extern int debug;
> ...
> /* errorlog.c ends */

> And there is some other file, say afile.c, that has nothing to do with
> the 'debug' variable.

> When I 'gcc afile.c libx.a', it does compile and works fine.

> But now I turn the library into a shared library, say libx.so.1.0,
> and when I 'gcc afile.c libx.so.1.0', the linker complains,

> libx.so.1.0: undefined reference to `debug'
> collect2: ld returned 1 exit status

> How do I solve this?

> Thanks.

The problem is the keyword extern. 'extern' means that the variable
'debug' is defined in some other file, to be linked with later. Also,
when linking with libraries you should use 'gcc -l<library>'.

--
M?ns Rullg?rd

Very Computer

static lib works fine, but why not the shared lib version

static lib works fine, but why not the shared lib version

static lib works fine, but why not the shared lib version