unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Puneet Goel <pgoel@txc.stpn.soft.net>
Cc: 'Emacs Pretesters' <emacs-pretesters@gnu.org>,
	"Marshall, Simon" <simon.marshall@misys.com>,
	'Emacs Developers' <emacs-devel@gnu.org>,
	puneet <puneet@computer.org>
Subject: Re: Anyone built Emacs with gcc-3.3?
Date: Wed, 09 Jul 2003 07:31:05 -0500	[thread overview]
Message-ID: <xn6u19v286u.fsf@txc.stpn.soft.net> (raw)
In-Reply-To: <rzq65mctzdi.fsf@albion.dl.ac.uk> (Dave Love's message of "Tue, 08 Jul 2003 23:41:45 +0100")

>>>>> "Dave" == Dave Love <d.love@dl.ac.uk> writes:

    Dave> puneet <puneet@computer.org> writes:
    >> I have compiled emacs in gcc 3.3. Actually I configured gcc for
    >> sparcv9 arch. And hence my emacs is 64-bit.

    Dave> That doesn't follow.  -mcpu=v9 is orthogonal to -m64.

    Sorry, I did not know that. For record, I am not a software
    engineer. I am a hardware professional. And I needed 64-bit emacs
    to read big files. I do use gcc -m64 for building my emacs. I try
    building 64-bit emacs from emacs CVS almost once a week. Never
    faced a problem.

    I think I first successfully built 64-bit emacs some three months
    back. That was the time when our sys-admin upgraded my sparc
    machine to solaris 2.8. Our sys-admin is on leave, and I do not
    know a way to get patch information on my system. I believe he
    installed just the recommended patches from Sun.

    So I have been compiling and running 64-bit emacs versions 21.X
    and 21.3.50 on my solaris 2.8 for the past three months now
    without any issue. The only issue I face is when I set my display
    to a linux system, and launch 64-bit emacs on that display, emacs
    dumps core. 32-bit solaris emacs compiles work fine.

    I am sure that my emacs is 64-bit because ....

    1. I use gcc -m64 to compile that.
    2. I am able to open BIG files (200MB and more) with this
       emacs. 32-bit emacs gives "Maximum buffer size exceeded" for
       the same files.
    3. I had to compile 64-bit versions of all the required
       libraries. And my emacs is linked to 64-bit versions of sun
       libraries. here is the ldd output ....
$ ldd /home/pgoel/local/gnu/arch/sparcv9-sun-solaris2.8/bin/emacs
        libXaw3d.so.5 =>         /home/pgoel/local/gnu/arch/sparcv9-sun-solaris2.8/lib/libXaw3d.so.5
        libXmu.so.4 =>   /usr/lib/64/libXmu.so.4
        libXt.so.4 =>    /usr/lib/64/libXt.so.4
        libSM.so.6 =>    /usr/lib/64/libSM.so.6
        libICE.so.6 =>   /usr/lib/64/libICE.so.6
        libXext.so.0 =>  /usr/lib/64/libXext.so.0
        libtiff.so =>    /home/pgoel/local/gnu/arch/sparcv9-sun-solaris2.8/lib/libtiff.so
        libjpeg.so.62 =>         /home/pgoel/local/gnu/arch/sparcv9-sun-solaris2.8/lib/libjpeg.so.62
        libpng.so.3 =>   /home/pgoel/local/gnu/arch/sparcv9-sun-solaris2.8/lib/libpng.so.3
        libz.so =>       /home/pgoel/local/gnu/arch/sparcv9-sun-solaris2.8/lib/libz.so  
        libm.so.1 =>     /usr/lib/64/libm.so.1
        libungif.so.4 =>         /home/pgoel/local/gnu/arch/sparcv9-sun-solaris2.8/lib/libungif.so.4
        libXpm.so.4.11 =>        /home/pgoel/local/gnu/arch/sparcv9-sun-solaris2.8/lib/libXpm.so.4.11
        libX11.so.4 =>   /usr/lib/64/libX11.so.4
        libsocket.so.1 =>        /usr/lib/64/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/64/libnsl.so.1
        libkstat.so.1 =>         /usr/lib/64/libkstat.so.1
        libcurses.so.1 =>        /usr/lib/64/libcurses.so.1
        libc.so.1 =>     /usr/lib/64/libc.so.1
        libICE.so.6 (SUNWprivate) =>     (version not found)
        libICE.so.6 (SUNWprivate) =>     (version not found)
        libdl.so.1 =>    /usr/lib/64/libdl.so.1
        libdga.so.1 =>   /usr/openwin/lib/sparcv9/libdga.so.1
        libgcc_s.so.1 =>         /home/pgoel/local/gnu/arch/sparcv9-sun-solaris2.8/lib/sparcv9/libgcc_s.so.1
        libmp.so.2 =>    /usr/lib/64/libmp.so.2
        /usr/platform/SUNW,Ultra-60/lib/sparcv9/libc_psr.so.1



    Dave> 
    Dave> `file' will tell you whether the binary is 64-bit, but as
    Dave> far as I remember, you won't get 64-bit Emacs words with gcc
    Dave> anyhow since gcc doesn't define _LP64.  (gcc -m64 wasn't
    Dave> useful when I last touched 64-bit sparc configuration.)

          Well file does say that it is 64-bit version.

    Dave> 
    Dave> Somewhere I have some changes to somewhat sanitize 64-bit
    Dave> configuration, but as far as I know there are still some
    Dave> basic problems with 64-bit systems, especially big-endian
    Dave> ones, and I'm surprised they work at all...

          I am not competent to comment on these. The first time I
          compiled 64-bit emacs was sometimes in oct 2002. RMS had put
          a request on the emacs-pretesters list for testing on 64 bit
          machines. At that time, I could compile emacs. I could even
          run it with "emacs -nw". X11 emacs used to dump core. It
          seemed to be some openwin internal error. I had reported
          all this on the emacs-pretesters list.

          Now I work for a different organization. And 64-bit emacs
          compiles have been running fine since last 3 months. I use
          64-bit emacs for almost everything (including gnus etc.)

    Dave> If it behaves differently on different Solaris systems with
    Dave> the same OS version then you should probably look at all the
    Dave> installed patches, versions of development tools (I assume
    Dave> you use the Sun ld) and what you pick up from the system
    Dave> libraries -- the version of malloc in particular.

          I do use sun ld. I do not know how to check for which
          malloc I am using. Should I send you the config.log file??

    Dave> --

Regards
- p

--
Puneet Goel
TranSwitch India
--
LEAD me in the centre of thy silence
to fill my heart with songs.
-
Stray Birds, Rabindernath Tagore

--

  reply	other threads:[~2003-07-09 12:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-04  8:33 Anyone built Emacs with gcc-3.3? Marshall, Simon
2003-07-04  8:41 ` Dhruva Krishnamurthy
2003-07-04 16:17 ` puneet
2003-07-08 22:41   ` Dave Love
2003-07-09 12:31     ` Puneet Goel [this message]
2003-07-15 22:31       ` Dave Love
2003-07-05 22:25 ` Richard Stallman
2003-07-11  9:55   ` Paul Eggert
2003-07-11 22:52     ` Paul Eggert
2003-07-13 14:56       ` Simon Leinen
2003-07-14  5:52         ` Paul Eggert
2003-07-12  5:32     ` Richard Stallman
2003-07-08 22:30 ` Dave Love
  -- strict thread matches above, loose matches on Subject: below --
2003-07-04 12:36 Nelson H. F. Beebe
2003-07-07  8:26 Marshall, Simon
2003-07-08 14:28 ` Richard Stallman
2003-07-08 14:39   ` Jason Rumney
2003-07-09  5:34     ` Dhruva Krishnamurthy
2003-07-09  7:36       ` Pascal Obry
2003-07-09  7:59       ` Jason Rumney
2003-07-08 15:18 Marshall, Simon
2003-07-09 15:49 ` Richard Stallman
2003-07-11  9:57 ` Paul Eggert
2003-07-14 11:19 Marshall, Simon
     [not found] ` <3F12B8E7.2C387FE7@yk.rim.or.jp>
2003-07-14 14:41   ` Eric Botcazou
2003-07-14 17:47 ` Paul Eggert
2003-07-14 19:40   ` Eric Botcazou

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=xn6u19v286u.fsf@txc.stpn.soft.net \
    --to=pgoel@txc.stpn.soft.net \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretesters@gnu.org \
    --cc=puneet@computer.org \
    --cc=simon.marshall@misys.com \
    /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).