aditya0yadav commented on PR #18331: URL: https://github.com/apache/nuttx/pull/18331#issuecomment-3856526829
> > > @simbit18 One more thing, what should we do with the linker in macOS? I know it will work perfectly with Linux but not with macOS. > > > Every time I have to disable the configuration toolchain related to Gcov. > > > Any suggestions? > > > > > > A long time ago, it was possible to build sim:nsh for Linux, macOS, and Windows . Currently, it does not work on macOS and Windows with MSYS2/Cygwin (the latest version I was able to build and test was [10.2](https://github.com/simbit18/nuttx-msys2)), so I personally think it is right to restore the build by modifying the defconfig file. > > Of course, this is just my opinion! :) > > I think is makes sense, maybe using git bisect it could be possible to identify which symbols cases the breaking and open an issue to track it. I just want to check if I’m understanding correctly: @simbit18 @acassis The linker issue seems to happen only on macOS, not on Linux. On Linux, it works fine and uses Gcov as expected, but on macOS, I always have to disable the Gcov-related toolchain in the configuration. If I wanted to find the specific symbol that is causing the linker to fail, doing a git bisect over 2–4 years of changes seems impractical because there’s been too much change in the repository. One idea I had is to use Docker with Linux to build NuttX, since Linux doesn’t hit the macOS linker problem. But of course, that wouldn’t reproduce the macOS-specific issue. Do you have any suggestions on how to approach this efficiently for macOS? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
