From: Glenn Morris <rgm@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Yavor Doganov <yavor@gnu.org>, Jason Rumney <jasonr@gnu.org>,
YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>,
emacs-devel@gnu.org
Subject: Removing --with-gcc, Cygwin [was Re: 23.0.50; Image support disabled by default?]
Date: Sat, 02 Feb 2008 17:32:07 -0500 [thread overview]
Message-ID: <e7k5lnng60.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <m3abmqkj1r.fsf@fleche.redhat.com> (Tom Tromey's message of "Sun, 27 Jan 2008 15:20:00 -0700")
Tom Tromey wrote:
> I don't see a reason to have --without-gcc at all. The normal
> approach is to have the user set CC on the command line and then have
> configure detect whether or not it is gcc; AC_PROG_CC will do this.
[patch elided]
Sounds fine to me.
etc/PROBLEMS and nt/INSTALL both suggest using '--with-gcc' (plus
other stuff) for some Cygwin builds.
Does Cygwin actually need --with-gcc for some reason, or is it ok to
remove it?
next prev parent reply other threads:[~2008-02-02 22:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 16:30 23.0.50; Image support disabled by default? Yavor Doganov
2008-01-23 16:44 ` Tom Tromey
2008-01-23 17:17 ` Jason Rumney
2008-01-23 17:21 ` Yavor Doganov
2008-01-23 18:40 ` Tom Tromey
2008-01-25 4:37 ` Glenn Morris
2008-01-25 5:00 ` YAMAMOTO Mitsuharu
2008-01-26 2:24 ` Glenn Morris
2008-01-26 4:55 ` Tom Tromey
2008-01-27 22:27 ` Tom Tromey
2008-01-27 22:20 ` Tom Tromey
2008-02-02 22:32 ` Glenn Morris [this message]
2008-02-03 4:07 ` Removing --with-gcc, Cygwin [was Re: 23.0.50; Image support disabled by default?] Eli Zaretskii
2008-02-03 21:00 ` Removing --with-gcc, Cygwin Glenn Morris
2008-02-03 21:19 ` Glenn Morris
2008-02-03 21:24 ` Jason Rumney
2008-02-03 21:43 ` David Robinow
2008-02-03 22:01 ` Jason Rumney
2008-02-04 4:12 ` Eli Zaretskii
2008-02-02 22:52 ` Removing --with-gtk [was Re: 23.0.50; Image support disabled by default?] Glenn Morris
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=e7k5lnng60.fsf_-_@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
--cc=tromey@redhat.com \
--cc=yavor@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.