On Sun, Jun 02, 2024 at 07:03:05PM +0530, Nilesh Patra wrote: > > That's not entirely true. The test uses the 'cio_ra.bin' from the build > > directory (not the one that is optionally installed by 'dh_install'). > > > > However, you are correct, that the cio_ra.bin file is a platform-specific > > (actually endian-specific) binary data file, and hence is normally produced > > by executing 'cio_file' on the target platform -- which of course is not > > possible when cross-compiling. I cannot think of an easy way to produce the > > correct cio_ra.bin file when cross-compiling. Is that a show-stopper? > > Unfortunately, yes. Just had an idea. If it is just an endian-ness issue, we could cross-compile when the archs are of same endian-ness. Something like: if endianness of the build arch[1] is same as that of host arch[2]: - compile cio_file with native compiler - generate cio_ra.bin with running the cio_file binary - install cio_ra.bin and move on else: - fail to cross-build - return an exit code and proceed to not build Does not solve the problem entirely but atleast partially. WDYT? [1]: architecture you are building on [2]: architecture you are building for Best, Nilesh
Attachment:
signature.asc
Description: PGP signature