From: "Stuart Summerville (NEC)" <stuarts@icpdd.neca.nec.com.au>
To: "Gcc-Help@Gcc. Gnu. Org" <gcc-help@gcc.gnu.org>
Subject: Re: Need help building & integrating library into target program
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <001301bf4385$1feb7820$cb884c93@porpoise.icpdd.neca.nec.com.au> (raw)
Message-ID: <19991231222400.Jc3Ts3rP0-7H5S3wGbhcuc-Fsxo8KCZwqpiBkHPVm_Q@z> (raw)
>It would be best to show us how you're trying to link against the
>library; knowing your platform would also be helpful.
>--ag
>
Hi Arthur,
Given that I have mylib.a in the current directory, I issue the command:
gcc -static -g -o rw startup_lib.a
to produce the rw executable. Then, issuing the command:
ldd rw
tells me that this dynamically linked executable is dependent on mylib.o. I
presume that as its linked statically, there shouldn't be any lib
dependence....
Tools used:
Solaris 2.5.1
gcc egcs-2.91.57 19980901 (egcs-1.1 release)
ld 2.8.1 (with BFD 2.8.1)
Also, mylib.a was created in the following manner:
gcc -MD -I../include -g -o init.o -c init.c
ar rv ../../../obj/mylib.a *.o
I've seen the same behaviour on two Sol251 boxes.
To contrast this, if I do the same thing on a Redhat Linux (5.2) box (gcc =
2.7.2.3, ld = 2.9.1 (with BFD 2.9.1.0.15)), it works fine. If statically
linked, ldd won't touch it (unlike the Solaris box, which still shows that
erroneous dependence) & it runs properly; if dynamically linked, ldd reports
that libc and ld-linux are linked but no mylib.a (or even mylib.o).
?
Some other questions:
1) does linking of libraries dynamically only affect files specified with
the -l switch to ld? Can a file specified as an ordinary object file to ld,
be dynamically linked in? eg. if I don't supply ld with the -static switch,
will archive files passed in the manner "ld -o myprog mylib.a ..." be
statically linked anyway?
2) Is there any use in my creating arcive/object files with the -shared
switch to ld? This seems to be a useful thing to do, but the ld manpage
suggests its not a common method anymore.
Thanks,
sTu.
_________________________________________________________________________
Stuart Summerville NEC Australia Pty. Ltd.
ph: (+61 3) 9264-3090 Integrated Comm Products (R&D)
fax:(+61 3) 9264-3841 649-655 Springvale Road
e-mail: stuarts@icpdd.neca.nec.com.au Mulgrave, VIC 3170, AUSTRALIA
next reply other threads:[~1999-12-31 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-11 12:14 Stuart Summerville (NEC) [this message]
1999-12-31 22:24 ` Stuart Summerville (NEC)
-- strict thread matches above, loose matches on Subject: below --
1999-12-11 2:42 Stuart Summerville (Deimus)
1999-12-31 22:24 ` Stuart Summerville (Deimus)
1999-12-10 0:21 Stuart Summerville
1999-12-10 13:02 ` Arthur Gold
1999-12-12 14:14 ` Stuart Summerville
1999-12-12 15:56 ` Stuart Summerville
1999-12-31 22:24 ` Stuart Summerville
1999-12-31 22:24 ` Stuart Summerville
1999-12-31 22:24 ` Arthur Gold
1999-12-31 22:24 ` Stuart Summerville
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001301bf4385$1feb7820$cb884c93@porpoise.icpdd.neca.nec.com.au' \
--to=stuarts@icpdd.neca.nec.com.au \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).