9:03 p.m.
While trying to do a build on Solaris (sparc), I ran into this
problem:
Building finder database ...
rm -f /net/gondor/Volumes/share2/src/xemacs/hg/xemacs-21.5/src/../lisp/finder-inf.el
./xemacs -no-packages -batch -eval "(setq finder-compile-keywords-quiet t)"
\
-eval "(setq lisp-directory
\"/net/gondor/Volumes/share2/src/xemacs/hg/xemacs-21.5/src/../lisp\")" \
-l finder -f finder-compile-keywords
Loading auto-autoloads.el... (file auto-autoloads.elc is out-of-date)
Loading auto-autoloads.el... (file auto-autoloads.elc is out-of-date)
xemacs exiting.
Invalid argument: No buffer named, "*finder-scratch*"
To see what was going on, I tried a 64-bit build using Sun C instead
of gcc 4.5.2. This works fine and the result works ok too. In case
this was a gcc issue, I tried again using Sun C to do a 32-bit build.
This fails in the same way.
As a final test, I tried a 32-bit build on Linux using gcc 4.4.1. The
64-bit build works fine. However, the 32-bit build fails miserably
with error messages like:
gcc -c -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wshadow
-Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes
-Wdeclaration-after-statement -Wunused-parameter -g -m32 -Demacs -I.
-I/net/gondor/src/xemacs/hg/xemacs-21.5/src -DHAVE_CONFIG_H
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:107: warning: function declaration
isn't a prototype
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:120: warning: function declaration
isn't a prototype
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:130: warning: function declaration
isn't a prototype
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:143: warning: function declaration
isn't a prototype
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:236: error: expected '=',
',', ';', 'asm' or '__attribute__' before
'ospeed'
Anyone doing 32-bit builds these days? A 64-bit build is fine with
me, but I don't really need an editor that can edit multi-GB
files.:-)
I also get a few warnings on 32-bit Solaris about integer overflows.
I'll check those out and see if they're important or not.
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
9:28 p.m.
On Thu, May 26, 2011 at 2:03 PM, Raymond Toy <toy.raymond(a)gmail.com> wrote:
Anyone doing 32-bit builds these days? A 64-bit build is fine with
me, but I don't really need an editor that can edit multi-GB
files.:-)
I also get a few warnings on 32-bit Solaris about integer overflows.
I'll check those out and see if they're important or not.
Ray
I maintain the Fedora package. We build on 32-bit systems (primarily
x86, but there are groups working on Sparc, PPC, etc. ports). I don't
use any of those platforms myself; I've been on 64-bit x86 for about 6
years now. But I also haven't received notice of any build failures
from the distribution builders, nor any bug reports from 32-bit users.
The termcap.c failure is apparently due to speed_t not being defined.
On my system, I get the appropriate typedef from <termios.h>.
--
Jerry James
http://www.jamezone.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
10:32 p.m.
>>>> Jerry James <james(a)xemacs.org> writes:
The termcap.c failure is apparently due to speed_t not being
defined.
There seems to be problems with termcap on many systems. I know it is
a problem on Windows(cygwin) and just the other day I built XEmacs on
my eeepc running ubuntu and had to install curses just to stay away
from termcap. So it is not only a matter of what OS, compiler version
etc, that you have, but what packages are installed. With the right
setup the build can work.
Under the current situation it is more or less the question if we
should fix termcap or maybe drop it!?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:58 a.m.
Mats Lidell writes:
There seems to be problems with termcap on many systems.
Yeah, it doesn't exist any more on most systems, except as a
compatibility option in terminfo. I would say the thing to do is to
fix configure.ac to recognize that termcap or some dependency may not
exist, and to do something sane instead of allowing the build to barf.
Or drop it, but I don't know if every system supported by XEmacs
supports terminfo or similar. Certainly some of the systems recently
dropped did not, but I don't know if all such systems were dropped.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:24 a.m.
>>>> "Jerry" == Jerry James
<james(a)xemacs.org> writes:
Jerry> On Thu, May 26, 2011 at 2:03 PM, Raymond Toy <toy.raymond(a)gmail.com>
wrote:
> Anyone doing 32-bit builds these days? A 64-bit build is fine
with
> me, but I don't really need an editor that can edit multi-GB
> files.:-)
>
> I also get a few warnings on 32-bit Solaris about integer overflows.
> I'll check those out and see if they're important or not.
>
> Ray
Jerry> I maintain the Fedora package. We build on 32-bit systems (primarily
Jerry> x86, but there are groups working on Sparc, PPC, etc. ports). I don't
Jerry> use any of those platforms myself; I've been on 64-bit x86 for about 6
Jerry> years now. But I also haven't received notice of any build failures
Jerry> from the distribution builders, nor any bug reports from 32-bit users.
Jerry> The termcap.c failure is apparently due to speed_t not being defined.
Jerry> On my system, I get the appropriate typedef from <termios.h>.
Yes, that solves the problem for me on my Linux box. I just
#include'd termios.h in termcap.c.
Is this a configure issue, then?
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
11:08 p.m.
Raymond Toy wrote:
While trying to do a build on Solaris (sparc), [...]
What release of Solaris, and what XEmacs configuration options?
As a final test, I tried a 32-bit build on Linux using gcc 4.4.1.
The
64-bit build works fine. However, the 32-bit build fails miserably
with error messages like:
gcc -c -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wshadow
-Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes
-Wdeclaration-after-statement -Wunused-parameter -g -m32 -Demacs -I.
-I/net/gondor/src/xemacs/hg/xemacs-21.5/src -DHAVE_CONFIG_H
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:107: warning: function declaration
isn't a prototype
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:120: warning: function declaration
isn't a prototype
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:130: warning: function declaration
isn't a prototype
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:143: warning: function declaration
isn't a prototype
/net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:236: error: expected '=',
',', ';', 'asm' or '__attribute__' before 'ospeed'
I usually get errors like that when I've forgotten to install all the
necessary -dev packages. For example, on Ubuntu 10.10 I needed to
install
libncurses5-dev
libx11-dev
libxaw7-dev
libpng++-dev
(as well as texinfo).
Anyone doing 32-bit builds these days?
That's all I build. Haven't built recently on Solaris, though, mostly
due to my employer's policies around downloading FOSS.
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:25 a.m.
>>>> "Raymond" == Raymond Toy
<toy.raymond(a)gmail.com> writes:
Raymond> While trying to do a build on Solaris (sparc), I ran into this
Raymond> problem:
Raymond> Building finder database ...
Raymond> rm -f
/net/gondor/Volumes/share2/src/xemacs/hg/xemacs-21.5/src/../lisp/finder-inf.el
Raymond> ./xemacs -no-packages -batch -eval "(setq
finder-compile-keywords-quiet t)" \
Raymond> -eval "(setq lisp-directory
\"/net/gondor/Volumes/share2/src/xemacs/hg/xemacs-21.5/src/../lisp\")" \
Raymond> -l finder -f finder-compile-keywords
Raymond> Loading auto-autoloads.el... (file auto-autoloads.elc is out-of-date)
Raymond> Loading auto-autoloads.el... (file auto-autoloads.elc is out-of-date)
Raymond> xemacs exiting.
Raymond> Invalid argument: No buffer named, "*finder-scratch*"
I think this problem is very strange. A 32-bit build fails with this
strange error, but the same code using a 64-bit build works fine.
How can I debug this?
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
8:43 a.m.
Raymond Toy writes:
>>>>> "Raymond" == Raymond Toy
<toy.raymond(a)gmail.com> writes:
Raymond> Building finder database ...
Raymond> rm -f
/net/gondor/Volumes/share2/src/xemacs/hg/xemacs-21.5/src/../lisp/finder-inf.el
Raymond> ./xemacs -no-packages -batch -eval "(setq
finder-compile-keywords-quiet t)" \
Raymond> -eval "(setq lisp-directory
\"/net/gondor/Volumes/share2/src/xemacs/hg/xemacs-21.5/src/../lisp\")" \
Raymond> -l finder -f finder-compile-keywords
I think this problem is very strange. A 32-bit build fails with
this
strange error, but the same code using a 64-bit build works fine.
How can I debug this?
What I would try first is cd'ing to the $build/src directory, and
./xemacs -no-packages -eval "(setq finder-compile-keywords-quiet t)" \
-eval "(setq lisp-directory
\"/net/gondor/Volumes/share2/src/xemacs/hg/xemacs-21.5/src/../lisp\")"
Then in XEmacs run M-: (setq debug-on-error t) RET, M-x load-lib RET
finder RET, and finally M-x finder-compile-keywords RET.
which should give you a Lisp backtrace. Please post that.
Other things to try: run under the debugger and poke at anything
suspicious you see in the Lisp backtrace.
Also, build without optimization. You might also try flipping the
--with-union-type bit (ie, if you usually build with "no", try
"yes"). If either of those succeeds, it's quite possibly a compiler
issue.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4928
days inactive
4929
days old
7 comments
5 participants
participants (5)
-
Jerry James -
Mike Kupfer -
Raymond Toy -
Stephen J. Turnbull -
The XEmacs Package Smoketest