tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkgsrc frozen for 2017Q2



On 07/07/17 15:49, Jason Bacon wrote:
On 07/07/17 02:27, Jonathan Perkin wrote:
* On 2017年07月07日 at 02:51 BST, Jason Bacon wrote:
All sounds good, with one correction:
pkgsrc *does* set -std=c++11 for packages with USE_LANGUAGES=c++ if a
dependent package contains USE_LANGUAGES=c++11.
This inheritance of compiler flags by dependencies is the behavior I was
questioning.
Not always, only if we add it to the buildlink3.mk file. The reason
for doing this is that some packages are now installing headers which
use C++11 features, and so packages which use them as a dependency
also require -std=c++11 otherwise they fail to build.
This makes perfect sense, but it's going the opposite direction of what we're talking about. Someone else had originally posted about the problem of fonts/harfbuzz inheriting -std=c++11 from x11/qt5-base, i.e. build qt5-base, it tries to install harfbuzz as a dependency with -std=c++11. However, I just discovered that this issue is actually isolated to the hardbuzz pkg itself. It fails with an unrecognized -std=c++11 on CentOS 6 even when being built directly, not just when being built as a dependency of qt5-base. I'm retracing my previous path (building octave) to see if any other packages that failed similarly actually inherited the flag from a dependent port. This may have been a false alarm.
False alarm. The following dependencies failed while building math/octave on CentOS 6, but they were independent issues. They all simply need a newer GCC than 4.4.
fonts/harfbuzz
print/poppler
print/luatex
print/web2c
--
Earth is a beta site.


Home | Main Index | Thread Index | Old Index

AltStyle によって変換されたページ (->オリジナル) /