[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: `print' does not print
From: |
Ralf Fassel |
Subject: |
Re: `print' does not print |
Date: |
Tue, 26 Mar 2002 18:30:32 +0100 |
* David Kaelbling
| > Great, so it seems that the SGI-specific patch in unexelf.c is
| > unnecessary and even dangerous, and should be taken out.
|
| It wouldn't surprise me, but is that really what Ralf said?
I wasn't quite sure about that statement either. I could not
reproduce the problems the `.got' statements were meant to solve, but
I'm not sure that this means that they might go away. They might help
in a different environment (which I obviously not have, since emacs
works at my site w/o those statements).
What I have found is that you need an upgraded IRIX version (at least
6.5.10 it seems) to make these `.got' statements work with gcc
compilation.
I also found that cc compilation seems to works in any case (21.1 and
21.2, contrary to the comments in 21.2 unexelf.c that require the
`.got' sections).
| I'm probably confused,
AOL :-)
Summary:
========
`prints' means:
emacs -batch -no-site-file -eval '(print emacs-version)'
prints the version number on both IRIX version.
`does not print' means:
the above command line does not print the version number on no
IRIX version.
The problem seems to be that stdio output is broken, since none of
the stdio functions produce any output. The plain I/O system
calls like write(2) do work, however.
There wasn't the situation that it printed on one OS and not on the
other. Either it printed on both or on none.
compiled =~ gmake temacs, i.e. compile all objects and link temacs,
then stop
dumped =~ gmake emacs, i.e. temacs has been built previously, now
produce the emacs executable
gcc version 2.95.3 20010315 (release)
cc MIPSpro Compilers: Version 7.30
OS IRIX 6.5.9f and 6.5.15m
Custom libraries:
- static libz 1.1.4
- static libtiff v3.4beta037
- static libpng 1.0.8
Configurations tested:
======================
Emacs version | compiled with | compiled on | dumped on | prints
----------------------------------------------------------------
21.2 gcc -g 6.5.9f 6.5.9f no
21.2 gcc -g 6.5.15m 6.5.9f no
21.2 gcc -g 6.5.9f 6.5.15m yes
21.2 gcc -g 6.5.15m 6.5.15m yes
21.2 cc -g * * yes
----------------------------------------------------------------
21.1 * -g * * yes
----------------------------------------------------------------
I had no core dumps during compilation/dumping in any configuration.
R'
- Re: `print' does not print, (continued)
- Re: `print' does not print, Ralf Fassel, 2002/03/25
- Re: `print' does not print, David Kaelbling, 2002/03/25
- Re: `print' does not print, Eli Zaretskii, 2002/03/25
- Re: `print' does not print, Ralf Fassel, 2002/03/25
- Re: `print' does not print, Eli Zaretskii, 2002/03/26
- Re: `print' does not print, David Kaelbling, 2002/03/26
- Re: `print' does not print,
Ralf Fassel <=
- Re: `print' does not print, Eli Zaretskii, 2002/03/27
- Re: `print' does not print, Ralf Fassel, 2002/03/27
- Re: `print' does not print, Eli Zaretskii, 2002/03/27
- Re: `print' does not print, Richard Stallman, 2002/03/25
Re: `print' does not print, Richard Stallman, 2002/03/22