This is the mail archive of the mailing list for the Cygwin project. See the Cygwin home page for more information.
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Error reading line numbers ?

The only use for libc.a libm.a TIKO is to recompile
libcygwin.a without recompiling newlib.
You can either hand edit the Makefile in .../obj/i586-cygwin32/winsup
and use 
LIBC_A=`gcc -print-file-name=libc.a`
LIBM_A=`gcc -print-file-name=libm.a`
which will work BTW whether you build newlib or not. (Why isn't this the default?)

or just place a copy of both libs in .../obj/i586-cygwin32/newlib
This will save quite a large percentage of the time normally used in a configure/compile,
but be careful about version/header changes in newlib.
ie READ the Changelog, if you do this.-)
or just use the ones from the same snap.

On Sun, 18 Apr 1999 07:14:42 -0700 (PDT), you wrote:

>--- "Suhaib M. Siddiqi" <> wrote:
>> > I have compiled my program with -c -g option's and linked it with libc.a,
>> libm.a,libcygwin.a an librpclib.a and got this error when I start it:
>> > 
>> You do not neet to link against libc.a, libcygwin.a is enough.
>This brings up the question of why libc.a is even included in the distribution
>package?  Is there a useful purpose for it?  Is there documentation as to when
>you might want to use libc.a over libcygwin.a?
>"Earnie Boyd" <>
>       DLLHELP: <>
>                <>
>Do You Yahoo!?
>Get your free address at

Want to unsubscribe from this list?
Send a message to