Re: security/polkit not working with evbarm-current

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Sat, Jun 25, 2016 at 07:30:52PM -0700, Michael Plass wrote:
> 
> On Jun 25, 2016, at 3:50 PM, Michael Plass wrote:
> 
> > On Jun 25, 2016, at 11:55 AM, Thomas Klausner wrote:
> > 
> >> On Wed, Jun 22, 2016 at 07:15:59PM -0700, Michael Plass wrote:
> >>> On Jun 14, 2016, at 12:13 AM, John Klos wrote:
> >>> 
> >>>> /usr/local/bin/xsltproc -nonet --stringparam man.base.url.for.relative.links /usr/local/share/gtk-doc/html/polkit-1/ --xincludehttp://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl pkcheck.xml
> >>>> /usr/local/lib/libgcrypt.so.20: text relocations/usr/local/lib/libgcrypt.so.20: text relocations
> >>>> 
> >>>> /usr/local/lib/libgcrypt.so.20: Cannot write-enable text segment: Permission denied/usr/local/lib/libgcrypt.so.20: Cannot write-enable text segment: Permission denied
> >>>> 
> >>>> /usr/local/lib/libgcrypt.so.20: text relocations/usr/local/lib/libgcrypt.so.20: text relocations
> >>>> 
> >>>> /usr/local/lib/libgcrypt.so.20: Cannot write-enable text segment: Permission denied/usr/local/lib/libgcrypt.so.20: Cannot write-enable text segment: Permission denied
> >>>> 
> >>>> gmake[3]: *** [Makefile:647: polkitd.8] Error 1
> >>> 
> >>> I ran into a similar problem today, building devel/git-contrib.
> >>> A workaround is
> >>> 
> >>> # paxctl +m /usr/pkg/bin/xsltproc
> >>> 
> >>> (see http://mail-index.netbsd.org/current-users/2016/05/20/msg029398.html)
> >> 
> >> That's strange. This paxctl is not necessary for me on 7.99.32/amd64,
> >> and I don't think there should be differences between the
> >> architectures in this regard. (My cc1 also does not need +m.)
> >> 
> >> Can you update to 7.99.32 and check if it's still needed?
> >> Thomas
> >> 
> >> 
> > 
> > 
> > Will do - I happen to have a build underway.
> > 
> > But I think it may be in libgcrypt, which has a fair bit of assembly code
> > for various architectures, including armv7-neon. All of the programs in 
> > /usr/pkgsrc/security/libgcrypt/work/libgcrypt-1.7.1/tests get the same message:
> > 
> > $ /usr/pkgsrc/security/libgcrypt/work/libgcrypt-1.7.1/tests/version
> > /usr/pkg/lib/libgcrypt.so.20: text relocations
> > /usr/pkg/lib/libgcrypt.so.20: Cannot write-enable text segment: Permission denied
> > 
> > - Michael
> > 
> > NetBSD mipi 7.99.30 NetBSD 7.99.30 (RPI2) #3: Sun Jun 19 20:55:51 PDT 2016  michael@mipi:/usr/obj/sys/arch/evbarm/compile/RPI2 evbarm
> > 
> 
> Indeed, configuring libgcrypt with --disable-neon-support seems to avoid the problem.

I don't speak ARM ASM; do you want to fix it or should we use
--disable-neon-support for now to work around it?
 Thomas