From: Andy Moreton <andrewjmoreton@gmail.com>
To: 15675@debbugs.gnu.org
Subject: bug#15675: the configure script invoked before make
Date: Thu, 24 Oct 2013 04:44:35 +0100 [thread overview]
Message-ID: <827gd3pc2k.fsf@gmail.com> (raw)
In-Reply-To: <20131021170256.GA1699@glam>
On Thu 24 Oct 2013, Glenn Morris wrote:
> Glenn Morris wrote:
>
>>> Building in "obj-mingw32/lib" fails because CPP and CPPFLAGS still have
>>> "-I ../nt/inc",
>
> ? Why does CPP contain flags at all? Sounds wrong.
With your updated configury from r114769, obj-mingw32/lib/Makefile has:
CPP = gcc -I ../nt/inc -E
CPPFLAGS = -mtune=pentium4 -IC:/emacs/mingw-devel/include -IC:/emacs/mingw-devel/src/xpm/3.5.1/libXpm-3.5.1-src/lib -DUSE_CRT_DLL=1 -I ${abs_top_srcdir}/nt/inc
Not sure where that comes from though...
>> Yes, I posted about that on emacs-devel a little earlier, see
>> http://lists.gnu.org/archive/html/emacs-devel/2013-10/msg00733.html
>
> I installed my guess at a solution...
Thanks for looking at this. There is still a build error in that the the
paths using $abs_top_srcdir don't expand properly. I've tracked this
down to the trailing tab and comment in the Makefile.in files:
abs_top_srcdir=@abs_top_srcdir@ # MinGW CPPFLAGS may use this
Removing the tab and the comment in all the Makefile.in files fixed
things for me.
AndyM
next prev parent reply other threads:[~2013-10-24 3:44 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 [this message]
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
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=827gd3pc2k.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=15675@debbugs.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.