public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "swilde@sha-bang.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug jit/100096] New: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 Date: Thu, 15 Apr 2021 11:14:00 +0000 [thread overview] Message-ID: <bug-100096-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096 Bug ID: 100096 Summary: libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: jit Assignee: dmalcolm at gcc dot gnu.org Reporter: swilde@sha-bang.de Target Milestone: --- On NetBSD 9.1 i386 the Hello World example from https://gcc.gnu.org/onlinedocs/jit/intro/tutorial01.html fails with: % ./tut01-hello-world /usr/local/lib/libgccjit.so.0: text relocations /usr/local/lib/libgccjit.so.0: Cannot write-enable text segment: Permission denied when security.pax.mprotect.global is enabled, which is the default on the system. When disabelin global memory protection (as root) with: sysctl -w security.pax.mprotect.global=0 The example works (still emitting a warning: % ./tut01-hello-world /usr/local/lib/libgccjit.so.0: text relocations hello world Turning of security.pax.mprotect.global shouldn't be required for libgccjit to work. Also the warning "/usr/local/lib/libgccjit.so.0: text relocations" should be prevented if possible.
next reply other threads:[~2021-04-15 11:14 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 11:14 swilde@sha-bang.de [this message] 2021-04-15 12:18 ` [Bug jit/100096] " jakub at gcc dot gnu.org 2021-04-15 13:21 ` swilde@sha-bang.de 2021-04-15 13:23 ` jakub at gcc dot gnu.org 2021-04-15 13:30 ` swilde@sha-bang.de 2021-04-15 13:32 ` swilde@sha-bang.de 2021-04-15 13:36 ` swilde@sha-bang.de 2021-04-15 13:38 ` schwab@linux-m68k.org 2021-04-15 13:47 ` dmalcolm at gcc dot gnu.org 2021-04-15 14:03 ` jakub at gcc dot gnu.org 2021-04-15 14:41 ` swilde@sha-bang.de 2021-04-15 14:42 ` swilde@sha-bang.de 2021-04-15 14:58 ` swilde@sha-bang.de 2021-04-15 15:00 ` jakub at gcc dot gnu.org 2021-04-15 15:08 ` jakub at gcc dot gnu.org 2021-04-15 16:13 ` swilde@sha-bang.de 2021-04-15 17:44 ` dmalcolm at gcc dot gnu.org 2021-04-15 20:07 ` swilde@sha-bang.de 2021-04-16 9:37 ` swilde@sha-bang.de 2021-04-16 9:38 ` swilde@sha-bang.de 2021-04-16 11:28 ` jakub at gcc dot gnu.org 2021-04-16 12:18 ` wilde@sha-bang.de 2021-04-16 12:25 ` jakub at gcc dot gnu.org 2021-04-16 14:32 ` wilde@sha-bang.de 2021-04-16 16:35 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:53 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:12 ` jakub at gcc dot gnu.org 2021-09-11 14:29 ` pinskia at gcc dot gnu.org 2022-06-27 8:28 ` swilde@sha-bang.de 2023-07-24 8:54 ` swilde@sha-bang.de
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-100096-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).