| 1 |
Hi, |
| 2 |
|
| 3 |
On Tue, 07 Dec 2004 01:51:13 +0100 |
| 4 |
"Buttchereit, Axel (XLsigned)" <XL@××××××××.net> wrote: |
| 5 |
|
| 6 |
> Now for my (open) questions: |
| 7 |
> 1. "buildroot" obviously does not provide a "fully featured" root-fs |
| 8 |
> for |
| 9 |
> kernel-2.6, i. e. with udev, hotplug/coldplug. |
| 10 |
> Anyone out there with experience on that? |
| 11 |
|
| 12 |
I've managed to use the new embedded-stage1 from Gentoo to compile |
| 13 |
myself a basic system, which is at least what buildroot does plus lots |
| 14 |
of more apps. I've even managed to compile xorg (6.8.0-r4 was the only |
| 15 |
one that worked for me right out of the box, it's currently masked). |
| 16 |
|
| 17 |
> 2. ntfsutils, smb, ... are not available in current "buildroot". |
| 18 |
> Anyone out there that has integrated this into "buildroot" |
| 19 |
> already?(or rather compiled/linked against uClibc manually) |
| 20 |
|
| 21 |
Try to use Gentoo, it really works quite well. I've managed to compile |
| 22 |
samba (even the server) and ntfsprogs with the default ebuilds. The NFS |
| 23 |
support mentioned in the subject relies on the kernel as said in recent |
| 24 |
thread here ("can't emerge nfs-utils") but can work, too. Userspace NFS |
| 25 |
doesn't seem to work yet because of not-glibc-like rpc support in |
| 26 |
uclibc. |
| 27 |
|
| 28 |
> 3. "buildroot" uses its own "package management" for downloading and |
| 29 |
> compiling of sources. |
| 30 |
> Is it possible to benefit from "gentoo-portage" and do (a kind |
| 31 |
> of) cross-compiling and linking against uClibc? |
| 32 |
|
| 33 |
Yes, you've got a lot more build scripts. If they work is another |
| 34 |
question. And I personally found it easier to use Gentoo for all this. |
| 35 |
When building your final filesystem, you should make a copy of the build |
| 36 |
system and delete everything that isn't needed. You can, on the other |
| 37 |
hand, build packages when emerging and then use "ROOT=/your/target/root |
| 38 |
emerge -K package" for everything you need. |
| 39 |
|
| 40 |
A last tip: I wouldn't recommend to actually install busybox into your |
| 41 |
dev environment. Just emerge it with "emerge --buildpkgonly busybox" and |
| 42 |
then do a "ROOT=/your/target/root emerge -K busybox" |
| 43 |
|
| 44 |
Note that gentoo won't work as a cross compilation env, AFAIK. |
| 45 |
|
| 46 |
HWH |
| 47 |
|
| 48 |
-- |
| 49 |
gentoo-embedded@g.o mailing list |
Archives