From: martin rudalics <rudalics@gmx.at>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 35410@debbugs.gnu.org
Subject: bug#35410: 27.0.50; 32-bit build of master failing with MSYS2
Date: Fri, 12 Jul 2019 10:12:01 +0200 [thread overview]
Message-ID: <2966c5b8-fa09-f465-190a-f125dfeeab28@gmx.at> (raw)
In-Reply-To: <85muhkctw1.fsf@gmail.com>
>> w32.o:w32.c:(.text+0xa29f): undefined reference to `_imp___futime32'
>> collect2.exe: error: ld returned 1 exit status
>> make[1]: *** [Makefile:643: temacs.exe] Fehler 1
>> make[1]: Verzeichnis „/c/emacs/trunk/opt-32/src“ wird verlassen
>> make: *** [Makefile:423: src] Fehler 2
>>
>> A build configured with CFLAGS='-O0 -g3' proceeds without problems.
>> The 32-builds use gcc 7.4.0. 64-bit builds with the same options
>> proceed without problems using gcc 8.3.0.
>
> Seems to work okay here, but my ming32 gcc is 7.2.0. Is this still a
> problem?
Yes. With slight changes in the Makefile references:
CCLD temacs.exe
w32.o:w32.c:(.text+0xa27f): undefined reference to `_imp___futime32'
collect2.exe: error: ld returned 1 exit status
make[1]: *** [Makefile:651: temacs.exe] Fehler 1
make[1]: Verzeichnis „/c/emacs/trunk/opt-32/src“ wird verlassen
make: *** [Makefile:424: src] Fehler 2
In an earlier conversation with Eli I wrote
> > An optimized 32-bit build apparently does not recognize
> >
> > #ifndef __MINGW64_VERSION_MAJOR
and he told me
> So I guess we need to find an alternative to
> __MINGW64_VERSION_MAJOR that will work in the 32-bit MinGW64 builds.
> Look for macros that include "_VERSION_" or "_MAJOR" in the MinGW64
> headers.
but I had no good idea how to continue.
martin
next prev parent reply other threads:[~2019-07-12 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 7:28 bug#35410: 27.0.50; 32-bit build of master failing with MSYS2 martin rudalics
2019-07-11 18:23 ` Noam Postavsky
2019-07-12 8:12 ` martin rudalics [this message]
2019-07-12 15:28 ` Noam Postavsky
2019-07-12 16:52 ` martin rudalics
2019-10-09 18:11 ` martin rudalics
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=2966c5b8-fa09-f465-190a-f125dfeeab28@gmx.at \
--to=rudalics@gmx.at \
--cc=35410@debbugs.gnu.org \
--cc=npostavs@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 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.