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: Wed, 25 Oct 2017 18:51:19 +0000	[thread overview]
Message-ID: <bug-10451-163-O09rhSv1ZV@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 #5 from Arnout Vandecappelle <arnout@mind.be> ---
Internal compiler error, so ideally you should report this to upstream GCC. I
would first of all try playing with the command line options like -O3 and -fpic
(replace with e.g. -fPIC) and the -mfloat-gprs and -Wa,-me500x2 options. You
can also try to strip down pcap.c to the minimal thing that exposes the issue -
that is needed for reporting the bug to GCC.

I do assume that the patches in ../../projects/92107-110/br_patches do not
affect libpcap or gcc?

You can also try with an unpatched GCC:
make host-gcc-final-dirclean
make host-gcc-final-extract
mv output/build/host-gcc-final-*/ /tmp/
make HOST_GCC_FINAL_OVERRIDE_SRCDIR=/tmp/host-gcc-final-* libpcap

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

  parent reply	other threads:[~2017-10-25 18:51 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 [this message]
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-O09rhSv1ZV@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