[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: drag-and-drop failures

From: Jan D.
Subject: Re: drag-and-drop failures
Date: Wed, 31 Mar 2004 23:05:06 +0200

No, little-endian (`all the world's a VAX').  It's the only OS I have
with a 64-bit userland, though I can also build a 64-bit Emacs on Irix
and Solaris/SPARC.

but what do you run Debian on?


Okay, thanks for the info.  I still suspect some kind of endian problem.
I'll have a big endian machine here shortly and then I'll try it again.

Finally, if you can evaluate the lisp function byteorder (no
arguments) and see what you get on the various machines, it would
help.  Most important is any 64-bit machines.

Well, the SPARC is a 64-bit machine, but it's a 32-bit userland.  It
didn't occur to me that this sort of thing wouldn't work between
different architectures :-/.  I can tell you characteristics of the
systems I have directly.

Actually, the definition of Fbyteorder doesn't look strictly right,
though I think it will work on all the Emacs platforms I know about;
it looks as though it assumes unsigned is 32-bit.  Also, it seems
wrong to have a function separate from the WORDS_BIG_ENDIAN macro.  I
think the endian test should be delegated to autoconf (which uses, if
necessary, a different runtime endian test).  See my comment in
configure.in, though I guess rms doesn't agree.

I have checked in a change in Fbyteorder so it behaves on 64 bit also.
The reason for a runtime check was that is the same type of check that
X11 uses, and I didn't know about WORDS_BIG_ENDIAN...  Wasn't there
a processor that could be both little and big endian?

        Jan D.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]