To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: gcc problem with libraries
Date:	Wed, 03 Aug 94 12:51:44 +0300
From:	eliz AT is DOT elta DOT co DOT il

GianPiero Puccioni <gip AT firefox DOT ino DOT it> writes:

> I  suppose  it means it can't find libgcc.a., but why? And why it's there
> twice? if I give by  hand  the  last  command  "ld.exe ..." and so on it
> works! The same line!

First, I would check the number of FILES= in your CONFIG.SYS.  Enlarge it by,
say, 20 and see if you win.  It just may be that DOS is out of handles by
the time it gets to libgcc.a.  When you run the same command from the DOS
prompt by hand, some handles used by go32 and gcc driver are freed and
available.
libgcc.a is mentioned twice on the ld line because some linkers only scan
the libraries once, and thus if some functions in libgcc call some functions
in libc, which in turn call other functions in libgcc, you'll get unresolved
externals if you omit the second -lgcc.  I'm not sure if that's an issue for
libc.a and libgcc.a that come with djgpp, or just a leftover from
GNU Gcc distribution (which must work for all kinds of linkers).

> DJGPP is actually on a HP workstation connected with PC-NFS as disk P:
> can this be the problem?

Why not test it?  Put libgcc.a in your current working directory and try
again.  To be on the safe side, add -L. to your command line, though I'm
not sure it's needed (there is an explanation of how and where does gcc
look for libraries in the gcc.info file, but I don't have it right here).

Hope this helps,
		Eli Zaretskii

Btw, your address <gip AT firefox DOT ino DOT it> bounces, maybe you should take
care of this?

- Raw text -