public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Sammartino, Ryan" <rsammartino@ea.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: other/3286 Date: Wed, 20 Jun 2001 17:46:00 -0000 [thread overview] Message-ID: <20010621004600.5165.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR other/3286; it has been noted by GNATS. From: "Sammartino, Ryan" <rsammartino@ea.com> To: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>, "'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>, "'fmuel@mpi-halle.mpg.de'" <fmuel@mpi-halle.mpg.de>, "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>, "'nobody@gcc.gnu.org'" <nobody@gcc.gnu.org> Cc: Subject: Re: other/3286 Date: Wed, 20 Jun 2001 17:45:03 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%26pr=3286%26database=gcc > Why did you think that --program-suffix is supported? Probably because it is listed in the output of configure --help Anyways, it would be nice if --program-suffix and --program-prefix were supported... makes it nicer for those of us who have multiple versions of various cross-compilers on one system. Ryan T. Sammartino I'd crawl over an acre of 'Visual This++' and 'Integrated Development That' to get to gcc, Emacs, and gdb. Thank you. Vance Petree
reply other threads:[~2001-06-20 17:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010621004600.5165.qmail@sourceware.cygnus.com \ --to=rsammartino@ea.com \ --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: linkBe 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).