From: Claudio Bley <bley@cs.uni-magdeburg.de>
To: frank.schafer@setuza.cz
Cc: kabir.patel@uk.andersen.com, me@rupey.net, gcc-help@gcc.gnu.org
Subject: Re: Configuration options
Date: Fri, 16 Nov 2001 07:40:00 -0000 [thread overview]
Message-ID: <15357.65288.238383.7265@wh2-19.st.uni-magdeburg.de> (raw)
In-Reply-To: <3BFE070B.3A270313@setuza.cz>
>>>>> "Frank" == Frank Schafer <frank.schafer@setuza.cz> writes:
Frank> kabir.patel@uk.andersen.com wrote:
>> I have a question regarding configuration options specified in
>> http://gcc.gnu.org/install/configure.html
>>
>> In the documentation it states:
>>
>> --prefix=dirname Specify the toplevel installation
>> directory. This is the recommended way to install the tools
>> into a directory other than the default. The toplevel
>> installation directory defaults to /usr/local.
>>
>> For this would I specify
>>
prompt> ./configure prefix="/home/gnu"
>> for example.
>>
>> It didn't seem to work, but came back with an error message
>> like the following:
>>
>> "Invalid configuration `prefix=/home/gnu': machine
>> `prefix=prefix=/home/gnu' not recognized"
>>
>> Could somebody tell me whats wrong?
>>
>> Thanks Kabir
>>
Frank> Hi,
Frank> simply replace the:
prompt> ./configure prefix="/home/gnu"
Frank> by:
prompt> ./configure prefix=/home/gnu
NO. This is not the problem.
To put it clearly this time (Ken?!):
You're missing the double dashes in front of the `--prefix' option.
../gcc-source/configure --prefix="/home/gnu"
The double quotes are okay because they are removed by the shell
before the command line arguments are passed to the configure
script. The last non-option argument is treated as a system type
specification and 'prefix=/home/gnu' is not a valid system type the
GCC configure script knows about.
Claudio
next prev parent reply other threads:[~2001-11-23 7:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 15:19 kabir.patel
2001-11-12 22:52 ` Claudio Bley
2001-11-16 0:57 ` Frank Schafer
2001-11-16 7:40 ` Claudio Bley [this message]
2001-11-17 12:26 ` Frank Schafer
2001-11-25 22:30 ` Frank Schafer
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=15357.65288.238383.7265@wh2-19.st.uni-magdeburg.de \
--to=bley@cs.uni-magdeburg.de \
--cc=frank.schafer@setuza.cz \
--cc=gcc-help@gcc.gnu.org \
--cc=kabir.patel@uk.andersen.com \
--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).