| Summary: | uClibc 0.9.28.3 fails to build | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Luke <luke_tucker> |
| Component: | Outdated package | Assignee: | unassigned |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | buildroot |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | 2010.02 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | openSuSE 11.1 | Target: | mipsel TViX DVICO m-6500 |
| Build: | |||
|
Description
Luke
2009-03-07 23:27:09 UTC
I looked at 0.9.29 and found an easy patch: --- uClibc-0.9.28.3/libc/sysdeps/linux/mips/clone.S.orig 2009-03-08 01:00:30.000000000 +0100 +++ uClibc-0.9.28.3/libc/sysdeps/linux/mips/clone.S 2009-03-08 01:01:06.000000000 +0100 @@ -24,7 +24,7 @@ #include <sys/regdef.h> #define _ERRNO_H 1 #include <bits/errno.h> -#include <asm/asm.h> +#include <sys/asm.h> /* int clone(int (*fn)(void *arg), void *child_stack, int flags, void *arg) */ Ooops, I jumped the gun a bit. The asm directory also needs patching in the following files.
--- uClibc-0.9.28.3/libc/sysdeps/linux/mips/pipe.S.orig 2009-03-08 01:15:35.000000000 +0100
+++ uClibc-0.9.28.3/libc/sysdeps/linux/mips/pipe.S 2009-03-08 01:16:35.000000000 +0100
@@ -3,9 +3,9 @@
/*see uClibc's sh/pipe.c and glibc-2.2.4's mips/pipe.S */
#include <features.h>
-#include <asm/asm.h>
+#include <sys/asm.h>
#include <asm/unistd.h>
-#include <asm/regdef.h>
+#include <sys/regdef.h>
.globl pipe
.ent pipe, 0
--- uClibc-0.9.28.3/libc/sysdeps/linux/mips/syscall.S.orig 2009-03-08 01:07:34.000000000 +0100
+++ uClibc-0.9.28.3/libc/sysdeps/linux/mips/syscall.S 2009-03-08 01:09:24.000000000 +0100
@@ -17,8 +17,8 @@
02111-1307 USA. */
#include <features.h>
-#include <asm/asm.h>
-#include <asm/regdef.h>
+#include <sys/asm.h>
+#include <sys/regdef.h>
#ifdef __PIC__
.option pic2
I would suggest to add http://lists.busybox.net/pipermail/uclibc-cvs/2006-September/023471.html to our list of patches, or to remove support for the obsolete 0.9.28.3 version of uClibc. uClibc 0.9.28 is deprecated, so I'm closing this bug. If you ever have an issue with a more recent version (0.9.30 or 0.9.31), do not hesitate to open another bug. Thanks! |