"Symbol errors" build failure(s)
clang 3.2
With some old libtool version (1.5.6 and older), pic_flag will be set to only
-DPIC. The missing option -fPIC (Position independent code) will make the link fail.
libtoolize or passing
-fPIC to the flags will fix the issue.
| Package | Version | Supposed error message | Full log |
Bug report |
|---|
| cdo | 1.5.9+dfsg.1-4 | crtbeginT.o: could not read symbols: Bad value
| Log |
|
| gnumeric | 1.12.0-1 | libgsf-1.so.114: could not read symbols: Invalid operation
| Log |
|
| harminv | 1.3.1-8 | .libs/harminv.o: could not read symbols: Bad value
| Log |
|
| jade | 1.2.1-47.1 | .libs/Allocator.o: could not read symbols: Bad value
| Log |
|
| ldiskfsprogs | 1.41.90.wc4+dfsg-1 | error_message.o: could not read symbols: Bad value
| Log |
|
| libgdal-grass | 1.9.0-1 | grass57dataset.o: could not read symbols: Bad value
| Log |
|
| ltt-control | 2.1.0~rc9-1 | liblttng-ust-ctl.a: could not read symbols: Bad value
| Log |
|
| nvidia-texture-tools | 2.0.8-1+dfsg-3 | squish/libsquish.a: could not read symbols: Bad value
| Log |
|
| openjade | 1.4devel1-20.1 | .libs/Node.o: could not read symbols: Bad value
| Log |
|
| slurm-llnl | 2.3.4-2 | Slurm.o: could not read symbols: Bad value
| Log |
|
| wmaker | 0.95.3-2 | .libs/raster.o: could not read symbols: Bad value
| Log |
|
11 errors
