public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Carter <john.carter@tait.co.nz>
To: gcc-help@gcc.gnu.org
Subject: Static linking to libgcc_s and libstdc++
Date: Sun, 04 Aug 2002 17:21:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0208051217520.21447-100000@parore> (raw)

Greetings folk,

I have just compiled gcc-3.1.1 for Solaris 2.5.1.

I have compiled my app, and now wish to distribute it to the test machines 
/ clients.

Alas, it expects a sharable libstdc++ and libgcc_s.

I can distribute the .so files as well, but this increases maintenance and 
customer support headaches.

How can I convince gcc to statically link in those libraries (and no other 
sharable libraries)?

Thank you,

-- 


John Carter                             Phone : (64)(3) 358 6639
Tait Electronics                        Fax   : (64)(3) 359 4632
PO Box 1645 Christchurch                Email : john.carter@tait.co.nz
New Zealand

This email message is intended only for the addressee(s) and contains
information which may be confidential and/or copyright.  If you are not
the intended recipient please do not read, save, forward, disclose, or
copy the contents of this email. If this email has been sent to you in
error, please notify the sender by reply email and he will be
along to delete you, this email and any copies or links to this email.  
No representation is made that this email, you, or the sender are free of
viruses. Virus scanning and prevention is recommended and is the
responsibility of consenting adults.

             reply	other threads:[~2002-08-05  0:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-04 17:21 John Carter [this message]
2002-08-04 22:41 ` bjorn rohde jensen
     [not found] <616BE6A276E3714788D2AC35C40CD18D762A3B@whale.softwire.co.uk>
2002-08-05  6:24 ` Rupert Wood

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=Pine.LNX.4.44.0208051217520.21447-100000@parore \
    --to=john.carter@tait.co.nz \
    --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).