From: lrtaylor@micron.com
To: <pekka.holopainen@ericsson.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: static linking
Date: Mon, 06 Oct 2003 17:20:00 -0000 [thread overview]
Message-ID: <363801FFD7B74240A329CEC3F7FE4CC4A276CA@ntxboimbx07.micron.com> (raw)
This will cause the library to get linked in statically, but it will
also cause ALL libraries specified after it (including any default
system libraries, such as the C library) to get linked in statically.
If that's OK, then this should work fine.
Lyle
-----Original Message-----
From: Liguo Song [mailto:liguo.song@vanderbilt.edu]
Sent: Saturday, October 04, 2003 12:35 PM
To: Pekka Holopainen (KI/EAB)
Cc: 'gcc-help@gcc.gnu.org'
Subject: Re: static linking
man gcc
/static
The above get me to the -static option. Have you tried this?
Liguo
On Mon, 29 Sep 2003, Pekka Holopainen (KI/EAB) wrote:
> Hi
>
> I am using gcc 2.95.3 and I have problem to link libstdc++ staticly.
>
> When I start program and this lib is missing it always ask for it.
> What cn i do to get a static link module?
>
> Regards Pekka
>
> I have a new mail address: Pekka.Holopainen@ericsson.com
> My old e-mail address will function untill 2004-05-01. Please change
address in your personal address book.
>
next reply other threads:[~2003-10-06 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 17:20 lrtaylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-29 13:41 Pekka Holopainen (KI/EAB)
2003-10-04 18:35 ` Liguo Song
2002-09-20 5:32 numeric_limits Matthias Oltmanns
2002-09-20 5:59 ` static linking Arnauld Michelizza
2002-01-23 3:24 Static linking Israel Alvarez
2002-01-23 3:24 Israel Alvarez
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=363801FFD7B74240A329CEC3F7FE4CC4A276CA@ntxboimbx07.micron.com \
--to=lrtaylor@micron.com \
--cc=gcc-help@gcc.gnu.org \
--cc=pekka.holopainen@ericsson.com \
/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).