public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Frank Mueller" <fmuel@mpi-halle.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: other/3286: --program-suffix is ignored
Date: Wed, 20 Jun 2001 22:36:00 -0000 [thread overview]
Message-ID: <20010621053601.15924.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR other/3286; it has been noted by GNATS.
From: "Frank Mueller" <fmuel@mpi-halle.de>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: <gcc-gnats@gcc.gnu.org>,
<gcc-bugs@gcc.gnu.org>
Subject: Re: other/3286: --program-suffix is ignored
Date: Thu, 21 Jun 2001 07:36:30 +0200
On 20 Jun 01, at 19:41, Joseph S. Myers wrote:
> On 20 Jun 2001 fmuel@mpi-halle.mpg.de wrote:
>
> > Most executables are installed without the suffix given to
> > configure.
> > >How-To-Repeat:
> > ../gcc-3.0/configure --program-suffix=3D'-3.0' && make && make install
>
> Why did you think that --program-suffix is supported? The supported
> configure options are listed in gcc/doc/install.texi (and the
> generated HTML documentation in the INSTALL directory in releases);
> --program-suffix is deliberately (i.e., when adding standard configure
> options such as --bindir to the GCC documentation, I deliberately did
> not add --program-suffix) not listed there.
>
It is given as an answer to ./configure --help and processed by
configure. So it should at least be removed there.
Best Regards
Frank M=FCller
-------------------------------------------
Dr. Frank Mueller
Max-Planck-Institut fuer Mikrostrukturphysik
Weinberg 2, D-06120 Halle, Germany
Tel.: ++49-345-5582-725
Fax.: 5511223
email: fmuel@mpi-halle.mpg.de
WWW : http://www.mpi-halle.mpg.de/~fmuel
next reply other threads:[~2001-06-20 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 22:36 Frank Mueller [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-20 11:46 Joseph S. Myers
2001-06-20 3:26 fmuel
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=20010621053601.15924.qmail@sourceware.cygnus.com \
--to=fmuel@mpi-halle.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).