pkgsrc-Bugs archive

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

Re: pkg/53319: text relocations fixes for multimedia/mplayer others

The following reply was made to PR pkg/53319; it has been noted by GNATS.

From: Onno van der Linden <>
To: Izumi Tsutsui <>
Subject: Re: pkg/53319: text relocations fixes for multimedia/mplayer others
Date: Mon, 13 Aug 2018 21:36:16 +0200

 On Tue, Aug 14, 2018 at 03:52:09AM +0900, Izumi Tsutsui wrote:
 > >  just like ffmpeg, mplayer and firefox as demonstrated earlier in this PR.
 > >  
 > >  I have my doubts about disabling asm completely for i386 as a fix
 > >  for the "Cannot write-enable text segment: Permission denied" error.
 > I cannot reproduce your problem on my NetBSD/i386 8.0 + pkgsrc-2018Q2
 > environment (for my own liveimage):
 I don't have any problem at all with -current running anything that
 was build with i386 assembler enabled which on 8.0 NetBSD/i386 is causing
 "Cannot write-enable text segment: Permission denied".
 This was fixed with a non too subtle "disable asm" fix in
 the Makefile of a handful of programs in pkgsrc. I have some
 doubts wether this was the right thing to do.
 As I've demonstrated in earlier reports to this PR I was able to
 compile and run everything (PC6001VX, mplayer and ffmpeg) on -current
 that gave "Cannot write-enable text segment" with asm enabled
 in your initial PR for 8.0.
 To be sure I've just compiled ffmpeg4 with asm enabled and
 that also runs without any problem at all.
 So, the question is why I don't have any problem running these
 programs with asm *enabled* on -current ? Could be paxctl
 and FORTIFY_SOURCE related, but why am I not seeing the
 error messages you were seeing with the programs that were build
 using the i386 assemebler code ? Were the 8.0 binaries build
 with stricter options ?

Home | Main Index | Thread Index | Old Index