unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: add etc/PROBLEMS entry for building 32-bit exe on 64-bit system
Date: Fri, 19 Jan 2007 17:36:03 +0200	[thread overview]
Message-ID: <20070119153603.GB30252@kobe.laptop> (raw)
In-Reply-To: <20070115233355.GA5125@kobe.laptop>

On 2007-01-16 01:33, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote:
> On 2007-01-15 18:28, Richard Stallman <rms@gnu.org> wrote:
> >     I don't really think the text below is correct.
> > 
> >     I have been building 32-bit versions of Emacs 22 on Solaris amd64
> >     systems for several months now, and the build works fine.  This means
> >     that, at least the following part of the text below is false:
> > 
> > Can you write text that is more correct?
> 
> Yes.
> 
> Please note that I haven't been able to build a 64-only version of Emacs
> on Solaris amd64; Emacs 22.X crashes during the autoload stage of the
> bootstrap process, when I try to build a 64-bit binary on Solaris.
> 
> Nevertheless, I can definitely help with writing the text for 32-bit
> builds for Solaris and FreeBSD.  For other systems, I may need some help
> from people who are more experienced in their use, and have more current
> installations than me.

Hi all,

I posted the following to rms@gnu.org, but forgot to Cc: the list, so
here it is, in case anyone else has time to review the text too:

%%
diff -r 1f853b6e3574 -r 59b73f6c6f46 ChangeLog
--- a/ChangeLog	Fri Jan 19 07:10:51 2007 +0200
+++ b/ChangeLog	Fri Jan 19 17:04:43 2007 +0200
@@ -1,3 +1,8 @@ 2007-01-18  Bruno Haible  <bruno@clisp.o
+2007-01-19  Giorgos Keramidas  <keramida@ceid.upatras.gr> (tiny change)
+
+	* etc/MACHINES: Describe how 32-bit and 64-bit versions of Emacs
+	  can be compiled on Solaris systems.
+
 2007-01-18  Bruno Haible  <bruno@clisp.org> (tiny change)
 
 	* INSTALL: Info files moved to share/info.
diff -r 1f853b6e3574 -r 59b73f6c6f46 etc/MACHINES
--- a/etc/MACHINES	Fri Jan 19 07:10:51 2007 +0200
+++ b/etc/MACHINES	Fri Jan 19 17:04:43 2007 +0200
@@ -1021,11 +1021,27 @@ Sun 3, Sun 4 (sparc), Sun 386 (m68k-sun-
 			       sparc-sun-sunos4.1.3noshr, sparc-sun-solaris2.*,
 			       i386-sun-solaris2.*, sparc*-*-linux-gnu)
 
+  To build a 32-bit Emacs (i.e. if you are having any sort of problem
+  bootstrapping a 64-bit version), you can use the Sun Studio compiler
+  and configure Emacs with:
+
+    env CC="cc -xarch=v7" CFLAGS='' ./configure    # on SPARC systems
+    env CC="cc -xarch=386" CFLAGS='' ./configure   # on x86 systems
+
+  On Solaris 2.10, it is also possible to use /usr/sfw/bin/gcc to build
+  a 32-bit version of Emacs.  Just make sure you point ./configure to
+  the right compiler:
+
+    env CC='/usr/sfw/bin/gcc -m32' ./configure
+
   To build a 64-bit Emacs (with larger maximum buffer size and
   including large file support) on a Solaris system which supports
   64-bit executables, use the Sun compiler, configuring something like
   this (see the cc documentation for information on 64-bit
-  compilation):  env CC="cc -xarch=v9" ./configure
+  compilation):
+
+    env CC="cc -xarch=v9" CFLAGS='' ./configure    # on SPARC systems
+    env CC="cc -xarch=amd64" CFLAGS='' ./configure # on x86 systems
 
   As of version 2.95, GCC doesn't support the 64-bit ABI properly, but
   later releases may.
%%

There is a buglet in the version I posted to Richard.  The last command,
which can be used to build a 64-bit Emacs on Solaris uses -xarch=386,
which should be replaced with the version shown above (-xarch=amd64).

Regards,
Giorgos

      reply	other threads:[~2007-01-19 15:36 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
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 [this message]

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=20070119153603.GB30252@kobe.laptop \
    --to=keramida@ceid.upatras.gr \
    --cc=emacs-devel@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).