From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7941] New: glibc-2.20 fails to build for sparc-buildroot-linux-gnu
Date: Tue, 17 Mar 2015 19:08:20 +0000 (UTC) [thread overview]
Message-ID: <bug-7941-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7941
Host: x86_64
Target: sparc-buildroot-linux-gnu
Summary: glibc-2.20 fails to build for
sparc-buildroot-linux-gnu
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: uwe at hermann-uwe.de
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5926
--> https://bugs.busybox.net/attachment.cgi?id=5926
build log
I've tried to build glibc for in git HEAD as of today.
Here's the first error message, full log as attachment.
../sysdeps/sparc/sparc32/sem_trywait.c: In function '__new_sem_trywait':
../sysdeps/sparc/sparc32/sem_trywait.c:35:11: error: dereferencing pointer to
incomplete type
if (isem->value > 0)
^
In file included from ../include/list.h:45:0,
from ../sysdeps/sparc/nptl/tls.h:28,
from ../include/errno.h:27,
from ../sysdeps/sparc/sparc32/sem_trywait.c:20:
../sysdeps/sparc/sparc32/sem_trywait.c:38:43: error: dereferencing pointer to
incomplete type
val = atomic_decrement_if_positive (&isem->value);
^
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2015-03-17 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 19:08 bugzilla at busybox.net [this message]
2015-03-17 21:47 ` [Buildroot] [Bug 7941] glibc-2.20 fails to build for sparc-buildroot-linux-gnu bugzilla at busybox.net
2015-03-17 21:50 ` bugzilla at busybox.net
2015-03-17 22:20 ` 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-7941-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