From: Karol Ostrovsky <karol.ostrovsky@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Chris Zheng <chriszheng99@gmail.com>, 18302@debbugs.gnu.org
Subject: bug#18302: MSYS2 build issues
Date: Mon, 25 Aug 2014 10:18:20 +0200 [thread overview]
Message-ID: <CAFpApP_y1i=oYgd9F4AUkLeUA6GiwyWf8-0JFoMSCmm0fa=O+g@mail.gmail.com> (raw)
In-Reply-To: <83bnrbmvm7.fsf@gnu.org>
Hello Eli,
thank you for the help. As for the item 3: as far as I understand the
situation with xpm in MinGW-w64 is the same as in Cygwin. There are
two packages providing xpm, and it is the package that is installed in
the non-standard place that must be used for Emacs native Windows
build. Thus, I don't see why the same solution that was approved for
Cygwin cannot be used for MinGW-w64.
Best regards,
Karol
On 23 August 2014 10:57, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 22 Aug 2014 16:18:11 +0200
>> From: Karol Ostrovsky <karol.ostrovsky@gmail.com>
>> Cc: Ken Brown <kbrown@cornell.edu>, Chris Zheng <chriszheng99@gmail.com>, 18302@debbugs.gnu.org
>>
>> I will try to summarise the situation, and I am attaching my updated
>> solution proposal for this particular bug:
>>
>> 1. MSYS2 uname must be handled properly, and that is fixed in the new
>> proposed patch. I disagree with not renaming opsys from mingw32 to
>> mingw, since mingw32 string is used in other places in the same file
>> and it means something else there, which I find possibly confusing.
>> But this change is not in my new patch.
>>
>> 2. -mtune is back to what it was with a minimal change required for
>> MSYS2+MinGW-w64 uname handling.
>>
>> 3. Include path for xpm in MSYS2+MinGW-w64 is handled in the same way
>> as in Cygwin. Perhaps, the same type of comment as was added for
>> Cygwin should be added for MSYS2+MinGW-w64.
>>
>> 4. A loop is added in the recipe for emacs.exe to handle
>> bootstrap-emacs.exe busy problem.
>
> Thanks. I installed items 1, 2, and 4, but not item 3.
>
> If you think we should do something about the xpm.h header, then
> please try this alternative solution: copy the xpm.h header file into
> the X11 subdirectory of your GCC 'include' directory (the one where
> you have all the standard C header files), then try configuring and
> building Emacs without adding the "-I/mingw64/include/noX" switch to
> CPPFLAGS. If that doesn't work, please show the error messages you
> get from the compiler, and let's take it from there.
>
> If, for some reason, you think that copying xpm.h to include/X11/xpm.h
> is not appropriate, please explain why you think so.
next prev parent reply other threads:[~2014-08-25 8:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 9:54 bug#18302: MSYS2 build issues Karol Ostrovsky
2014-08-20 16:26 ` Eli Zaretskii
2014-08-20 17:04 ` Glenn Morris
2014-08-20 17:20 ` Eli Zaretskii
2014-08-21 10:08 ` Karol Ostrovsky
2014-08-21 14:30 ` Eli Zaretskii
2014-08-21 16:00 ` Glenn Morris
2014-08-21 18:38 ` Ken Brown
2014-08-21 19:22 ` Eli Zaretskii
2014-08-21 19:33 ` Eli Zaretskii
2014-08-21 21:29 ` Ken Brown
2014-08-22 6:10 ` Eli Zaretskii
2014-08-22 13:04 ` Ken Brown
2014-08-22 13:33 ` Eli Zaretskii
2014-08-22 14:18 ` Karol Ostrovsky
2014-08-23 8:57 ` Eli Zaretskii
2014-08-25 8:18 ` Karol Ostrovsky [this message]
2014-08-25 14:56 ` Eli Zaretskii
2017-11-29 1:46 ` Noam Postavsky
2014-08-21 22:32 ` Angelo Graziosi
2014-08-22 6:30 ` Eli Zaretskii
2014-08-22 10:55 ` Angelo Graziosi
2014-08-22 13:25 ` 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
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='CAFpApP_y1i=oYgd9F4AUkLeUA6GiwyWf8-0JFoMSCmm0fa=O+g@mail.gmail.com' \
--to=karol.ostrovsky@gmail.com \
--cc=18302@debbugs.gnu.org \
--cc=chriszheng99@gmail.com \
--cc=eliz@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).