Problems: Difference between revisions

153 bytes added ,  10 March 2022
→‎64bit binary on a 32bit operating system: remove section about 32bit, and create new "frame numbers beyond 999999"
(→‎64bit binary on a 32bit operating system: remove section about 32bit, and create new "frame numbers beyond 999999")
Line 58: Line 58:
     tcsh: setenv KMP_INIT_AT_FORK FALSE
     tcsh: setenv KMP_INIT_AT_FORK FALSE


=== 64bit binary on a 32bit operating system ===
=== frame numbers beyond 999999 ===


If the error message is e.g.
If the number of question marks "?" in NAME_TEMPLATE_OF_DATA_FRAMES is larger than 6, to allow for e.g.
  xds: Exec format error. Wrong Architecture.
  DATA_RANGE= 1000001 10001000
or
then IDXREF cannot properly read SPOT.XDS written by COLSPOT, and stops with
-bash: /usr/local/bin/xds: cannot execute binary file
  !!! ERROR !!! CANNOT READ SPOT.XDS
you try to run the 64bit version on a 32bit operating system; this won't work. Since October 2015, you need a 64bit Linux operating system to run XDS because the 32bit version is no longer provided.
This happens when the filenames of the frames have digits before the actual number, as in myframe1000001.cbf .
The workaround is to specify e.g.  
NAME_TEMPLATE_OF_DATA_FRAMES=myframe100????.cbf
DATA_RANGE=1 1000


(Problem reported by Pedro Dinis)


=== ASSERT VIOLATION ===
=== ASSERT VIOLATION ===
2,684

edits