Re: Possible byte-order problems in TeX format files with -rc1

nix  writes:

> This is TeXk, Version 3.14159 (Web2C 7.4.0)

> This is TeXk, Version 3.14159 (Web2C 7.4.4)

These tex binaries come from different web2c versions.  There's no
guarantee that you can exchange formats between them.

I've done some tests with: linux (i386, little-endian), IRIX (MIPS 32
bit, big-endian), and IRIX (MIPS 64 bit, big-endian), and can exchange
the formats.  The formats differ in more than a few bytes, but they
are mutually interchangable.

What's tripping you up is probably the first part of this change, as
it changed the size of one datatype from 2 bytes to 4.

$ cvs diff -u -rtexk-7_4_0 -rtexk-7_4_4 tex.ch
Index: tex.ch
===================================================================
RCS file: /usr/local/cvsroot/texk/texk/web2c/tex.ch,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- tex.ch      11 Nov 2002 09:54:11 -0000      1.51
+++ tex.ch      14 Jan 2003 10:43:32 -0000      1.52
@@ -197,8 +197,8 @@
 @y
 @d file_name_size == maxint
 @d ssup_error_line = 255
-@d ssup_max_strings ==65535
-{Larger values may be used, but then the arrays consume much more memory.}
+@d ssup_max_strings == 262143
+{Larger values than 65536 cause the arrays consume much more memory.}
 @d ssup_trie_opcode == 65535
 @d ssup_trie_size == 262143

@@ -229,7 +229,7 @@
   {string of length |file_name_size|; tells where the string pool appears}
 @#
 @!inf_main_memory = 2999;
-@!sup_main_memory = 8000000;
+@!sup_main_memory = 32000000;

 @!inf_trie_size = 8000;
 @!sup_trie_size = ssup_trie_size;
@@ -267,7 +267,7 @@
 @!inf_font_max = 50; {could be smaller, but why?}

 @!inf_pool_size = 32000;
-@!sup_pool_size = 10000000;
+@!sup_pool_size = 40000000;
 @!inf_pool_free = 1000;
 @!sup_pool_free = sup_pool_size;
 @!inf_string_vacancies = 8000;


-- 
Olaf Weber

               (This space left blank for technical reasons.)