public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug jit/100096] libgccjit.so.0: Cannot write-enable text segment: Permission denied on NetBSD 9.1 Date: Fri, 16 Apr 2021 16:35:14 +0000 [thread overview] Message-ID: <bug-100096-4-rXb9KCAIWj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100096-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100096 --- Comment #24 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:4a1493f0603262a7dc1114d9827353e9810e63dc commit r11-8225-g4a1493f0603262a7dc1114d9827353e9810e63dc Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Apr 16 18:32:27 2021 +0200 intl: Add --enable-host-shared support [PR100096] As mentioned in the PR, building gcc with jit enabled and --enable-host-shared doesn't work on NetBSD/i?86, as libgccjit.so.0 has text relocations. The r0-125846-g459260ecf8b420b029601a664cdb21c185268ecb changes added --enable-host-shared support to various libraries, but didn't add it to intl/ subdirectory; on Linux it isn't really needed, because all: all-no all-no: #nothing but on other OSes intl/libintl.a is built. The following patch makes sure it is built with -fPIC when --enable-host-shared is used. 2021-04-16 Jakub Jelinek <jakub@redhat.com> PR jit/100096 * configure.ac: Add --enable-host-shared support. * Makefile.in: Update copyright. Add @PICFLAG@ to CFLAGS. * configure: Regenerated.
next prev parent reply other threads:[~2021-04-16 16:35 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 11:14 [Bug jit/100096] New: " swilde@sha-bang.de 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 [this message] 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-rXb9KCAIWj@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).