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: Duplicate symbols if there multiple source files have the same name #683
Comments
Yeah... This happens if you specify source files by absolute path. Do you? If you specify them by relative path, then sub-directories will be reflected in |
If a source file was specified by absolute path, then the corresponding object file was placed into OUT_DIR. This posed a problem if multiple files with the same base name were specified by absolute paths. Fixes rust-lang#683.
But just in case I've opened #684. You can test it by referring to cc as |
I compiled *.c files in ROS directory |
If a source file was specified by absolute path, then the corresponding object file was placed into OUT_DIR. This posed a problem if multiple files with the same base name were specified by absolute paths. Fixes rust-lang#683.
If a source file was specified by absolute path, then the corresponding object file was placed into OUT_DIR. This posed a problem if multiple files with the same base name were specified by absolute paths. Fixes rust-lang#683.
If a source file was specified by absolute path, then the corresponding object file was placed into OUT_DIR. This posed a problem if multiple files with the same base name were specified by absolute paths. Fixes rust-lang#683.
The
compile()
complains about duplicate symbols when there are multiple input files with the same name but in different directories. Thecc
names the object file by its source file and places them underOUT_DIR
. It causes one object file to replace the other file, and pack the last object file twice in the .a static library.This is an example of the occurrence. The
target/debug/build/xxx/output
log shows that twoempty__functions.c
files from different dirs are compiled intoempty_functions.o
in the same directory.The text was updated successfully, but these errors were encountered: