From: kadreg@free.fr
To: gcc-help@gcc.gnu.org
Cc: jpequery@objecteering.com
Subject: static instanciation in libraries stripped by the linker
Date: Mon, 06 Sep 2004 12:25:00 -0000 [thread overview]
Message-ID: <1094473544.413c57486f286@imp5-q.free.fr> (raw)
I have a huge application, all its object files in a single library file due to
a bash limitation for command line size. This file is about 715 megabytes.
I link using the command:
g++ -o myApplication mybiglib.a
and I obtains a single file of 2 megabytes.
This file only contains the loader for the application. Normally, this
application is instanciated by static parts, which seems to not be in the final
file.
Is the a way to ask to the linker to keep all this parts of the application, and
not losing it, like if I use a simple set of object files.
Jérôme Péquery.
next reply other threads:[~2004-09-06 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 12:25 kadreg [this message]
2004-09-06 12:47 ` Why does this segfault, big struct: too big? Jack Liddle
2004-09-07 12:33 ` Eljay Love-Jensen
2004-09-07 13:04 ` static instanciation in libraries stripped by the linker Eljay Love-Jensen
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=1094473544.413c57486f286@imp5-q.free.fr \
--to=kadreg@free.fr \
--cc=gcc-help@gcc.gnu.org \
--cc=jpequery@objecteering.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).