From: "Vincent Belaïche" <vincent.b.1@hotmail.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "eggert@cs.ucla.edu" <eggert@cs.ucla.edu>,
emacs-devel <emacs-devel@gnu.org>
Subject: RE: Latest EMACS on BZR trunk does not compile with MinGW
Date: Wed, 4 Jun 2014 15:17:38 +0200 [thread overview]
Message-ID: <DUB109-W941EB2F1B51E105D799F5D84220@phx.gbl> (raw)
In-Reply-To: <83lhtd892x.fsf@gnu.org>
No, not to my recollection.
Please not that I have also a ~/.bash_profile file. It seems that neither it, nor /etc/profile are loaded by rxvt or sh on my machine.
Also in the /etc/profile, the relevant code is
if [ -z "$MSYSTEM" ]; then
MSYSTEM=MINGW32
fi
shouldn't it be with export, ie
if [ -z "$MSYSTEM" ]; then
export MSYSTEM=MINGW32
fi
Or maybe somewhere MSYSTEM variable is already tagged as exported.
Anyway, although my build is not yet complete, it seems that already it went beyond what has happened.
Vincent.
----------------------------------------
> Date: Wed, 4 Jun 2014 09:47:34 +0300
> From: eliz@gnu.org
> Subject: Re: Latest EMACS on BZR trunk does not compile with MinGW
> To: vincent.b.1@hotmail.fr
> CC: eggert@cs.ucla.edu; emacs-devel@gnu.org
>
>> From: Vincent Belaïche <vincent.b.1@hotmail.fr>
>> CC: emacs-devel <emacs-devel@gnu.org>
>> Date: Tue, 3 Jun 2014 23:21:19 +0200
>>
>> Yep, MSYSTEM was simply not defined under my MSYS shell
>
> How did that happen? Did you edit your MSYS etc/profile file?
>
>
>
next prev parent reply other threads:[~2014-06-04 13:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 20:00 Latest EMACS on BZR trunk does not compile with MinGW Vincent Belaïche
2014-06-03 20:22 ` Paul Eggert
2014-06-03 20:56 ` Óscar Fuentes
2014-06-03 21:15 ` Eli Zaretskii
2014-06-03 21:21 ` Vincent Belaïche
2014-06-04 6:47 ` Eli Zaretskii
2014-06-04 13:17 ` Vincent Belaïche [this message]
2014-06-04 13:31 ` Eli Zaretskii
2014-06-04 15:28 ` Vincent Belaïche
2014-06-04 15:44 ` Eli Zaretskii
2014-06-04 15:54 ` Dani Moncayo
2014-06-04 16:05 ` Eli Zaretskii
2014-06-04 21:50 ` Dani Moncayo
2014-06-05 0:42 ` Stefan Monnier
2014-06-05 2:51 ` Eli Zaretskii
2014-06-05 3:40 ` Óscar Fuentes
2014-06-05 7:03 ` Dani Moncayo
2014-06-05 9:03 ` Vincent Belaïche
2014-06-05 15:09 ` Eli Zaretskii
2014-06-05 14:51 ` Eli Zaretskii
2014-06-05 16:19 ` Óscar Fuentes
2014-06-05 17:52 ` Eli Zaretskii
2014-06-05 13:31 ` Stefan Monnier
2014-06-05 15:15 ` Eli Zaretskii
2014-06-05 16:50 ` Stefan Monnier
2014-06-05 18:07 ` Eli Zaretskii
2014-06-05 19:35 ` Paul Eggert
2014-06-05 19:54 ` Eli Zaretskii
2014-06-10 19:25 ` Dani Moncayo
2014-06-10 20:21 ` Eli Zaretskii
2014-06-05 20:54 ` Stefan Monnier
2014-06-05 2:47 ` Eli Zaretskii
2014-06-04 12:22 ` Using Qunsupported__w32_dialog Dmitry Antipov
2014-06-04 13:09 ` Eli Zaretskii
2014-06-04 13:37 ` Dmitry Antipov
2014-06-04 13:47 ` Eli Zaretskii
2014-06-04 14:06 ` Eli Zaretskii
2014-06-03 21:14 ` Latest EMACS on BZR trunk does not compile with MinGW 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=DUB109-W941EB2F1B51E105D799F5D84220@phx.gbl \
--to=vincent.b.1@hotmail.fr \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).