I have no idea what Yesod is, but I know exactly what each of your other errors means. First, you should not try to link statically. The warning you get is exactly right: if you link statically, and use one of the routines for which you are getting the warning, then you must arrange to … Read more
You can specify the full path to the static libs without the -l flag to link with those. gcc … source.c … /usr/lib32/libmysuperlib.a …
The link commandline argument -static-libgcc should work. Another variant you could try is plain -static. If you don’t want to worry about this, and still want to redistribute your binary, just copy the relevant dll from MinGW’s bin directory and place it alongside your executable. This is common practice and works as advertised.
Reading the manual page (for ar) is a good start: c Create the archive. The specified archive is always created if it did not exist, when you request an update. But a warning is issued unless you specify in advance that you expect to create it, by using this modifier. r Insert the files member… … Read more
I’ve managed to solve my problem by using the following: #Dynamic/Shared Libs … #Static start set_target_properties(icarus PROPERTIES LINK_SEARCH_START_STATIC 1) set_target_properties(icarus PROPERTIES LINK_SEARCH_END_STATIC 1) set(CMAKE_FIND_LIBRARY_SUFFIXES “.a”) #Static Libs … #Set Linker flags set(CMAKE_EXE_LINKER_FLAGS “-static-libgcc -static-libstdc++”) This works without passing a -static which creates other big issues, and can essentially mix static and dynamic libraries. As long … Read more
Please, have a look at ld and WIN32 (cygwin/mingw). Especially, the direct linking to a dll section for more information on the behavior of -l flag on Windows ports of LD. Extract: For instance, when ld is called with the argument -lxxx it will attempt to find, in the first directory of its search path, … Read more
Static linking produces a larger executable file than dynamic linking because it has to compile all of the library code directly into the executable. The benefit is a reduction in overhead from no longer having to call functions from a library, and anywhere from somewhat to noticeably faster load times. A dynamically linked executable will … Read more
For release libraries, it’s unlikely that you could determine the version. For debug libraries, you can use dumpbin: dumpbin /rawdata:1 library.lib The assembly manifest should be at the beginning of the dump and will contain the version of the CRT the library requires along with the full path to the compiler used to build the … Read more
glibc uses libnss to support a number of different providers for address resolution services. Unfortunately, you cannot statically link libnss, as exactly what providers it loads depends on the local system’s configuration.
With the development branch of GHC (anyone know exactly which version this was added in?): $ ghc -o hello hello.hs $ strip -p –strip-unneeded –remove-section=.comment -o hello-small hello $ du hello hello-small 700 hello 476 hello-small Add the -dynamic flag for a dynamically linked RTS: $ ghc -dynamic -o hello hello.hs $ strip -p –strip-unneeded … Read more