On Wed, Nov 23, 2016 at 03:40:22PM +, Jonathan Dowland wrote:
> But digging into this a little, it seems to be an argument order issue.
...and all of my ISOs now read fine without the RR warnings. I haven't
double-checked
the docs, if you state that the argument order of -read_fs / -indev is
On Fri, Nov 18, 2016 at 05:27:25PM +0100, Thomas Schmitt wrote:
> $ gdb xorriso/xorriso
> (gdb) b fs_image.c:3024
> (gdb) b rockridge_read.c:111
> (gdb) r -read_fs norock -indev /path/to/your.iso
Using the above and one of the UDF images that I am about to email you a URL to,
and the above
On Fri, Nov 18, 2016 at 05:27:25PM +0100, Thomas Schmitt wrote:
> If you got the GNU xorriso tarball, then it is not linked dynamically
> with installed libisofs.so but rather statically with its own copy of
> libisofs.
OK, yup that's what I did.
> In the build directory
>
> $ xorriso/xorriso
Hi,
i wrote:
> > Was that already with -read_fs "norock" ?
Jonathan Dowland wrote:
> Just retried: alas, no difference
> ...
> libisofs: SORRY : Damaged RR/SUSP information.
It should not even get near to that error message.
Grrr ...
> I'm wondering if my hand-built modern xorriso is l
4 matches
Mail list logo
