public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Rodney Sparapani <rsparapa@post.its.mcw.edu>
To: gsl-discuss@sources.redhat.com
Subject: linker trouble w/ GSL-0.8
Date: Wed, 19 Dec 2001 13:20:00 -0000	[thread overview]
Message-ID: <200106192143.QAA21713@post.its.mcw.edu> (raw)

I was having linking problems with GSL 0.8 on Solaris 8 from gcc 2.95.3.  Today, 
gcc 3.0 was released, and I'm happy to report that the linker problems are gone. 
Give it a shot if you are having this problem.

Rodney Sparapani              Medical College of Wisconsin
Sr. Biostatistician           Patient Care & Outcomes Research (PCOR)
rsparapa@mcw.edu              8701 Watertown Plank Rd., Rm. H2775
(414) 456-8786 (FAX: 6689)    PO Box 26509, Milwaukee, WI  53226-0509

             reply	other threads:[~2001-12-19 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 13:20 Rodney Sparapani [this message]
2001-12-19 13:20 ` Brian Gough

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=200106192143.QAA21713@post.its.mcw.edu \
    --to=rsparapa@post.its.mcw.edu \
    --cc=gsl-discuss@sources.redhat.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).