-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Linker multiple definition issue with FATFS and VFS (IDFGH-13239) #14174
Comments
I think the key point here is not the usage of fatfs component, but the usage of std::filesystem. I also got the same issue with the latest toolchain when trying std::filesystem. We didn't have any test cases which used std::filesystem, so we didn't notice this issue when doing the last toolchain upgrade. We'll try to fix this soon. In the meantime, please try this patch which can help you temporarily bypass this issue: #13736 (comment) |
Thank you ! The patch works. What's the timeframe for having a fix on the release branch ? I just need a ballpark figure. |
Any update ? |
@igrr Sorry to bother. Do you have an ETA when commit 684d3e6 will be merged into the The Rust For us - btw - the problem only manifests itself with the "duplicate symbol" errors and we don't have missing symbols during linkage: getcwd
chdir
But I think anyway the "duplicate symbol" error is a side effect of at least one missing symbol, because otherwise |
Answers checklist.
IDF version.
v5.3-rc1
Operating System used.
Linux
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
What is the expected behavior?
Calling opendir, closedir, mkdir works in v5.2.2. I use std::filesystem to call std::filesystem::exists, std::filesystem::remove and std::filesystem::file_size with no issues.
What is the actual behavior?
With v5.3 you get a multiple definition error at link time with newlib's implementations of opendir, closedir, mkdir and so on.
Steps to reproduce.
...
Build or installation Logs.
More Information.
No response
The text was updated successfully, but these errors were encountered: