From: "Artūras Moskvinas" <arturas.moskvinas@gmail.com>
To: Takatsugu Kobayashi <tkobayas@indiana.edu>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Newbie question
Date: Fri, 25 May 2007 21:12:00 -0000 [thread overview]
Message-ID: <46573A39.2070206@gmail.com> (raw)
In-Reply-To: <4657386E.7000804@indiana.edu>
Takatsugu Kobayashi wrote:
> Hi,
>
> I migrated from windows to Fedora6 linux a few months ago, and am still
> learning to make the best out of this fantastic OS....
>
> I just installed GSL for my statistical research, but I installed it on
> a different folder than the one I wa supposed to. I should have
> installed /usr/include directory rather than /usr/local/include. So I
> should specify the path to this usr/local/inlcude/gsl everytime I run
> C/C++.
>
> This is very simple newbie question, but how to specify the path in the
> process of ./configure, make, make install etc? I could just copy and
> paste all the files in the gsl directory in /usr/local/include to
> /usr/include by the chmod command....
>
Hi,
Very often (almost always) you can specify --prefix
./configure --prefix=/usr/
And all files will be written to /usr/include /usr/lib and etc, not
under /usr/local/
However there is a gsl package in FC6 repository try "yum install gsl"
and "yum install gsl-devel".
Arturas M.
next prev parent reply other threads:[~2007-05-25 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 19:32 Takatsugu Kobayashi
2007-05-25 21:12 ` Artūras Moskvinas [this message]
2007-05-26 8:54 ` Matthew Woehlke
-- strict thread matches above, loose matches on Subject: below --
2007-07-06 20:10 newbie question Leonardo Santagostini
[not found] <616BE6A276E3714788D2AC35C40CD18D3F27FE@whale.softwire.co.uk>
2002-02-08 1:14 ` Rupert Wood
2002-02-07 16:47 M.A-R. Abdullah
2001-03-14 10:16 David Korn
2001-03-14 9:16 Stagner, Robert
2001-01-10 23:22 Craig Cowen
2001-01-10 23:24 ` Lawrence W. Leung
2001-01-10 23:32 ` Puneet Singhal
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=46573A39.2070206@gmail.com \
--to=arturas.moskvinas@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tkobayas@indiana.edu \
/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).