From: Glenn Morris <rgm@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 11669@debbugs.gnu.org
Subject: bug#11669: 24.1; Build failure on amd64 with x32 ABI
Date: Mon, 11 Jun 2012 02:46:00 -0400 [thread overview]
Message-ID: <o21ulmibx3.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20436.63644.849695.332693@a1i15.kph.uni-mainz.de> (Ulrich Mueller's message of "Sun, 10 Jun 2012 21:42:20 +0200")
Ulrich Mueller wrote:
> + AC_CHECK_DECL([__ILP32__], [machfile="m/intel386.h"])
emacs-24's configure.in already attempts to deal with this kind of
thing:
## Although we're running on an amd64 kernel, we're actually compiling for
## the x86 architecture. The user should probably have provided an
## explicit --build to `configure', but if everything else than the kernel
## is running in i386 mode, we can help them out.
if test "$machine" = "amdx86-64"; then
AC_CHECK_DECL([i386])
if test "$ac_cv_have_decl_i386" = "yes"; then
canonical=`echo "$canonical" | sed -e 's/^amd64/i386/' -e 's/^x86_64/i386/'`
machine=intel386
machfile="m/${machine}.h"
fi
fi
So I guess you don't define i386 but rather __ILP32__ for some reason?
However, the src/m files have been removed in the trunk and the above
piece of configure with it.
http://lists.gnu.org/archive/html/emacs-diffs/2012-05/msg00352.html
I don't know what, if anything, replaces it.
Is passing an explicit --build to configure now the recommended/only way
to deal with this?
next prev parent reply other threads:[~2012-06-11 6:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 19:42 bug#11669: 24.1; Build failure on amd64 with x32 ABI Ulrich Mueller
2012-06-11 6:46 ` Glenn Morris [this message]
2012-06-11 18:30 ` Glenn Morris
2012-06-11 20:27 ` Ulrich Mueller
2012-06-11 20:52 ` Glenn Morris
2012-06-15 6:21 ` Ulrich Mueller
2012-06-21 7:13 ` Glenn Morris
2012-06-21 19:36 ` Ulrich Mueller
2012-06-21 19:44 ` Glenn Morris
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=o21ulmibx3.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=11669@debbugs.gnu.org \
--cc=ulm@gentoo.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 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.