lua-users home
lua-l archive

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



yes. :)

Which is weird since if you're having problems with x86 it's not the endian issue, then.

You might want to check the code actually giving that error; Lua source is fairly simple to grasp, unlike many other open source projects I've seen. Perhaps it's due to having only 3 major developers, who are quite feature cautious.

-asko


Baker, Derek kirjoitti 7.2.2006 kello 15.41:

# uname -a
Linux imx21 2.4.20-celf3 #2 Fri Apr 29 21:43:58 UTC 2005 armv5EJl unknown

So I think the "l" at the end of "armv5EJl" indicates little endian. Is that correct?

Derek

Asko Kauppi wrote:

-bash-2.05b$ uname -a
Linux kepponen 2.4.22-xfs #1 Sun Jun 12 21:17:17 PDT 2005 armv5b unknown unknown GNU/Linux

The 'b' is for big endian (NSLU2)

"The x86 architecture is little endian. Many ARM processors support either mode, but usually are used in little endian mode."
http://www.handhelds.org/minihowto/porting-software.html

-aka


Baker, Derek kirjoitti 6.2.2006 kello 21.47:

At the moment, we're running on an eval board, and no one seems to know if it's little or big. Is there any way to tell using some Linux tool?

Thanks for you help.

Derek

Asko Kauppi wrote:
I could easily help you with this.

ARM can be placed into both big and little endian mode; do you know which one you have?

-asko


Stefan Schwarzbach kirjoitti 6.2.2006 kello 19.44:


Hi Derek,

I'm not sure, but could there be a problem with the byte order of values
bigger than 8bits? Little endian vs. Big endian.
I'm not a lua developer so this is more a notice than an answer

Greetings,
Stefan


Baker, Derek schrieb:

Hi,

Is it possible to run compiled Lua on an architecture other than that which it was compiled on? For instance, can I compile a lua script to bytecode on an x86 platform and run the bytecode on an ARM platform?

I'm trying that now on a very simple script, and get the error:

   lua: unknown number format in test.byt

when trying to run it. This happens when compiling on x86 and trying to run on ARM as well as compiling on ARM and trying to run on x86.
All running Linux, btw.

Thanks,
Derek