ee24fabd83
infrastructure only uses them under Linux and OpenBSD (eww, hardcoded logic based on OS names). Aside making installations more consistent across systems, this lets Boost work correctly on the systems where sonames were previously used. Otherwise, they are unable to find the correct libraries at runtime and we get PLIST errors (more files installed than expected). The problem exposes itself when building software that needs Boost (e.g. monotone). This also means that we can't rename the installed libraries any more as we were doing until now, because programs linked against them will be looking for their respective sonames. Therefore, keep the default names produced by a --layout=system build. Bump PKGREVISION of boost, boost-libs and boost-python to 1. |
||
|---|---|---|
| .. | ||
| buildlink3.mk | ||
| DESCR | ||
| Makefile | ||
| PLIST | ||