From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: 18302@debbugs.gnu.org
Subject: bug#18302: MSYS2 build issues
Date: Fri, 22 Aug 2014 16:25:02 +0300 [thread overview]
Message-ID: <83tx54mzbl.fsf@gnu.org> (raw)
In-Reply-To: <53F721B9.5010806@alice.it>
> Date: Fri, 22 Aug 2014 12:55:53 +0200
> From: Angelo Graziosi <angelo.graziosi@alice.it>
> CC: 18302@debbugs.gnu.org
>
> > Sorry, I don't understand what does this have to do with the issue at
> > hand.
>
> Sorry for the noise then.. I have tried to explain (unsuccessfully) why
> MSYS2 doesn't put XPM things in standard directory..
MSYS2 cannot put anything anywhere, it can only map some /foo
directories to certain Windows directories. But those MSYS2 mappings
do not and cannot change the places where the compiler looks for its
headers.
The user who installs XPM is the one who decides where its headers
will be. MSYS2 cannot possibly change that.
prev parent reply other threads:[~2014-08-22 13:25 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
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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tx54mzbl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18302@debbugs.gnu.org \
--cc=angelo.graziosi@alice.it \
/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.