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 bootstrap/110550] libintl build without -fPIC even though --enable-shared is configured
Date: Fri, 14 Jul 2023 12:06:35 +0000	[thread overview]
Message-ID: <bug-110550-4-ZyE2JBkSgB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110550-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110550

--- Comment #2 from Sascha Wilde <swilde@sha-bang.de> ---
(please excuse my late reply)

Indeed without jit the build works as expected.

However, jit is the primary reason I'm building gcc on NetBSD.  
Building relocateable code also in the supporting libraries is essential 
for jit to work. (see also #100096 for reference)

  parent reply	other threads:[~2023-07-14 12:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 17:08 [Bug other/110550] New: " swilde@sha-bang.de
2023-07-05  7:05 ` [Bug bootstrap/110550] " rguenth at gcc dot gnu.org
2023-07-14 12:06 ` swilde@sha-bang.de [this message]
2023-07-28  8:19 ` 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-110550-4-ZyE2JBkSgB@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: link
Be 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).