public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/100207] -Werror=format-security error in AUR build of libgccjit
Date: Thu, 22 Apr 2021 15:04:28 +0000	[thread overview]
Message-ID: <bug-100207-4-4XT6EywcuR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100207-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to sujay1844 from comment #13)
> (In reply to David Malcolm from comment #12)
> > Is that the default /etc/makepkg.conf, or did you hand-edit it?  (i.e is
> > this something that all AUR users are going to run into, or just you?)
> > 
> > Clearly the "-Werror=format-security" is not compatible with building
> > libgccjit; I think "-fexceptions" is probably not a good idea either.
> 
> Nope I don't think I ever opened this. In fact, I just came to know that it
> exists a few minutes back. Please suggest the settings to change.

I wonder if it's just you that's running into this, or it's affecting everyone
using libgccjit via AUR.

I think you need to take this downstream, to the AUR community; it appears that
the default /etc/makepkg.conf is injecting build flags that are incompatible
with libgccjit, so either the default needs to change, or libgccjit's PKGBUILD
needs to change.  Hopefully the above discussion has enough information for the
downstream AUR experts to fix things.

  parent reply	other threads:[~2021-04-22 15:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 12:03 [Bug jit/100207] New: Error in build() sujay1844 at protonmail dot com
2021-04-22 12:30 ` [Bug jit/100207] " marxin at gcc dot gnu.org
2021-04-22 12:31 ` sujay1844 at protonmail dot com
2021-04-22 12:38 ` marxin at gcc dot gnu.org
2021-04-22 13:42 ` dmalcolm at gcc dot gnu.org
2021-04-22 13:46 ` [Bug jit/100207] -Werror=format-security error in AUR build of libgccjit dmalcolm at gcc dot gnu.org
2021-04-22 13:48 ` sujay1844 at protonmail dot com
2021-04-22 13:49 ` sujay1844 at protonmail dot com
2021-04-22 13:49 ` sujay1844 at protonmail dot com
2021-04-22 13:52 ` sujay1844 at protonmail dot com
2021-04-22 14:09 ` dmalcolm at gcc dot gnu.org
2021-04-22 14:12 ` sujay1844 at protonmail dot com
2021-04-22 14:19 ` dmalcolm at gcc dot gnu.org
2021-04-22 14:21 ` sujay1844 at protonmail dot com
2021-04-22 15:04 ` dmalcolm at gcc dot gnu.org [this message]
2021-04-22 15:27 ` sujay1844 at protonmail dot com
2021-05-10  0:43 ` jonathon at m2x dot dev
2021-05-10  1:18 ` sujay1844 at protonmail dot com
2021-05-10  1:34 ` jonathon at m2x dot dev
2021-05-10  1:36 ` sujay1844 at protonmail dot com
2021-05-10  1:39 ` sujay1844 at protonmail dot com

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-100207-4-4XT6EywcuR@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).