From: Eli Zaretskii <eliz@gnu.org>
To: rgm@gnu.org
Cc: 15675@debbugs.gnu.org, andrewjmoreton@gmail.com
Subject: bug#15675: the configure script invoked before make
Date: Fri, 25 Oct 2013 11:45:47 +0300 [thread overview]
Message-ID: <83txg5hh6s.fsf@gnu.org> (raw)
In-Reply-To: <83vc0lhn2g.fsf@gnu.org>
> Date: Fri, 25 Oct 2013 09:38:47 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 15675@debbugs.gnu.org, andrewjmoreton@gmail.com
>
> > From: Glenn Morris <rgm@gnu.org>
> > Cc: andrewjmoreton@gmail.com, 15675@debbugs.gnu.org
> > Date: Thu, 24 Oct 2013 17:30:00 -0400
> >
> > It seems to me that both the Irix and MinGW cases should be using
> > C(PP)FLAGS instead of using GCC_TEST_OPTIONS to modify CC.
>
> That was the first thing I tried back when I worked on configuring
> MinGW with the configure script. But it doesn't fly too well, either.
> I don't exactly remember the details, but I think the flags ended
> up twice in the compilation command, once from CPPFLAGS and another
> time from CFLAGS. Or something like that.
>
> These are all minor issues, but so is the fact that CPP includes
> switches. And CPP is only used by lib/Makefile.in. So these are nits
> in any case.
Actually, having these flags twice on the command line is not a minor
problem: some headers in nt/inc use #include_next, which will not DTRT
if -I../nt/inc is seen more than once on the command line.
prev parent reply other threads:[~2013-10-25 8:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 17:02 bug#15675: the configure script invoked before make “Adrian”
2013-10-23 6:26 ` Glenn Morris
2013-10-24 1:12 ` Andy Moreton
2013-10-24 1:56 ` Glenn Morris
2013-10-24 2:16 ` Glenn Morris
2013-10-24 3:44 ` Andy Moreton
2013-10-24 4:07 ` Glenn Morris
2013-10-24 14:48 ` Andy Moreton
2013-10-24 16:11 ` Eli Zaretskii
2013-10-24 21:30 ` Glenn Morris
2013-10-25 6:38 ` Eli Zaretskii
2013-10-25 8:45 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83txg5hh6s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15675@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=rgm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).