Opened 13 years ago
Closed 13 years ago
#3373 closed Bugs (fixed)
Boost.Build doesn't run ranlib when creating static libs
| Reported by: | loonycyborg | Owned by: | Vladimir Prus |
|---|---|---|---|
| Milestone: | Boost 1.42.0 | Component: | build |
| Version: | Boost 1.39.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
Although that supposed to only be required to speed up linking, mingw linker(at least the cross-compile one) barfs without it: $ LANG=C mingw32-g++ test.cpp -L. -llibboost_regex ./libboost_regex.lib: could not read symbols: Archive has no index; run ranlib to add one collect2: ld returned 1 exit status
Change History (5)
comment:1 by , 13 years ago
| Milestone: | Boost 1.40.0 → Boost 1.42.0 |
|---|
comment:2 by , 13 years ago
For the record, the best way to detect which ranlib to use is to run "gcc -print-prog-name=ranlib".
comment:4 by , 13 years ago
For posterity -- print-prog-name is sufficiently smart and will restore to system-wide 'ranlib' is it cannot find ranlib alongside a cross-compiler. The change was tested with arm-eabi cross compiler.
Note:
See TracTickets
for help on using tickets.
Will be fixed together with other mingw cleanups.