undefined reference to 'wrapper_dnrm2_' 'wrapper_dasum_' #477
Comments
|
Hi, can you please provide a more complete build log? The CMake output would be very helpful, too. Also, how do you have Armadillo configured? (i.e. is |
|
Hi, but allexec2man.sh exists. On 11/20/2015 09:55 PM, Ryan Curtin wrote:
*/Cordially,/ |
|
Hi there, Can you provide more information about what you are doing (i.e. what commands you are using)? Try removing your mlpack sources entirely and starting over. If |
|
Hi, On 2015/11/23 21:29, Ryan Curtin wrote:
*/Cordially,/ |
|
So, if you restart with a clean environment, i.e. remove your mlpack directory, git clone again, then reconfigure and build, does |
|
I just recompiling armadillo again, now there is no On 2015/11/23 22:03, Ryan Curtin wrote:
*/Cordially,/ |
|
So there is no problem and I can close this issue? Or is there something to investigate? |
|
There's no problem in this issue. So how to solve On 2015/11/23 22:13, Ryan Curtin wrote:
*/Cordially,/ |
|
Did you restart with a clean environment? |
|
I git clone mlpack again and still can't find allexec2man.sh On 2015/11/23 22:18, Ryan Curtin wrote:
*/Cordially,/ |
|
Does the file exist inside of your git repository? You're not providing very much information here, so it's hard for me to figure out what is going on. What would be preferable is this:
If you can get me all of that information, it'd be helpful for figuring out what is going on here; thanks. |
|
Attach: And I'm sure allexec2man.sh exists in the right place. On 2015/11/23 22:48, Ryan Curtin wrote:
*/Cordially,/ -- The C compiler identification is GNU 4.9.2 The target name "test" is reserved or not valid for certain CMake features, -- Found Doxygen: /usr/bin/doxygen (found version "1.8.8") This is the CMakeCache file.For build in directory: /home/asuka/Documents/mlpack/buildIt was generated by CMake: /usr/bin/cmakeYou can edit this file to change values found and used by cmake.If you do not want to change any of the values, simply exit the editor.If you do want to change a value, simply edit, save, and exit the editor.The syntax for the file is as follows:KEY:TYPE=VALUEKEY is the name of a variable in the cache.TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.VALUE is the current value for the KEY.######################## EXTERNAL cache entries######################## //Path to a file. //Path to a library. //Compile with extra Armadillo debugging symbols. //Header //Path to a file. //Library providing backtrace(3), //The directory containing a CMake configuration file for Boost. //Path to a file. //Boost library directory //Boost program_options library (debug) //Boost program_options library (release) //Boost serialization library (debug) //Boost serialization library (release) //Boost unit_test_framework library (debug) //Boost unit_test_framework library (release) //Path to a program. //Choose the type of build, options are: None(CMAKE_CXX_FLAGS or //Enable/Disable color output during build. //CXX compiler. //Flags used by the compiler during all build types. //Flags used by the compiler during debug builds. //Flags used by the compiler during release builds for minimum //Flags used by the compiler during release builds. //Flags used by the compiler during release builds with debug info. //C compiler. //Flags used by the compiler during all build types. //Flags used by the compiler during debug builds. //Flags used by the compiler during release builds for minimum //Flags used by the compiler during release builds. //Flags used by the compiler during release builds with debug info. //Flags used by the linker. //Flags used by the linker during debug builds. //Flags used by the linker during release minsize builds. //Flags used by the linker during release builds. //Flags used by the linker during Release with Debug Info builds. //Enable/Disable output of compile commands during generation. //Install path prefix, prepended onto install directories. //Path to a program. //Path to a program. //Flags used by the linker during the creation of modules. //Flags used by the linker during debug builds. //Flags used by the linker during release minsize builds. //Flags used by the linker during release builds. //Flags used by the linker during Release with Debug Info builds. //Path to a program. //Path to a program. //Path to a program. //Value Computed by CMake //Path to a program. //Flags used by the linker during the creation of dll's. //Flags used by the linker during debug builds. //Flags used by the linker during release minsize builds. //Flags used by the linker during release builds. //Flags used by the linker during Release with Debug Info builds. //If set, runtime paths are not added when installing shared libraries, //If set, runtime paths are not added when using shared libraries. //Flags used by the linker during the creation of static libraries. //Flags used by the linker during debug builds. //Flags used by the linker during release minsize builds. //Flags used by the linker during release builds. //Flags used by the linker during Release with Debug Info builds. //Path to a program. //If true, cmake will use relative paths in makefiles and projects. //If this value is on, makefiles will be generated without the //Compile with debugging information //Graphviz Dot tool for using Doxygen //Doxygen documentation generation tool (http://www.doxygen.org) //git command line client //Compile MATLAB bindings if MATLAB is found. //C++ compiler flags for OpenMP parallization //C compiler flags for OpenMP parallization //Compile with profiling information //Run test cases with verbose output. //Path to a program. //Value Computed by CMake //Dependencies for the target //Value Computed by CMake ######################## INTERNAL cache entries######################## //ADVANCED property for variable: ARMADILLO_INCLUDE_DIR Scanning dependencies of target mlpack_arma_config |
|
I've spent a little while thinking about this. This one is a bit baffling... What happens if you type |
|
Attach my output of allexec2man.sh. On 2015/11/25 22:30, Ryan Curtin wrote:
*/Cordially,/ mkdir: cannot create directory ‘’: No such file or directory |
|
Huh, why is it trying to use Also, now that you have run |
|
Yes, after I run dos2unix allexec2man.sh, I also get the error? On 2015/11/25 23:06, Ryan Curtin wrote:
*/Cordially,/ |
|
I think the issue here is that |
|
Well, I really did not install nash and I don't know what nash is. On 2015/11/30 21:00, Ryan Curtin wrote:
*/Cordially,/ |
|
What you've told me is that In order to test that theory, though, I'd need you to find a way to install bash (or at the very least make sure In looking a little deeper here, I can't find any evidence anywhere that Debian even packages nash, and if it is this nash: http://linuxcommand.org/man_pages/nash8.html then that isn't a suitable replacement for bash at all and I have no idea how your system is even running. So, I don't know what could have possibly caused this issue on your system, but I'd be willing to bet that this is the problem. |
|
Closing for inactivity. (Feel free to reopen for more help/discussion.) |
Linking CXX executable ../../../../bin/adaboost
../../../../lib/libmlpack.so.1.0: undefined reference to 'wrapper_dnrm2_'
../../../../lib/libmlpack.so.1.0: undefined reference to 'wrapper_dasum_'
collect2: error: ld returned 1 exit status
and how to fix this?
The text was updated successfully, but these errors were encountered: