Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10451] libpcap 1.8.x and 1.7x does not compile on PPC
Date: Tue, 31 Oct 2017 20:57:01 +0000	[thread overview]
Message-ID: <bug-10451-163-63WoPnR37w@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10451-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=10451

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #6 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I'm going to close this bug because this is not a Buildroot bug, but a gcc
issue.

However, I don't think we caught this issue with our autobuilders, which means
our coverage of PowerPC testing isn't great. Karl, would you mind reviewing
https://git.buildroot.org/buildroot/tree/support/config-fragments/autobuild and
see if the set of PowerPC configurations is relevant or not ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2017-10-31 20:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 11:38 [Buildroot] [Bug 10451] New: libpcap 1.8.x and 1.7x does not compile on PPC bugzilla at busybox.net
2017-10-23 11:40 ` [Buildroot] [Bug 10451] " bugzilla at busybox.net
2017-10-23 11:42 ` bugzilla at busybox.net
2017-10-23 11:43 ` bugzilla at busybox.net
2017-10-23 11:45 ` bugzilla at busybox.net
2017-10-23 11:50 ` bugzilla at busybox.net
2017-10-23 12:18 ` bugzilla at busybox.net
2017-10-25 18:51 ` bugzilla at busybox.net
2017-10-31 20:57 ` bugzilla at busybox.net [this message]

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-10451-163-63WoPnR37w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox