Thanks Samuel,
It's working now, with a few small tweaks. Both putting #define
_FILE_OFFSET_BITS 64 and switching the offset type in the read function
to loff_t caused the translator to output what appears to be the
contents of some memory instead of a string of '1's. But compiling with
-D_FILE_
Thank you. Yes, I misunderstood. All three methods work (independently) now.
Samuel Thibault writes:
> Hello,
>
> Andrew Eggenberger, le dim. 28 juil. 2019 04:21:21 -0500, a ecrit:
>> It's working now,
>
> Good :)
>
>> Both putting #define _FILE_OFFSET_BITS 64 and switching the offset
>> type i
Hello,
Andrew Eggenberger, le dim. 28 juil. 2019 04:21:21 -0500, a ecrit:
> It's working now,
Good :)
> Both putting #define _FILE_OFFSET_BITS 64 and switching the offset
> type in the read function to loff_t
? Only one of the two should be needed. Note that the #define needs to
be very first,
Samuel Thibault, le sam. 27 juil. 2019 11:09:56 +0200, a ecrit:
> The issue here is actually that the source code is missing
>
> #define _FILE_OFFSET_BITS 64
>
> at the very top of the file.
Or you can make the hooks use loff_t instead of off_t.
Samuel
Hello,
Andrew Eggenberger, le ven. 26 juil. 2019 20:36:20 -0500, a ecrit:
> I've been trying to compile and run the trivfs example [1] in the Hurd
> Hacking Guide. It compiles with the slightly amended command:
>
> gcc -g -o one -ltrivfs -lports
Indeed, it is using a libports function an
