From: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
To: 51583@debbugs.gnu.org
Subject: bug#51583: 29.0.50; cygw32 build break
Date: Wed, 03 Nov 2021 20:35:57 +0900 [thread overview]
Message-ID: <86y265xyhu.wl--xmue@d1.dion.ne.jp> (raw)
Cygw32 build fails on trunk.
$ ./configure --with-w32
$ make
(snip)
CCLD temacs.exe
/usr/lib/gcc/x86_64-pc-cygwin/10/../../../../x86_64-pc-cygwin/bin/ld: w32fns.o:w32fns.c:(.text+0xec1a): undefined reference to `w32_get_resource'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:647: temacs.exe] Error 1
make[1]: Leaving directory '/dfs/f/build/cygwin64/emacs/src'
make: *** [Makefile:450: src] Error 2
w32_get_resource function is defined in w32.c, which is not compiled
on Cygwin buid.
--
Kazuhiro Ito
next reply other threads:[~2021-11-03 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 11:35 Kazuhiro Ito [this message]
2021-11-03 14:15 ` bug#51583: 29.0.50; cygw32 build break Eli Zaretskii
2021-11-04 8:43 ` Kazuhiro Ito
2021-11-04 9:14 ` 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=86y265xyhu.wl--xmue@d1.dion.ne.jp \
--to=kzhr@d1.dion.ne.jp \
--cc=51583@debbugs.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).