unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 11669@debbugs.gnu.org
Subject: bug#11669: 24.1; Build failure on amd64 with x32 ABI
Date: Mon, 11 Jun 2012 22:27:53 +0200	[thread overview]
Message-ID: <20438.21705.2229.857235@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <o21ulmibx3.fsf@fencepost.gnu.org>

>>>>> On Mon, 11 Jun 2012, Glenn Morris wrote:

> So I guess you don't define i386 but rather __ILP32__ for some
> reason?

For x32, GCC defines both __x86_64__ and __ILP32__ (but not i386).
And the canonical system name is x86_64-pc-linux-gnu.

Size of long and of pointers is the same between i386 and x32.
However, x32 has native 64 bit support, so programs will get access to
64 bit registers for 64 bit types (e.g., long long).

> However, the src/m files have been removed in the trunk and the
> above piece of configure with it.

>>>>> On Mon, 11 Jun 2012, Glenn Morris wrote:

>> emacs-24's configure.in already attempts to deal with this kind of
>> thing:

> I didn't look at the context of your patch; obviously you knew that.

> I wonder if the removal of src/m/ in the trunk means it Just Works
> now?

Right, I haven't noticed any problems with the trunk.

Will 24.2 be released from the trunk or from the emacs-24 branch?





  parent reply	other threads:[~2012-06-11 20:27 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
2012-06-11 18:30   ` Glenn Morris
2012-06-11 20:27   ` Ulrich Mueller [this message]
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

  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=20438.21705.2229.857235@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=11669@debbugs.gnu.org \
    --cc=rgm@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).