Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-28 Thread Sébastien Bernard
I've been looking through this problem. genisoimage is reporting a problem with . and .. aliased to the same '' name. logs of the problem: - genisoimage -r -J -o ./tmp/miniiso/mini.iso -G /boot/isofs.b -B ... ./tmp/miniiso/cd_tree I: -input-charset not specified, using utf-8 (dete

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-28 Thread Sébastien Bernard
Le 28/04/2014 12:09, Thomas Schmitt a écrit : Hi, I tried with the xorriso -as mkisofs command, with no luck. This command terminates with a SIGBUS no matter of the options I pass on the command line. Ouch. I have no Debian of arch "sparc" in reach. I may provide you access to a shell account

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-28 Thread Sébastien Bernard
Le 28/04/2014 13:20, Thomas Schmitt a écrit : [genisoimage] (gdb) x rpnt 0x1ea7f9:0x (gdb) x lpnt 0x1e9dc1:0x0100 (gdb) n 659if (strcmp(rpnt, lpnt) == 0) { Both values match the prescribed names for "." and ".." in ECMA-119 (aka ISO 9660), 6.8.2.2 Identification of

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-28 Thread Sébastien Bernard
Le 28/04/2014 14:15, Thomas Schmitt a écrit : Hi, Sébastien Bernard: result from strcmp('\','\0001' is 0) result from strcmp('\','\0001' is -1) Typicaly, an endianness error. But one in strcmp(), not in your code or the one of genisoimage. Y

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-28 Thread Sébastien Bernard
Le 28/04/2014 16:05, Patrick Baggett a écrit : strcmp() may well be implemented by word comparisons. But then it is the duty of the implementation to properly handle the ends of the strings even if those are not word aligned. Indeed, the correct fix is using strcmp. Meanwhil

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-28 Thread Sébastien Bernard
Le 28/04/2014 22:01, Thomas Schmitt a écrit : Hi, Sebastien's machine now has a xorriso-1.3.7 (the current development snapshot) with changed libburn/async.c. The callers of add_worker() now declare: union w_list_data o; rather than struct union_member o; The type of the f

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-28 Thread Sébastien Bernard
Le 28/04/2014 20:21, Patrick Baggett a écrit : Seb, Yes, I can reproduce this issue. { 1, 0 } { 1, 1 } returns 0, when it should return -1. Interestingly, if you use: { 1, 1, 1, 1, 0 } //i.e. 5 bytes { 1, 1, 1, 1, 1 } //i.e. 5 bytes as the strings, it returns -1. So it clearly has a probl

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-28 Thread Sébastien Bernard
Le 28/04/2014 22:25, Sébastien Bernard a écrit : Le 28/04/2014 22:01, Thomas Schmitt a écrit : Hi, Sebastien's machine now has a xorriso-1.3.7 (the current development snapshot) with changed libburn/async.c. The callers of add_worker() now declare: union w_list_data o; rather

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-29 Thread Sébastien Bernard
Le 29/04/2014 16:34, Kieron Gillespie a écrit : I am currently investigating this unusual behavior with strcmp, and I am unable to reproduce the problem using the test_strcmp example provided. It returns the correct output of, result from strcmp('\','\0001' is -1) This was built on Debian

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-29 Thread Sébastien Bernard
t 10:45 AM, Sébastien Bernard mailto:sbern...@nerim.net>> wrote: Le 29/04/2014 16:34, Kieron Gillespie a écrit : I am currently investigating this unusual behavior with strcmp, and I am unable to reproduce the problem using the test_strcmp example provided.

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

2014-04-29 Thread Sébastien Bernard
Le 30/04/2014 00:12, Kieron Gillespie a écrit : Do we currently have a master list of all the major bugs facing the Sparc Port right now? I don't think so. I haven't been able to get one. You can start one. Seb -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subjec