From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: "Po Lu" <luangruo@yahoo.com>, "Alan Third" <alan@idiocy.org>,
55846@debbugs.gnu.org, "Joakim Verona" <joakim@verona.se>,
"Jan Djärv" <jan.h.d@swipnet.se>
Subject: bug#55846: make bootstrap -j2 fails on macOS
Date: Thu, 09 Jun 2022 15:29:59 +0200 [thread overview]
Message-ID: <878rq655ig.fsf@gnus.org> (raw)
In-Reply-To: <DB817AA7-2321-472C-9FBE-57CDAD8DA8C7@acm.org> ("Mattias Engdegård"'s message of "Wed, 8 Jun 2022 12:52:04 +0200")
Mattias Engdegård <mattiase@acm.org> writes:
> Just making one target depend on the other, as in the diff below,
> makes it work, but I'm not sure of the purpose of ns_check_file.
Let's see...
if test "$HAVE_NS" = "yes"; then
if test "$NS_IMPL_GNUSTEP" = yes; then
AC_CONFIG_FILES([nextstep/GNUstep/Emacs.base/Resources/Info-gnustep.plist:nextstep/templates/Info-gnustep.plist.in \
nextstep/GNUstep/Emacs.base/Resources/Emacs.desktop:nextstep/templates/Emacs.desktop.in])
ns_check_file=Resources/Info-gnustep.plist
else
AC_CONFIG_FILES([nextstep/Cocoa/Emacs.base/Contents/Info.plist:nextstep/templates/Info.plist.in \
nextstep/Cocoa/Emacs.base/Contents/Resources/English.lproj/InfoPlist.strings:nextstep/templates/InfoPlist.strings.in])
ns_check_file=Contents/Info.plist
fi
AC_SUBST(ns_check_file)
fi
Uhm... OK, still not sure. Seems like this was added by
commit 63dae8e97d343fd4ebfe3dc08f0e8dc932630a4c
Author: Joakim Verona <joakim@verona.se>
AuthorDate: Tue Sep 10 23:52:26 2013 +0200
but the commit is just "merge upstream". I've added Joakim to the CCs;
perhaps he remembers.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-09 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 10:41 bug#55846: make bootstrap -j2 fails on macOS Mattias Engdegård
2022-06-08 10:52 ` Mattias Engdegård
2022-06-09 13:29 ` Lars Ingebrigtsen [this message]
2022-06-09 13:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 14:26 ` Mattias Engdegård
2022-06-10 8:35 ` Mattias Engdegård
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=878rq655ig.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55846@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=jan.h.d@swipnet.se \
--cc=joakim@verona.se \
--cc=luangruo@yahoo.com \
--cc=mattiase@acm.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).