From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11961] New: libpri build failure
Date: Thu, 13 Jun 2019 22:02:35 +0000 [thread overview]
Message-ID: <bug-11961-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11961
Bug ID: 11961
Summary: libpri build failure
Product: buildroot
Version: 2019.02.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: zinosat at tiscali.it
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 8096
--> https://bugs.busybox.net/attachment.cgi?id=8096&action=edit
libpri build failure
I've tried to include libpri in a build based on pc_x86_64_bios_defconfig and
using x86-64-core-i7--glibc--bleeding-edge-2018.11-1.tar.bz2
it fails to build: see the attached log for details.
thank you
Davide
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-06-13 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 22:02 bugzilla at busybox.net [this message]
2019-06-14 8:39 ` [Buildroot] [Bug 11961] libpri build failure bugzilla at busybox.net
2019-06-14 8:40 ` bugzilla at busybox.net
2019-08-17 21:51 ` 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-11961-163@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