Re: [PATCH] Add build time guard to detect off_t mismatch

On Tue, May 12, 2026 at 4:26 PM Florian Bezdeka
<[email protected]> wrote:
> __RT() might be the problem here. You will end up in __cobalt_mmap()
> unconditionally, right? Does migrating to mmap() with all the wrapping
> magic help here?

When not using __RT(), the unresolved symbol is  __wrap_mmap64().

> Probably the same question as we had for the time_t related services: Do
> we want one libcobalt build to support both worlds at the same time?

At least the application on my desk uses __RT() a lot.
Sorting all this out would make some pople rather unhappy, I guess.

-- 
Thanks,
//richard