From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: gdb@sourceware.org
Subject: [RFC] The never ending 32-bit vs. 64-bit blues
Date: Mon, 07 Nov 2005 22:45:00 -0000 [thread overview]
Message-ID: <200511072245.jA7MjnIL005849@elgar.sibelius.xs4all.nl> (raw)
In the past we have had a lot of bug reports from people trying to
debug 64-bit programs with a native 32-bit gdb. As far as I know we
don't support any native configuration that allows this. I've never
quite managed to come up with a satisfactory solution to deal with
this. Here's an attempt to deal with it by making configure complain.
Any opinions about this?
Mark
Index: configure.ac
===================================================================
RCS file: /cvs/src/src/gdb/configure.ac,v
retrieving revision 1.24
diff -u -p -r1.24 configure.ac
--- configure.ac 25 Jul 2005 15:08:40 -0000 1.24
+++ configure.ac 7 Nov 2005 22:34:19 -0000
@@ -34,6 +34,19 @@ AM_PROG_CC_STDC
AC_CONFIG_AUX_DIR(`cd $srcdir;pwd`/..)
AC_CANONICAL_SYSTEM
+# Sanity check; refuse to build a native GDB for a 64-bit target with
+# a 32-bit compiler.
+AC_CHECK_SIZEOF(void *)
+if test "${target}" = "${host}"; then
+ case "$host_cpu" in
+ hppa64|mips64*|powerpc64|sparc64|x86_64)
+ if test $ac_cv_sizeof_void_p != 8; then
+ AC_MSG_ERROR(
+[building native target ${host} with a 32-bit compiler is not supported])
+ fi
+ esac
+fi
+
dnl List of object files and targets accumulated by configure.
CONFIG_OBS=
next reply other threads:[~2005-11-07 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 22:45 Mark Kettenis [this message]
2005-11-07 22:50 ` Jim Ingham
2005-11-07 22:52 ` David Lecomber
2005-11-07 22:59 ` Daniel Jacobowitz
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=200511072245.jA7MjnIL005849@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).