FS#4632 - boost libraries have unwanted -gcc suffix

Attached to Project: Arch Linux
Opened by Thom Johansen (preglow) - Saturday, 13 May 2006, 22:21 GMT
Last edited by arjan timmerman (blaasvis) - Thursday, 25 May 2006, 15:47 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Kevin Piche (kpiche)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

All of the libboost libraries are suffixed with -gcc. Example: libboost_filesystem.a is libboost_filesystem-gcc.a in arch. I believe no packages that actually use boost libraries will expect to see this suffix, which will give autoconf or makefile errors.
This task depends upon

Closed by  Kevin Piche (kpiche)
Tuesday, 30 May 2006, 02:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  No '-gcc' suffixes on libraries in boost 1.33.1-5
Comment by Thom Johansen (preglow) - Sunday, 14 May 2006, 17:01 GMT
I've had a look around, and both Debian and Ubuntu keep the -gcc and other information in the filenames, but not in the main symlink 'libboost_filesystem.so'. None of them have 'libboost_filesystem-gcc.so'. This behaviour is perfectly fine with me. As for packages that don't build I really don't know of any but my own, which compile nice on all other systems I've tried using '-lboost_filesystem' as a linker flag. '-lboost_filesystem-gcc' does not work any of the systems I have access to apart from Arch.
It looks like config/auto_link.hpp might yield the functionality you describe, but needing to use a header file to decide on linker time options sounds a bit strange to me.
Comment by Kevin Piche (kpiche) - Tuesday, 30 May 2006, 02:31 GMT
Built boost with the --layout=system option. No '-gcc' suffixes.

Loading...