From: "Rupert Wood" <me@rupey.net>
To: "'yt wang'" <yt_y2k@yahoo.com>
Cc: <gcc-help@gnu.org>
Subject: RE: gcc installation problem
Date: Mon, 01 Jul 2002 01:01:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D5EC4C7@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D6BFC5C@whale.softwire.co.uk>
Yt Wang wrote:
> ../gcc-3.0.3/configure --prefix=../gcc-3.0.3 --exec-prefix=.
:
> libtool: link: only absolute run-paths are allowed
Relative paths don't work as prefixes; you need to specify the full
path, e.g.
../gcc-3.0.3/configure --prefix=/home/arch03/apps/gcc-3.0.3
You appear to be trying to set the executable prefix to the build
directory; that's probably not a good idea. You probably don't need to
set exec-prefix (it'll default to the same as prefix) unless you've got
many systems mounting the same home directory over NFS and want
different binaries for each but maintain a shared directory for scripts,
etc.
Hope that helps,
Rup.
next parent reply other threads:[~2002-07-01 8:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18D6BFC5C@whale.softwire.co.uk>
2002-07-01 1:01 ` Rupert Wood [this message]
[not found] <002a01c36409$72d08fa0$2c7b2e80@ee271dpc5>
2003-08-16 15:30 ` Gcc " Andrew Pinski
2003-08-16 15:14 Long Fei
[not found] <002801c36407$3ff5fc20$2c7b2e80@ee271dpc5>
2003-08-16 15:08 ` Andrew Pinski
-- strict thread matches above, loose matches on Subject: below --
2002-06-30 21:11 gcc " yt wang
2001-04-05 18:08 GCC Installation problem kyamada
2001-04-05 19:05 ` Alexandre Oliva
2000-10-20 1:34 GCC Installation Problem TEO Poh Kwee
2000-04-05 23:22 gcc installation problem Gilad Even-Tzur
1999-10-08 11:58 gcc:installation problem oupegt
1999-10-08 14:43 ` Paul D. Smith
1999-10-11 12:54 ` oupegt
1999-10-11 14:12 ` Paul D. Smith
1999-10-31 13:57 ` Paul D. Smith
1999-10-31 13:57 ` oupegt
1999-10-31 13:57 ` Paul D. Smith
1999-10-31 13:57 ` oupegt
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=616BE6A276E3714788D2AC35C40CD18D5EC4C7@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=gcc-help@gnu.org \
--cc=yt_y2k@yahoo.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).