The configure test sets PIKE_BYTEORDER to 0 because (obviously) it can't test that when cross compiling. It seems like having a byteorder of "0" ought to be a failure, and possibly a way to define it manually, since there doesn't appear to be a consistent convention (ie, if not explicitly big-endian, assume it's little-endian)

Thoughts?

Bill

January 28, 2018 5:46 PM, "H. William Welliver III" william@welliver.org wrote:

Yes, I thought it was a little strange. On a side note, I was able to get pike 7.8 to run, so it seems like something specific to 8.0.

...

On Jan 28, 2018, at 1:47 PM, Henrik Grubbström (Lysator) @ Pike (-) developers forum 10353@lyskom.lysator.liu.se wrote:

...

I cross compiled pike 8.0.498 on an amd64/linux system for use on an armv5tejl/linux system, and I m getting a strange error when starting it up:

-:1: Type mismatch for callback function `[]=: -:1: Expected: scope(0,function(zero, (0=zero) : 0)). -:1: Got : function(int(128..-129), int(128..-129) : int(0..-16777216)).

^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^ These two types look suspect.

...

-:1: Program constant "Buffer" is NULL. program.c:6011: Fatal error: Failed to initialize class '_Stdio' No stack - no backtrace. Aborted