1 |
So the uClibc build script |
2 |
(/var/tmp/portage/uclibc-0.9.28/work/uClibc-0.9.28/extra/scripts/fix_includes.sh) |
3 |
tries to find UTS_RELEASE in include/linux/version.h |
4 |
|
5 |
There are only 2 entries though, |
6 |
|
7 |
#define LINUX_VERSION_CODE 132626 |
8 |
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c)) |
9 |
|
10 |
if you turn 132626 into hex it's 20612 ... does that correspond to 2.6.12 ? |
11 |
|
12 |
My work-around was just to patch include/linux/version.h with |
13 |
|
14 |
#define UTS_RELEASE "2.6.18" |
15 |
|
16 |
However, in uClibc, the scripts should take into account the (newer?) |
17 |
LINUX_VERSION_CODE field. |
18 |
|
19 |
Has anyone filed this as a bug? |
20 |
|
21 |
~/Chris |
22 |
|
23 |
Christopher Friedt wrote: |
24 |
> I encountered the same error when building uclibc-0.9.28 using 'xmerge'. |
25 |
> |
26 |
> You're right, there should be some way to specify the kernel version for |
27 |
> uclibc in the case that UTS_RELEASE isn't declared in |
28 |
> include/linux/version.h |
29 |
> |
30 |
> Has there been any new development? |
31 |
> |
32 |
> ~/Chris |
33 |
> |
34 |
> thomas.cooksey@××.com wrote: |
35 |
>> I'm trying to use crossdev to generate a toolchain for an |
36 |
>> arm-softfloat-linux-uclibc target. I'm using the following versions: |
37 |
>> |
38 |
>> binutils 2.17 |
39 |
>> gcc 3.4.5 |
40 |
>> kernel 2.6.18 |
41 |
>> libc 0.9.28-r1 |
42 |
>> |
43 |
>> The command I'm using is: |
44 |
>> |
45 |
>> USE="-*" UCLIBC_CPU=ARM_XSCALE crossdev --binutils 2.17 --gcc 3.4.5 |
46 |
>> --kernel 2.6.18 --libc 0.9.28-r1 --target arm-softfloat-linux-uclibc |
47 |
>> |
48 |
>> The build fails on uclibc at the point it runs the fix_includes.sh |
49 |
>> script, which fails saying "Unable to determine version for kernel |
50 |
>> headers". I've looked at the version.h in the |
51 |
>> /usr/arm-softfloat-linux-uclibc/usr/include/linux directory and it is |
52 |
>> indeed missing the UTS_RELEASE define. If you edit version.h and add |
53 |
>> "#define UST_RELEASE "2.6.18foo"", the build runs through to the end |
54 |
>> (although I've not had chance to test the binaries it outputs yet). |
55 |
>> |
56 |
>> Editing the version.h file by hand feels like a bit of a bodge. Is there |
57 |
>> a fix for this? E.g. by adding a use flag I don't know about? |
58 |
>> |
59 |
>> |
60 |
>> |
61 |
>> Cheers, |
62 |
>> |
63 |
>> Tom |
64 |
>> |
65 |
>> |
66 |
>> |
67 |
-- |
68 |
gentoo-embedded@g.o mailing list |