Hello,
Thank you Petro for the help! I've taken a look over the past couple days,
tried a few different variations, and I'm still very confused by what's
going on. You're correct that the program seems to get stuck when I print a
string which is *not* marked as `static` in `arm64_earlyprintinit`
(
Could you tell us a bit about what problem you're trying to solve by using
the host system's glibc? As Greg explained, that isn't really feasible, but
perhaps if we understand what you're trying to accomplish, someone might be
able to suggest a different approach...
Cheers
Nathan
On Fri, Aug 2, 2
Hi,
Thank you so much for the valuable insights Gregory and Alan. I kind of
understood the pitfalls but nevertheless wanted to confirm.
Regards,
Ritvik
On Fri, Aug 2, 2024 at 3:49 PM Gregory Nutt wrote:
> On 8/2/2024 12:06 PM, Ritvik Tanksalkar wrote:
> > Hello,
> >
> > I'm working on a proj
On 8/2/2024 12:06 PM, Ritvik Tanksalkar wrote:
Hello,
I'm working on a project where I need to compile the NuttX kernel to use
the system's standard library (stdlib) instead of its custom
implementation. My goal is to have NuttX use the host system's stdlib
functions rather than the ones provide
Hi Ritvik,
I think currently we don't have a "drop-in" replacement for NuttX libc with
external libc like musl and others, but it is something easy to do with
existing configuration:
Look at libs/libc/machine/Kconfig after line 47 you can define that your
ARCH has its own libc function.
In fact
Hello,
I'm working on a project where I need to compile the NuttX kernel to use
the system's standard library (stdlib) instead of its custom
implementation. My goal is to have NuttX use the host system's stdlib
functions rather than the ones provided with the kernel.
Currently, I'm compiling the
