Opened 16 years ago
Closed 16 years ago
#895 closed Bugs (Fixed)
"...failed gcc-Link-action", mingw tools
| Reported by: | archimed7592 | Owned by: | nobody |
|---|---|---|---|
| Milestone: | Component: | build | |
| Version: | None | Severity: | |
| Keywords: | Cc: |
Description
boost-1.33.1
mingw-3.4.2
"g++" "-Wl,--enable-auto-image-base" "-Wl,--exclude-symbols,_bss_end__:_bss_start__:_data_end__:_data_start__" "-Wl,--out-implib,bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\boost_filesystem-mgw-d-1_33_1.lib" -g -shared -Wl,--allow-multiple-definition -mno-cygwin -o "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\boost_filesystem-mgw-d-1_33_1.dll" -L"" "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\exception.obj" "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\operations_posix_windows.obj" "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\path_posix_windows.obj" "bin\boost\libs\filesystem\build\boost_filesystem.dll\mingw\debug\convenience.obj"
...failed gcc-Link-action
-L"" cause to loss one object file instead of add "empty path" to lib-lookups table.
caused by these lines from mingw-tools.jam
# So that RUNPATH, and PATH, is set to include where the mingw DLLs are located.
flags mingw STDLIBPATH : $(GCC_BIN_DIRECTORY) ;
workaround is to pass "-sMINGW_ROOT_DIRECTORY=/mingw" to bjam invocation (i'm using msys), but documentation says
MINGW_ROOT_DIRECTORY Path to installation of MinGW. (none) If not set tools must be available in the executable path
so it isn't obligatory to pass that argument.
Note:
See TracTickets
for help on using tickets.
