From: "Roger.Gough" <Roger.Gough@ul.ie>
To: 'Rupert Wood' <me@rupey.net>, "'Roger.Gough'" <roger.gough@ul.ie>
Cc: "'Gcc Help (E-mail)'" <gcc-help@gcc.gnu.org>
Subject: RE: Prefix command with gcc-2.95
Date: Wed, 05 Feb 2003 09:28:00 -0000 [thread overview]
Message-ID: <0B2F845E9599D611A6FA00B0D0D1DE4A27796C@exch-staff4.ul.ie> (raw)
Thanks Rup for your reply.
Yes everything you said I have done. However I was getting an error
with the Make command. If it does not build fully does that mean I will not
see any files in the directory I set as my prefix? I definetely dont see any
files in my prefix directory after I do my configuration. At the moment I am
not too bothered about the make error, I just want to get the prefix command
working. Thanks again.
Roger.
-----Original Message-----
From: Rupert Wood [mailto:me@rupey.net]
Sent: 04 February 2003 18:12
To: 'Roger.Gough'
Cc: 'Gcc Help (E-mail)'
Subject: RE: Prefix command with gcc-2.95
Roger Gough wrote:
> I am having some problems using the prefix command with gcc version
> 2.95. With the command:
>
> --prefix=dirname.
>
> This command should specify the toplevel installation directory.
> This does not seem to work for me.
It's always worked here. Can I verify you're adding this to the
configure line for a source-code distribution of GCC, i.e. you've done
something like
gzip -cd gcc-2.95.3.tar.gz |tar xvf -
mkdir build
cd build
../gcc-2.95.3/configure --prefix=/my/install/path
followed by 'make bootstrap', 'make install', etc.? It's not a parameter
for the gcc executable, nor is it a standalone command.
Rup.
next reply other threads:[~2003-02-05 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 9:28 Roger.Gough [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-05 9:34 Bhattiprolu Ravikumar-A18658
[not found] <616BE6A276E3714788D2AC35C40CD18DA26EB0@whale.softwire.co.uk>
2003-02-04 18:11 ` Rupert Wood
2003-02-04 18:03 Roger.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=0B2F845E9599D611A6FA00B0D0D1DE4A27796C@exch-staff4.ul.ie \
--to=roger.gough@ul.ie \
--cc=gcc-help@gcc.gnu.org \
--cc=me@rupey.net \
/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).