-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Python interperter distclean isn't working #2895
Comments
Hi @PetervdPerk-NXP , were you able to build it properly in the last run? I remember seeing something similar when I was developing and the sources were not being properly tracked. Can you try cleaning the nuttx and the nuttx-apps repository with |
I tried and it worked as expected on our docker image:
The build logs show the folder
Can you provide more details about your environment? |
Compile failure I'll try
So yeah most likely Also which compiler are you using? Because I think my failure has to do with my gcc version. |
I see... Yeah, would need to investigate why it fails to clean the files if the build fails too... About the toolchain, we always recommend using the same CI uses: https://nuttx.apache.org/docs/latest/platforms/risc-v/qemu-rv/boards/rv-virt/index.html#risc-v-toolchain |
Any idea where the CI downloads the 64 bit of the riscv toolchain I only see this?
But when building it wants the 64 bit version
|
You need to export it to your PATH env var, just like it's done on CI: So, basically, it doesn't matter where you download it, as long as you export it to your
|
Okay got it now turns out it fails on GCC 10.2, but GCC 13.2 works fine.
|
Description / Steps to reproduce the issue
Try to compile python interpreter using
Run
make distclean or
make apps_distclean`Python compile objects are still there.
Dry run doesn't show removal of the files
On which OS does this issue occur?
[OS: Linux]
What is the version of your OS?
Ubuntu 22.04
NuttX Version
master
Issue Architecture
[Arch: risc-v]
Issue Area
[Area: Interpreters]
Verification
The text was updated successfully, but these errors were encountered: