All of 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: Mon, 23 Oct 2017 11:40:58 +0000	[thread overview]
Message-ID: <bug-10451-163-MT2pEtt0Gx@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10451-163@https.bugs.busybox.net/>

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

--- Comment #1 from Karl Krach <mail@kkrach.de> ---

Libpcap in version 1.8.1 and 1.7.4 doesn't compile with PPC gcc 7.2.0. When
downgrading to 1.6.2 the compilation succeeds.

Buildroot is version 2017.08.



Full GCC Version:

./output/host/bin/powerpc-buildroot-linux-uclibcspe-gcc --version
powerpc-buildroot-linux-uclibcspe-gcc.br_real (Buildroot 2017.08-dirty) 7.2.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

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

  reply	other threads:[~2017-10-23 11:40 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 ` bugzilla at busybox.net [this message]
2017-10-23 11:42 ` [Buildroot] [Bug 10451] " 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

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-MT2pEtt0Gx@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.