From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11476] stdio2.h error invalid use of __builtin_va_arg_pack
Date: Fri, 02 Nov 2018 17:50:44 +0000 [thread overview]
Message-ID: <bug-11476-163-FUtCxGtW8Z@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11476-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11476
--- Comment #5 from goldstar611 at hotmail.com ---
I have not had any problems thus far with gcc6, so I personally don't have a
problem with dropping gcc5 support but I would suggest making Fortify_Source
require gcc>=6 for ppc iff there are no plans for dropping gcc5 for other
arches.
If it would help I can volunteer to run a matrix of PPC big endian builds to
see which of them fail.
At some point us PowerPC guys won't have much left but unsupported tools
unfortunately.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-11-02 17:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 23:21 [Buildroot] [Bug 11476] New: stdio2.h error invalid use of __builtin_va_arg_pack bugzilla at busybox.net
2018-11-02 0:40 ` [Buildroot] [Bug 11476] " bugzilla at busybox.net
2018-11-02 0:56 ` bugzilla at busybox.net
2018-11-02 8:44 ` bugzilla at busybox.net
2018-11-02 8:44 ` bugzilla at busybox.net
2018-11-02 15:03 ` bugzilla at busybox.net
2018-11-02 17:15 ` bugzilla at busybox.net
2018-11-02 17:50 ` bugzilla at busybox.net [this message]
2018-11-03 11:31 ` bugzilla at busybox.net
2018-11-03 11:41 ` Romain Naour
2018-11-04 21:56 ` bugzilla at busybox.net
2018-12-03 12:51 ` bugzilla at busybox.net
2018-12-06 10:38 ` bugzilla at busybox.net
2018-12-06 10:40 ` bugzilla at busybox.net
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-11476-163-FUtCxGtW8Z@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.