-
Notifications
You must be signed in to change notification settings - Fork 90
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
Error linking libframework.a #24
Comments
I will give a shot on this one. It seems it cannot find your linker binary. Is your path set correctly? Can you execute make with verbose? Maarten -- my phone has a tiny keyboard so I kept this message short On Dec 20, 2015 10:10 PM, Drasko DRASKOVIC notifications@github.com wrote: I am trying to compile the project, but I am hitting the linking error: drasko@Mali: — |
Here is a verbose output:
|
Hmm... I am looking at
It looks like cross-tool auto-detection did not work for me. |
You can specify your linker path in cmake to solve CMAKE_AR-NOTFOUND cr libframework.a CMakeFiles/framework.dir/framework_bootstrap.c.obj hal/platforms/ -- my phone has a tiny keyboard so I kept this message short On Dec 21, 2015 12:20 AM, Drasko DRASKOVIC notifications@github.com wrote: Hmm... I am looking at build/CMakeFiles/2.8.12.2/CMakeCCompiler.cmake, there are parts like: set(CMAKE_C_COMPILER "arm-none-eabi-gcc") set(CMAKE_AR "CMAKE_AR-NOTFOUND") It looks like cross-tool auto-detection did not work for me. — |
You can specify the path to ar however i assume you would have to do this for ld etc as well. I Can you make sure the mentioned path is correct please? Did you install /usr/bin/arm-none- On Monday, December 21, 2015 07:28:25 AM Weyn Maarten wrote: You can specify your linker path in cmake to solve CMAKE_AR-NOTFOUND cr libframework.a Hmm... I am looking at build/CMakeFiles/2.8.12.2/CMakeCCompiler.cmake, there are parts like: set(CMAKE_AR "CMAKE_AR-NOTFOUND") It looks like cross-tool auto-detection did not work for me. [1] https://github.com/MOSAIC-LoPoW/dash7-ap-open-source-stack/issues/ |
Hi Drasko, Any progression on this matter? Maarten From: Glenn Ergeerts [mailto:glenn.ergeerts@uantwerpen.be] You can specify the path to ar however i assume you would have to do this for ld etc as well. I should not be necessary and i would suggest to first look into why it cmake is not able to detect your toolchain.. Your cmake output shows it uses /usr/bin/arm-none-eabi-gcc instead of the version in ~/dash7-ap-open-source-stack/gcc-arm-none-eabi-4_9-2015q3/ as you specified in your cmake arguments. Can you make sure the mentioned path is correct please? Did you install /usr/bin/arm-none-eabi-gcc from a repository package? On Monday, December 21, 2015 07:28:25 AM Weyn Maarten wrote: You can specify your linker path in cmake to solve CMAKE_AR-NOTFOUND cr libframework.a CMakeFiles/framework.dir/framework_bootstrap.c.obj hal/platforms/ -- my phone has a tiny keyboard so I kept this message short On Dec 21, 2015 12:20 AM, Drasko DRASKOVIC <notifications@github.commailto:notifications@github.com> wrote: Hmm... I am looking at build/CMakeFiles/2.8.12.2/CMakeCCompiler.cmake, there are parts like: set(CMAKE_C_COMPILER "arm-none-eabi-gcc") set(CMAKE_C_COMPILER_ARG1 "") set(CMAKE_C_COMPILER_ID "GNU") set(CMAKE_C_COMPILER_VERSION "") set(CMAKE_C_PLATFORM_ID "") set(CMAKE_AR "CMAKE_AR-NOTFOUND") set(CMAKE_RANLIB ":") set(CMAKE_LINKER "CMAKE_LINKER-NOTFOUND") It looks like cross-tool auto-detection did not work for me. — You received this message because you are subscribed to the Google Groups "dash7-ap-oss" group. |
Yeap, it was a Cmake version that needed upgrade on my old Debian. This is what I use now:
and it compiles latest master nicely. We can close this one. |
On Tuesday, January 5, 2016 at 8:03:33 AM UTC+1, Maarten Weyn wrote:
Yes, issue closed: BR, |
I am trying to compile the project, but I am hitting the linking error:
The text was updated successfully, but these errors were encountered: