From: Eli Zaretskii <eliz@gnu.org>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: 55595@debbugs.gnu.org
Subject: bug#55595: 29.0.50; Compilation warnings on macOS
Date: Thu, 02 Jun 2022 22:10:32 +0300 [thread overview]
Message-ID: <83fskmev9z.fsf@gnu.org> (raw)
In-Reply-To: <m2sfomq5dh.fsf@me.com> (message from Rudolf Adamkovič on Thu, 02 Jun 2022 20:36:58 +0200)
> From: Rudolf Adamkovič <salutis@me.com>
> Cc: 55595@debbugs.gnu.org
> Date: Thu, 02 Jun 2022 20:36:58 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks, please try the latest master branch, where I tried to fix
> > that.
>
> I tried again at:
>
> 8f279c8666dc642ed1f8f49aa709530fcea47374
>
> Compile command:
>
> ./configure --with-json --with-native-compilation && make && make install
Did you regenerate configure before running the above? The change is
in configure.ac, so you need to run ./autogen.sh to regenerate the
configure script from configure.ac.
(In general, I suggest to always say "make && make install", because
that will run the configure script automatically when needed, and will
regenerate the configure script automatically when configure.ac was
updated.)
> comp.c:2816:24: warning: pragma diagnostic pop could not pop, no matching push [-Wunknown-pragmas]
> #pragma GCC diagnostic pop
> ^
> comp.c:4698:24: warning: pragma diagnostic pop could not pop, no matching push [-Wunknown-pragmas]
> #pragma GCC diagnostic pop
> ^
> comp.c:4714:24: warning: pragma diagnostic pop could not pop, no matching push [-Wunknown-pragmas]
> #pragma GCC diagnostic pop
> ^
> comp.c:4967:24: warning: pragma diagnostic pop could not pop, no matching push [-Wunknown-pragmas]
> #pragma GCC diagnostic pop
I guess this means you did not regenerate the configure script? Or
maybe the compiler doesn't identify itself as clang, so the changes I
did don't have effect?
next prev parent reply other threads:[~2022-06-02 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 15:42 bug#55595: 29.0.50; Compilation warnings on macOS Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 15:53 ` Eli Zaretskii
2022-05-23 16:10 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 16:28 ` Eli Zaretskii
2022-06-02 18:36 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-02 19:10 ` Eli Zaretskii [this message]
2022-06-03 19:37 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 6:06 ` Eli Zaretskii
2022-06-05 10:51 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-05 10:59 ` Eli Zaretskii
2022-11-20 0:07 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-20 7:29 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fskmev9z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55595@debbugs.gnu.org \
--cc=salutis@me.com \
/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.