unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Andreas Schwab <schwab@suse.de>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: add etc/PROBLEMS entry for building 32-bit exe on 64-bit system
Date: Wed, 10 Jan 2007 10:28:30 -0500	[thread overview]
Message-ID: <jwv7ivunbzu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <yf7ivvselx.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue\, 09 Jan 2007 23\:14\:02 -0500")

> Actually, I don't know any more if I'm asking for a reasonable thing.
> Should I expect to be able to _compile_ 32-bit apps on an x86_64
> system, or just _run_ them? The fact that almost none of the OS
> "devel" packages exist in 32-bit form suggests the latter.

I for one have compiled Emacs in 32bit-mode on an amd64 machine in two
difference circumstances:

- once on my home machine which is a Debian GNU/Linux x86 system (no amd64
  lib or compiler installed) with an amd64 kernel (mostly to get access to
  more than 3GB of ram, although a bigmem kernel would have done the trick
  as well).

- once on my work machine, which is running a version of Fedora for amd64
  and where some of the 32bit libs are indeed missing.  There's still plenty
  of libs to build Emacs.  The main reason there was to test the 32bit
  build, as well as to get a build which uses less memory.


        Stefan

  reply	other threads:[~2007-01-10 15:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09  1:44 add etc/PROBLEMS entry for building 32-bit exe on 64-bit system Glenn Morris
2007-01-09  9:58 ` Andreas Schwab
2007-01-09 21:08   ` Richard Stallman
2007-01-09 22:30     ` Andreas Schwab
2007-01-10  0:25       ` Glenn Morris
2007-01-10  4:14         ` Glenn Morris
2007-01-10 15:28           ` Stefan Monnier [this message]
2007-01-10 20:17             ` Glenn Morris
2007-01-10 20:36             ` Eli Zaretskii
2007-01-10 23:28               ` Stefan Monnier
2007-01-16  1:22                 ` Glenn Morris
2007-01-16  9:58                   ` Andreas Schwab
2007-01-16 14:40                   ` Stefan Monnier
2007-01-10 23:05           ` Richard Stallman
2007-01-11  1:52             ` Glenn Morris
2007-01-14 23:23           ` Richard Stallman
2007-01-15  6:23           ` Giorgos Keramidas
2007-01-10  9:41         ` Andreas Schwab
2007-01-10 19:31           ` Glenn Morris
2007-01-10 20:00             ` Andreas Schwab
2007-01-10 20:14               ` Glenn Morris
2007-01-10 20:23                 ` Andreas Schwab
2007-01-10 20:16             ` Stuart D. Herring
2007-01-10 20:42             ` Eli Zaretskii
2007-01-10 18:46         ` Richard Stallman
2007-01-13  2:26           ` Glenn Morris
2007-01-09 17:57 ` Richard Stallman
2007-01-15  6:21 ` Giorgos Keramidas
2007-01-15  9:54   ` Andreas Schwab
2007-01-15 20:27   ` Glenn Morris
2007-01-15 23:28   ` Richard Stallman
2007-01-15 23:33     ` Giorgos Keramidas
2007-01-19 15:36       ` Giorgos Keramidas

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=jwv7ivunbzu.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=schwab@suse.de \
    /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).