stack protector mode differs in PCH file vs. current file:
bob prohaska
fbsd at www.zefox.net
Sat Apr 27 23:56:00 UTC 2019
On Sat, Apr 27, 2019 at 03:26:14PM +0200, Jan Beich wrote:
> bob prohaska <fbsd at www.zefox.net> writes:
>
> > In trying (still) to compile www/chromium on an RPI3 running -current with
> > ports at 500082 and system at 346613 portmater is stopping in (I think)
> > openjdk8 with
> > errorerrorerror: : errorstack protector mode differs in PCH file vs. current file: :
> > stack protector mode differs in PCH file vs. current filestack protector mode differs in PCH file vs. current file
> > stack protector mode differs in PCH file vs. current file
>
> Can't say much without full build log but it maybe a regression from
> https://svnweb.freebsd.org/changeset/ports/499897
>
> Maybe precompiled.hpp.pch is generated with different arguments compared
> to when it's included in source files. Try the following workaround:
>
> --- java/openjdk8/Makefile.orig
> +++ java/openjdk8/Makefile
> @@ -203,14 +203,14 @@ CONFIGURE_ENV+= LIBCXX="-lc++"
> .endif
> .endif
>
> -# GCC is broken with PCH: https://lists.freebsd.org/pipermail/svn-src-all/2015-March/101722.html
> .if ${COMPILER_TYPE} == gcc
> CONFIGURE_ARGS+= --with-toolchain-type=gcc
> -.if ${ARCH} == "powerpc64"
> -MAKE_ARGS+= USE_PRECOMPILED_HEADER=1
> -.else
> -MAKE_ARGS+= USE_PRECOMPILED_HEADER=0
> .endif
> +
> +# GCC is broken with PCH: https://lists.freebsd.org/pipermail/svn-src-all/2015-March/101722.html
> +# PCH is poorly tested outside of x86
> +.if ${ARCH} != "amd64" || ${COMPILER_TYPE} == gcc
> +MAKE_ARGS+= USE_PRECOMPILED_HEADER=0
> .endif
>
> .if empty(ICONV_LIB)
I'm doing something wrong, patch replies
patch: **** malformed patch at line 22: .if empty(ICONV_LIB)
and exits without doing anything. Come to think of it, shouldn't
.if [anything]
be followed by
.endif
eventually?
Thanks for your help!
bob prohaska
More information about the freebsd-ports
mailing list