unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
Subject: add etc/PROBLEMS entry for building 32-bit exe on 64-bit system
Date: Mon, 08 Jan 2007 20:44:58 -0500	[thread overview]
Message-ID: <ex3b6lezxh.fsf@fencepost.gnu.org> (raw)


I suggest adding something like the following to etc/PROBLEMS and
etc/TODO. I not infrequently want to compile 32-bit apps on 64-bit
systems (so that they can be run on otherwise identical 64- and 32-bit
systems).



*** PROBLEMS    16 Dec 2006 14:00:15 -0000 1.202
--- PROBLEMS    9 Jan 2007 01:39:51 -0000
***************
*** 2355,2360 ****
--- 2355,2366 ----
  the problem, install the current version of GNU Sed, then rerun
  Emacs's configure script.
  
+ *** Building a 32-bit executable on a 64-bit GNU/Linux architecture fails.
+ 
+ For example, if CFLAGS=-m32 is passed to configure, the resulting
+ build will fail.  There is no fix for this problem at present - when
+ building on a 64-bit platform, you must build a 64-bit executable.
+ 
  *** Building the Cygwin port for MS-Windows can fail with some GCC
      version
  
  Building Emacs 22 with Cygwin builds of GCC 3.4.4-1 and 3.4.4-2 is


*** TODO   2 Jan 2007 18:29:37 -0000   1.137
--- TODO   9 Jan 2007 01:40:09 -0000
***************
*** 159,164 ****
--- 159,167 ----
  
  * Other features we would like:
  
+ ** Make it possible to build a 32-bit executable on 64-bit systems.
+   See http://lists.gnu.org/archive/html/emacs-pretest-bug/2006-10/msg00462.html
+ 
  ** Remove the default toggling behavior of minor modes when called from elisp
  rather than interactively.  This a trivial one-liner in easy-mode.el.
  ** Create a category of errors called `user-error' for errors which are

             reply	other threads:[~2007-01-09  1:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09  1:44 Glenn Morris [this message]
2007-01-09  9:58 ` add etc/PROBLEMS entry for building 32-bit exe on 64-bit system 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
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=ex3b6lezxh.fsf@fencepost.gnu.org \
    --to=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).