NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/comp/os/linux/7023

Text File | 1992-07-29 | 1.6 KB | 38 lines

Newsgroups: comp.os.linux
Path: sparky!uunet!wupost!cs.utexas.edu!rice!corywest
From: [e-mail] (Cory Richard West)
Subject: GDB 4.6 Questions (What's a .a good for anyway?)
Message-ID: <[e-mail]>
Followup-To: comp.os.linux
Summary: Questions about gdb and .a files
Keywords: gdb 4.6 library
Sender: [e-mail] (News)
Organization: Rice University Computer Science
Date: Thu, 30 Jul 1992 06:04:23 GMT
Lines: 24

    Hello all.  I just built gdb 4.6 and I have some questions for
anyone else that may have had similar problems.  My hardware setup is a
486-33 running gcc 2.2.2d and .96c pl2.  I used the -m486 -O2 CFLAGS
and the -static LDFLAGS (explained below).
    First, gdb 4.6 always crashed with a memory corruption error
when I linked it dynamically.  I had to link it statically in order for
it to function.  Why is this?  Would using a different sharing scheme
(like the jump tables in gcc 2.2.2d) have overcome this problem?
    Second, along with a binary, I created a bunch of .a files.
Is there a reason that I should keep these libraries around?  I have
an old libiberty.a hanging around in /usr/local from an old gcc installation
if I remember correctly.  If I should keep these, where should I put
them.  I'm just curious, I guess, as to why these might or might not
be saving material.
    Ok, that's enough for now.  Many thanks and I'll see you all
later.

            Cory West, [e-mail]

P.S.  One of the default CFLAGS is -g.  That produces a 3.5+ megabyte
binary and sucks up some 20 megabytes of disk while building.  I had
to compile twice because I missed this one -- Yuck!