From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 363] New: uClibc build fails in 2009.05-rc3
Date: Sat, 30 May 2009 20:42:29 +0000 (UTC) [thread overview]
Message-ID: <bug-363-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=363
Host: x86
Target: mips
Summary: uClibc build fails in 2009.05-rc3
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: eike at sf-mail.de
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=369)
--> (https://bugs.busybox.net/attachment.cgi?id=369)
Configuration used
I tested 2009.05-rc3 on my openSuSE 11.1 (x86) and it fails with this error:
make[1]: Entering directory
`/home/eike/repos/buildroot-2009.05-rc3/toolchain_build_mips/uClibc-0.9.30.1'
CC libpthread/linuxthreads/sysdeps/pthread/errno-loc.oS
In file included from libpthread/linuxthreads/sysdeps/pthread/errno-loc.c:23:
./libpthread/linuxthreads/sysdeps/unix/sysv/linux/mips/sysdep-cancel.h:20:20:
error: sysdep.h: No such file or directory
make[1]: *** [libpthread/linuxthreads/sysdeps/pthread/errno-loc.oS] Fehler 1
make[1]: Leaving directory
`/home/eike/repos/buildroot-2009.05-rc3/toolchain_build_mips/uClibc-0.9.30.1'
make: ***
[/home/eike/repos/buildroot-2009.05-rc3/build_mips/staging_dir/usr/lib/libc.a]
Fehler 2
--
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:[~2009-05-30 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 20:42 bugzilla at busybox.net [this message]
2009-05-31 5:45 ` [Buildroot] [Bug 363] uClibc build fails in 2009.05-rc3 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-363-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