From: Bernd Eggink <eggink@uni-hamburg.de>
To: David Mazieres <dm@reeducation-labor.lcs.mit.edu>
Cc: egcs@cygnus.com
Subject: Re: Suggestion for --with-local-prefix configure option
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <36EF6694.50DF9AE7@uni-hamburg.de> (raw)
Message-ID: <19990331234600.-FV5UZ89Cn-FTfsLZL58VE--jGw6E0_gD2dkINML_dI@z> (raw)
In-Reply-To: <199903161814.NAA04184@reeducation-labor.lcs.mit.edu>
David Mazieres wrote:
>
> The gcc/egcs --with-local-prefix configure argument seems to confuse a
> lot of people, and the default generally seems wrong if --prefix is
> something other than /usr/local.
I confess I belong to the confused lot, and yes, I had trouble with the
include files. Specifically, I'd appreciate an advice how to set up the
prefixes when egcs is installed on a server. Clients only mount the base
directory and I don't always know what's in their /usr/local
directories, so I'd rather not have the client's directories searched at
all.
Will --with-local-prefix == --prefix be OK in that case?
Regards,
Bernd
--
Bernd Eggink
Regionales Rechenzentrum der Uni Hamburg
eggink@rrz.uni-hamburg.de
http://www.rrz.uni-hamburg.de/eggink/BEggink.html
next prev parent reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 10:14 David Mazieres
1999-03-16 16:14 ` Alexandre Oliva
1999-03-31 23:46 ` Alexandre Oliva
1999-03-17 0:24 ` Bernd Eggink [this message]
1999-03-31 23:46 ` Bernd Eggink
1999-03-31 23:46 ` David Mazieres
1999-03-16 18:01 N8TM
[not found] ` < c37ea7d.36ef0bb1@aol.com >
1999-03-16 18:07 ` Jean-Pierre Radley
1999-03-31 23:46 ` Jean-Pierre Radley
1999-03-17 3:57 ` fheitka
1999-03-31 23:46 ` fheitka
1999-03-31 23:46 ` N8TM
1999-03-17 14:53 Mike Stump
1999-03-17 19:41 ` David Starner
1999-03-31 23:46 ` David Starner
1999-03-31 23:46 ` Mike Stump
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=36EF6694.50DF9AE7@uni-hamburg.de \
--to=eggink@uni-hamburg.de \
--cc=dm@reeducation-labor.lcs.mit.edu \
--cc=egcs@cygnus.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).