From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 37852@debbugs.gnu.org
Subject: bug#37852: Build failure on MSYS2 (undefined reference to _chk functions)
Date: Mon, 21 Oct 2019 19:01:20 +0300 [thread overview]
Message-ID: <837e4y2ilr.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ohc_xomY331aJVYPnLhNK+=Jcw=Mmeb8OR2j=ar0LAiFg@mail.gmail.com> (message from Richard Copley on Mon, 21 Oct 2019 15:04:34 +0100)
> From: Richard Copley <rcopley@gmail.com>
> Date: Mon, 21 Oct 2019 15:04:34 +0100
> Cc: 37852@debbugs.gnu.org
>
> or is this an option you
> added manually?
>
> No, I built in a clean checkout of master, with these commands:
>
> ./autogen.sh
> ./configure --without-pop --without-dbus --without-gconf --without-gsettings "CFLAGS=-O2"
> make
Hmm... okay, could you please grep Makefiles in lib-src/ and src/, and
see if FORTIFY_SOURCE appears in any of them? If not, I guess the
references to those _chk functions are coming from some libraries
linked into the programs we compile, and that probably means we need
to use -lssp for MinGW just in case?
Possibly relevant discussion:
https://github.com/msys2/MINGW-packages/issues/5803
next prev parent reply other threads:[~2019-10-21 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 12:28 bug#37852: Build failure on MSYS2 (undefined reference to _chk functions) Richard Copley
2019-10-21 13:07 ` Eli Zaretskii
2019-10-21 13:17 ` Richard Copley
2019-10-21 13:31 ` Eli Zaretskii
2019-10-21 14:04 ` Richard Copley
2019-10-21 16:01 ` Eli Zaretskii [this message]
2019-10-21 16:05 ` Andy Moreton
2019-10-21 16:36 ` Eli Zaretskii
2019-10-21 16:55 ` Eli Zaretskii
2019-10-22 0:40 ` Paul Eggert
2019-10-22 2:37 ` Eli Zaretskii
2019-10-22 18:27 ` Paul Eggert
2019-10-22 18:51 ` Eli Zaretskii
2019-10-23 21:29 ` Richard Copley
2019-10-24 13:50 ` 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=837e4y2ilr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37852@debbugs.gnu.org \
--cc=rcopley@gmail.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 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).