From: Christian Franke <Christian.Franke@t-online.de>
To: grub-devel@gnu.org
Subject: NEED_REGISTER_FRAME_INFO can be replaced by -static-libgcc
Date: Tue, 13 Apr 2010 21:10:01 +0200 [thread overview]
Message-ID: <4BC4C189.6020409@t-online.de> (raw)
Hi,
a note regarding this fix:
2010-04-11 Vladimir Serbinenko <...>
Fix cygwin compilation.
* configure.ac: Define NEED_REGISTER_FRAME_INFO.
* include/grub/misc.h (__register_frame_info)
[NEED_REGISTER_FRAME_INFO && !UTIL]: New export.
(__deregister_frame_info) [NEED_REGISTER_FRAME_INFO && !UTIL]:
Likewise.
* kern/misc.c (__register_frame_info)
[NEED_REGISTER_FRAME_INFO && !UTIL]: New empty function.
(__deregister_frame_info) [NEED_REGISTER_FRAME_INFO && !UTIL]:
Likewise.
--- configure.ac 2010-04-11 14:14:51 +0000
+++ configure.ac 2010-04-12 14:58:44 +0000
@@ -376,7 +376,11 @@
# For platforms where ELF is not the default link format.
AC_MSG_CHECKING([for command to convert module to ELF format])
case "${host_os}" in
- cygwin) TARGET_OBJ2ELF='grub-pe2elf' ;;
+ cygwin) TARGET_OBJ2ELF='grub-pe2elf';
+# FIXME: put proper test here
+ AC_DEFINE([NEED_REGISTER_FRAME_INFO], 1,
+ [Define to 1 if GCC generates calls to __register_frame_info()])
+ ;;
*) ;;
The *_frame_info symbols are set undefined to force linkage of the
libgcc_s shared library or dll.
This can be prevented by TARGET_LDFLAGS=-static-libgcc. To build from
grub-1.98 tarball on Cygwin, run configure with this argument.
May also be necessary on other build platforms when -shared-libgcc is
the default. It may be possible simply set -static-libgcc unconditionally.
--
Regards,
Christian Franke
next reply other threads:[~2010-04-13 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 19:10 Christian Franke [this message]
2010-04-13 19:24 ` NEED_REGISTER_FRAME_INFO can be replaced by -static-libgcc Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-14 10:35 ` Christian Franke
2010-04-17 20:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-19 15:13 ` Christian Franke
2010-04-24 21:19 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4BC4C189.6020409@t-online.de \
--to=christian.franke@t-online.de \
--cc=grub-devel@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox