public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Gunter <gunterj@dustbunny.physics.indiana.edu>
To: gcc-help@gcc.gnu.org
Subject: libg2c.so?
Date: Mon, 06 Dec 1999 08:09:00 -0000	[thread overview]
Message-ID: <199912061609.LAA1390350@dustbunny.physics.indiana.edu> (raw)

Hi,

I think I would like to have a shared version of libg2c for some stuff I'm 
doing under Linux.  I have searched through the gcc mailing lists and come 
up dry. There are "wish list"/"to be done in the future" comments about 
converting libg2c.a into libg2c.so but no reports of anyone having done this 
successfully. So  before I run off and try it, does anybody know of I a 
reason I can't just build the stuff in the g2c subdir to be shared?

Thanks
Jeff Gunter

gunterj@dustbunny.physics.indiana.edu



WARNING: multiple messages have this Message-ID

From: Jeff Gunter <gunterj@dustbunny.physics.indiana.edu>
To: gcc-help@gcc.gnu.org
Subject: libg2c.so?
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <199912061609.LAA1390350@dustbunny.physics.indiana.edu> (raw)
Message-ID: <19991231222400.IQIqRml74Qt7OH_CYIYxjPZy-eJBKnSjWTG-4m6q0xQ@z> (raw)

Hi,

I think I would like to have a shared version of libg2c for some stuff I'm 
doing under Linux.  I have searched through the gcc mailing lists and come 
up dry. There are "wish list"/"to be done in the future" comments about 
converting libg2c.a into libg2c.so but no reports of anyone having done this 
successfully. So  before I run off and try it, does anybody know of I a 
reason I can't just build the stuff in the g2c subdir to be shared?

Thanks
Jeff Gunter

gunterj@dustbunny.physics.indiana.edu



             reply	other threads:[~1999-12-06  8:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-06  8:09 Jeff Gunter [this message]
1999-12-31 22:24 ` libg2c.so? Jeff Gunter

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=199912061609.LAA1390350@dustbunny.physics.indiana.edu \
    --to=gunterj@dustbunny.physics.indiana.edu \
    --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).