Hi, all

I try to compile my program with chmlib.
There're chmlib.so and chmlib.a under /usr/lib. I find a wierd problem, when I compile my program, the compiler uses chmlib.so, and the compilation is successful.
But what I want is too compile it with chmlib.a so that the executable will be independent with chmlib.so. So I delete the chmlib.so and the compiler try to compile with chmlib.a, the following errors occur:

/usr/local/lib/libchm.a(chm_lib.o)(.text+0x3b1): In function `chm_set_param':
src/chm_lib.c:1034: undefined reference to `__moddi3' /usr/local/lib/libchm.a(chm_lib.o)(.text+0xba6): In function `_chm_decompress_block':
src/chm_lib.c:1387: undefined reference to `__umoddi3' /usr/local/lib/libchm.a(chm_lib.o)(.text+0xd4b):src/chm_lib.c:1454: undefined reference to `__umoddi3'
/usr/local/lib/libchm.a(chm_lib.o)(.text+0xf86): In function `chm_retrieve_object':
src/chm_lib.c:1500: undefined reference to `__udivdi3' /usr/local/lib/libchm.a(chm_lib.o)(.text+0xf9c):src/chm_lib.c:1501: undefined reference to `__umoddi3'
/usr/local/lib/libchm.a(chm_lib.o)(.text+0xff8):src/chm_lib.c:1509: undefined reference to `__umoddi3'
Error: Error while linking
Error: /usr/bin/ppc386 returned an error exitcode (normal if you did not specifiy a source file to be compiled)

So interesting, the same program compiled with different libs gives different results.

Can anyone give me some sugguestion? Thanks in advance.

Try linking with libm.a and also check for the libgcc.a library.

Michael.

I added the following lines:
{$LINKLIB m}
{$LINKLIB gcc}
but still get the errors.

BTW, I am using Fedora4test3 which use gcc4. Should I recompile the whole fpc?

Thank you,

So I delete the chmlib.so and the compiler try to compile with chmlib.a

FPC tells the linker to look first in the current directory, so instead of deleting chmlib.so, you can just do this: % ln -s /usr/local/lib/libchm.a
in the directory of your pascal source.

undefined reference to `__moddi3'

Try adding this line to the top of your unit or program:
{$LINKLIB gcc_s}

- Jeff

Great, thank you.

There's no libgcc_s.a or something else in my computer:

/usr/bin/ld: cannot find -lgcc_s
Error: Error while linking

/usr/bin/ld: cannot find -lgcc_s BTW, I am using Fedora4test3 which use gcc4.

Do you have the libgcc libraries installed?
It should be be something like this:
http://rpmfind.net//linux/RPM/fedora/devel/i386/libgcc-4.0.0-8.i386.html

- Jeff

Try adding this line to the top of your unit or program: {$LINKLIB gcc_s}

Why _s? Is FC4 breaking compat here?

> {$LINKLIB gcc_s} Why _s? Is FC4 breaking compat here?

I think it is gcc that broke it, not Fedora. I am running SuSE 9.2 and I have /lib/libgcc_s.so.1 ( Installed from SuSE RPM )
and
/opt/gcc-3.4.0/lib/libgcc_s.so.1 ( Built directly from gnu.org sources )

- Jeff

Yes! Thank you. I create a link to /usr/lib from
/usr/lib/gcc/i386-redhat-linux/4.0.0/libgcc_s.so, and then my program can compile with the libchm.a successfully.
Thank you all.

Another question from a newbie fpc coder..

When compiling my project, I do a:

fpc -XS -XX -O3 -So -Fu~/manndoor/units -Fu~/manndoor/units/elecom -Fu~/manndoor/units/unix lord.pas

it goes through with its thing, warning me of unused variables and whatnot, but finishes with:

lord.pas(1841,1) Error: Can't call the linker, switching to external linking Error: /usr/local/bin/ppc386 returned an error exitcode (normal if you did not specifiy a source file to be compiled)

Whats the error that Im getting and how can I fix it?

[ Charset ISO-8859-1 unsupported, converting... ]

Typically this means "can't find binutils error".

So either you don't have binutils, or there is something wrong wiht it.

Marco and Michael,

game]$ ld
ld: no input files

So it exists.. And I know it works (I compiled apache, et al).. or could this particular version of ld be messed up?

You don't have the binutils installed. The compiler doesn't find 'ld'.

try executing the 'ld' command on a command prompt. If you get something like ld: Command not found
then you know ld is not installed, and you should install the binutils package.

Michael.

yy> >

which ld

and

ld --version

Add the "-s" option to your command line options when compiling, and afterwards run ./ppas.sh. Then you can see what error ld gives.

Jonas

Marco and Jonas,

ld --version:
GNU ld version 2.14.90.0.4 20030523

Add the "-s" option to your command line options when compiling, and afterwards run ./ppas.sh. Then you can see what error ld gives.

Added -s to the command line, ran ppas.sh, and it linked. Strange, eh?

Try running the compiler with -va, and examine the output. It should say where it looks for binaries, and why it didn't find 'ld'.

Michael.

(

just to keep the thread current, my current command line is:

fpc -va -XS -XX -O3 -So -Fu~/manndoor/units -Fu~/manndoor/units/elecom -Fu~/manndoor/units/unix lord.pas

)

Okay.. Running with -va.. The first time I run it, I get the following..

Searching file /usr/local/lib/fpc/2.0.0/ld... not found ...
Searching file /usr/bin/ld... found
Using util /usr/bin/ld
lord.pas(1841,1) Error: Can't call the linker, switching to external linking Error: /usr/local/bin/ppc386 returned an error exitcode (normal if you did not specifiy a source file to be compiled)

But the second time I run it

Searching file /usr/local/lib/fpc/2.0.0/ld... not found ...
Searching file /usr/bin/ld... found
Using util /usr/bin/ld
1969 Lines compiled, 9.7 sec

I can then recompile, over and over, without issue..