| 1 |
> |
| 2 |
> # ls -l /etc/make.profile |
| 3 |
> /etc/make.profile -> ../usr/portage/profiles/default-linux/amd64/2007.0 |
| 4 |
> |
| 5 |
> An old profile can often force a 2.4.x kernel/kernel headers. |
| 6 |
|
| 7 |
|
| 8 |
My /etc/make.profile looks at /usr/portage/profile/linux-default/arm/2007.0 |
| 9 |
|
| 10 |
Also, when was the last time you updated portage? |
| 11 |
|
| 12 |
|
| 13 |
Today, my Portage-Tree is up2date. |
| 14 |
|
| 15 |
If it becomes too difficult, I would suggest trying to rebuild from |
| 16 |
> scratch. The Gentoo Embedded Handbook [1] will give you a toolchain and |
| 17 |
> a basic build environment. Then, I use some of the nslu2-linux docs [2] |
| 18 |
> to test the image. When I have an image I like, the Redboot docs [3] |
| 19 |
> showed me how to burn the image to flash. At the very least, it's a |
| 20 |
> great way to learn embedded development. Also, cross-compiling on a |
| 21 |
> development host is _a_lot_ faster than compiling natively. ;-) |
| 22 |
> |
| 23 |
> At the very least, you'll end up using [2] and [3] once you get your |
| 24 |
> kernel built. |
| 25 |
|
| 26 |
|
| 27 |
I have masked all linux-headers beside version 2.6.16 and my update looks |
| 28 |
very good. |
| 29 |
An update from kernel and kernel-headers I will give a try in the course of |
| 30 |
time. |
| 31 |
|
| 32 |
|
| 33 |
> [1] - http://www.gentoo.org/proj/en/base/embedded/handbook/ |
| 34 |
> [2] - http://www.nslu2-linux.org/wiki/HowTo/TestAnImageInRamUsingRedBoot |
| 35 |
> [3] - |
| 36 |
> http://ecos.sourceware.org/docs-latest/redboot/flash-image-system.html |
| 37 |
> -- |
| 38 |
> gentoo-embedded@l.g.o mailing list |
| 39 |
> |
| 40 |
> |
| 41 |
Thx for any hints. |
| 42 |
|
| 43 |
Sven |
Archives