From: Slaven Peles <peles@cns.physics.gatech.edu>
To: crsccw@nus.edu.sg
Cc: gsl-discuss@sources.redhat.com
Subject: Re: problem in linking the lib
Date: Wed, 15 May 2002 12:24:00 -0000 [thread overview]
Message-ID: <E177c6t-0000Qe-00@kaos.physics.gatech.edu> (raw)
Message-ID: <20020515122400.Bd8eYUT03c7bUu7U3lp7mJksBWpSQ6ggsHc190BlQ6k@z> (raw)
In-Reply-To: <3CE0E44D.21DBDD0D@uni-koeln.de>
To make things even simpler, you don't have to specify your library path,
since compiler will look in /usr/lib anyway. In your case it is enough to
write
gcc tst.c -lgsl
or depending on what do you want to compile you might have to use
gcc tst.c -lgsl -lgslcblas -lm
Slaven
On Tuesday 14 May 2002 06:17 am, Achim Gaedke wrote:
> Hmm... Maybe it is a typo: the gcc command must be:
>
> gcc -L/usr/lib -lgsl test.c
>
> Please note the space between the option -L/usr/lib (extends the library
> searchpath) and the option -lgsl (command to link against gsl library).
>
> Achim
>
> Chang Chew Wai schrieb:
> > Dear sir, i think i need some help with gsl. i installed the rpm for
> > gsl-1.1.1-0. and was unable to link it to the lib.
> >
> > i tried to compile with the following command.
> > gcc -L/usr/lib-lgsl test.c
> >
> > the error messages are
> > /tmp/ccrOm9yz.o: In function `main':
> > /tmp/ccrOm9yz.o(.text+0x24): undefined reference to `gsl_stats_mean'
> > /tmp/ccrOm9yz.o(.text+0x3f): undefined reference to `gsl_stats_variance'
> > /tmp/ccrOm9yz.o(.text+0x5a): undefined reference to `gsl_stats_max'
> > /tmp/ccrOm9yz.o(.text+0x75): undefined reference to `gsl_stats_min'
> >
> > thanx
> > waiting for the reply
> > chew wai
next prev parent reply other threads:[~2002-05-14 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 9:55 Chang Chew Wai
2002-05-14 3:28 ` Chang Chew Wai
2002-12-31 9:55 ` Achim Gaedke
2002-05-14 3:39 ` Achim Gaedke
2002-12-31 9:55 ` Jacek Pliszka
2002-05-14 6:15 ` Jacek Pliszka
2002-12-31 9:55 ` Slaven Peles [this message]
2002-05-15 12:24 ` Slaven Peles
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=E177c6t-0000Qe-00@kaos.physics.gatech.edu \
--to=peles@cns.physics.gatech.edu \
--cc=crsccw@nus.edu.sg \
--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).