From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org
Subject: Re: Posix build on Windows: parallel `make' broken
Date: Mon, 03 Jun 2013 19:58:39 +0300 [thread overview]
Message-ID: <837gibxha8.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SRzJQf-a3jMmiQchcWbubDZ3+zFL+Qwu7YDO=ZprpMQtg@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 3 Jun 2013 17:47:40 +0200
> Cc: Óscar Fuentes <ofv@wanadoo.es>,
> Emacs developers <emacs-devel@gnu.org>
>
> A few comments about INSTALL.MSYS:
Thanks.
> - It says that GTK includes PNG, JPEG and TIFF libraries. PNG is in
> its own standalone package, but in a not-exhaustive check, I didn't
> find JPEG and TIFF libraries here. Perhaps a pointer could be useful.
I just removed the reference to JPEG and TIFF. (Perhaps they are
included in some other package; if someone knows, please tell.)
> - The example invocation of msysconfig.sh says:
>
> CPPFLAGS='-DGLYPH_DEBUG=1' CFLAGS='-O0 -g3' ./nt/msysconfig.sh
> --prefix=PREFIX --enable-checking
>
> but I suppose -DGLYPH_DEBUG=1 shouldn't be required if using
> --enable-checking=yes,glyphs, should it?
Old habits die hard, and that is just an example. If you have better
examples, I'm all ears.
> - You mentioned in a thread that the way to make a binary tarball is
> to use "make install prefix=SOMEWHERE" and then create a tar archive
> from SOMEWHERE. That should be mentioned, I think; also, that
> procedure does not copy libXpm.dll (which the configure.bat based
> build method could do by using --distfiles), so that should be noted
> too.
I'd prefer that someone who actually did that describe this.
> - There's now a --with-file-notification=w32 option that isn't on by
> default. Perhaps worth mentioning?
It is on by default. I don't see why it should be mentioned when
other configure options aren't.
> > Do you have EMACSLOADPATH set in the environment or something?
>
> Aha. No, I don't have EMACSLOADPATH in the environment, but yesterday
> I did a "make install" of some older release and it added
> EMACSLOADPATH (and friends) to the registry. Removing these makes the
> warning disappear.
Good. One more mystery eats dust.
Thanks.
next prev parent reply other threads:[~2013-06-03 16:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 23:59 Posix build on Windows: parallel `make' broken Óscar Fuentes
2013-06-02 2:48 ` Eli Zaretskii
2013-06-02 4:07 ` Juanma Barranquero
2013-06-02 15:14 ` Eli Zaretskii
2013-06-02 15:55 ` Juanma Barranquero
2013-06-03 1:06 ` Juanma Barranquero
2013-06-03 2:52 ` Eli Zaretskii
2013-06-03 3:41 ` Juanma Barranquero
2013-06-03 15:30 ` Eli Zaretskii
2013-06-03 15:47 ` Juanma Barranquero
2013-06-03 16:58 ` Eli Zaretskii [this message]
2013-06-03 21:06 ` Juanma Barranquero
2013-06-02 10:04 ` Óscar Fuentes
2013-06-02 15:30 ` Eli Zaretskii
2013-06-02 18:22 ` Óscar Fuentes
2013-06-02 18:36 ` Eli Zaretskii
2013-06-02 19:10 ` Óscar Fuentes
2013-06-02 19:18 ` Eli Zaretskii
2013-06-02 19:41 ` Óscar Fuentes
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=837gibxha8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=ofv@wanadoo.es \
/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).