Chris Friedt

@whythefyouflying - it might be necessary to do some console switching as well the way it is done in [tests/drivers/console_switching](https://github.com/zephyrproject-rtos/zephyr/tree/main/tests/drivers/console_switching). For example, you could probably use just about everything in...

> > To clarify, what are the legitimate reasons we would want to allow `_POSIX_C_SOURCE` definitions to be used by "core" parts of Zephyr such as the kernel? > >...

> @cfriedt Unfortunately, for some reason the stdin is not connected with the emulated uart, not sure how to connect the two. I've uploaded my latest code, it's building but...

I would suggest the following 1. Mitigate the layering violations with `strnlen()`, `strtok_r()`, and `gmtime_r()` by prefixing the Zephyr implementations with a `k_`, adding them to `lib/os`, and declaring them...

I would suggest testing this out initially with regular files via the filesystem (so exclude `getc()` for now since that deals with `/dev/stdin`, which is of course a special file)

> @cfriedt > Please note: > > > 1. Mitigate the layering violations with strnlen( > > Those functions are not OS dependant, and are provided directly by the C...

I'm confused... It really does not seem like anything has been done to address the concerns raised by @keith-packard, myself, and @bjarki-trackunit . One concern was to limit checking `_POSIX_C_SOURCE`...

I think this one can be closed in favour of a separate pr

> Do you have a working version of Thrift module that builds with the 0.15.2 SDK? I tried to build it and it complained about `struct stat` being redefined: @dcpleung...

Still hitting this on `qemu_x86`. https://github.com/zephyrproject-rtos/gsoc-2022-thrift/pull/158 can be modified to not exclude `qemu_x86` to demonstrate the issue. I suspect it will be excluded in thrift until we get a new...