[uClibc] n00b Questions
Quantum Scientific
Info at Quantum-Sci.com
Fri Apr 1 15:55:52 UTC 2005
I took out hotplug, and now iptables is busted. Maybe uClibc just isn't going to work out.
-----------------------------------------------------------
/usr/src/buildroot/build_mipsel/+toolchain/bin/mipsel-linux-uclibc-gcc -Os -pipe -Wall -Wunused -I/include -Iinclude/ -DIPTABLES_VERSION=\"1.2.11\" -D_UNKNOWN_KERNEL_POINTER_SIZE -fPIC -o extensions/libipt_DNAT_sh.o -c extensions/libipt_DNAT.c
extensions/libipt_DNAT.c:16: error: field `mr' has incomplete type
extensions/libipt_DNAT.c:232: error: invalid application of `sizeof' to incomplete type `ip_nat_multi_range_compat'
extensions/libipt_DNAT.c:233: error: invalid application of `sizeof' to incomplete type `ip_nat_multi_range_compat'
make[1]: *** [extensions/libipt_DNAT_sh.o] Error 1
make[1]: Leaving directory `/usr/src/buildroot/build_mipsel/iptables-1.2.11'
make: *** [/usr/src/buildroot/build_mipsel/iptables-1.2.11/iptables] Error 2
/usr/src/buildroot #
-----------------------------------------------------------
On Friday 01 April 2005 7:57, Quantum Scientific wrote:
> Well, I removed hostap from the packages, and the linux/pcmcia error went
> away. Sure wish I could have HostAP, or at least WDS. (Not using pcmcia...
> minipci)
>
> But now it's crashing so:
> -----------------------------------------------------------
> make[1]: Entering directory `/usr/src/buildroot/build_mipsel/diethotplug-0.4'
> perl convert_usb.pl
> < /usr/src/buildroot/build_mipsel/root/lib/modules/2.6.11/modules.usbmap >
> usb_modules.h
> /bin/sh: /usr/src/buildroot/build_mipsel/root/lib/modules/2.6.11/modules.usbmap:
> No such file or directory
> make[1]: *** [usb_modules.h] Error 1
> make[1]: Leaving directory `/usr/src/buildroot/build_mipsel/diethotplug-0.4'
> make: *** [/usr/src/buildroot/build_mipsel/diethotplug-0.4/hotplug] Error 2
> /usr/src/uclibc-buildroot-mipsel26 #
> -----------------------------------------------------------
>
> It appears that this is because the kernel is not built... chicken & egg? Is
> it possible to conveniently build hotplug in the chroot environment?
>
> Any input on the below questions?
>
> Best,
>
> Carl Cook
>
>
>
> On Thursday 31 March 2005 14:14, Quantum Scientific wrote:
> > Hello List,
> >
> > Am testing buildroot-20050330, and it looks really good.
> >
> > Target system is the Belkin F5D7230 wireless router (mipsel). In looking
> > through Belkin's apps, I find that they were compiled with "GCC: (GNU) 3.2.3
> > with Broadcom modifications)". Now, the CPU and switch chips are Broadcom,
> > so does anyone know what these modifications might be? (Broadcom ain't
> > talking)
> >
> > Is there any way to add these modifications in buildroot? I would think
> they
> > are GPLed, but darned if I can find them anywhere. The Linksys GPL source
> > comes with an older toolchain that has these modifications, but I'd rather
> > use the newer versions of everything if possible. (buildroot)
> >
> > Is there any chance that the Askey radio driver, which runs on kernel
> 2.4.20,
> > would run on 2.6.11? We have no chance of getting the source, and there's
> > probably not a newer binary.
> >
> > I'm getting compile failures:
> > -----------------------------------------------------------
> >
> cp /usr/src/uclibc-buildroot-mipsel26/build_mipsel/dropbear-0.45/S50dropbear /usr/src/uclibc-buildroot-mipsel26/build_mipsel/root/etc/init.d/
> > chmod
> >
> a+x /usr/src/uclibc-buildroot-mipsel26/build_mipsel/root/etc/init.d/S50dropbear
> > make: *** No rule to make target `linux', needed by `pcmcia'. Stop.
> > /usr/src/uclibc-buildroot-mipsel26 #
> > -----------------------------------------------------------
> > I hadn't selected linux. So tried setting up buildroot with Board Support
> > Options > linux but still dumps. (Does this in fact build the kernel into
> > the target root? If so, how to provide custom kernel .config?)
> > Why the crash above? Why is pcmcia noted, I'm not including it?
> >
> > If I set the target to cramfs, can I make modifications and compile within?
> > The final image will bundle the cramfs with external kernel using trx. Is
> it
> > possible to select both cramfs and ext2 at the same time? Or should I just
> > chroot into the target root dir to modify, and later mkcramfs?
> >
> > If I do not build the native toolchain into the target root, can I still
> > compile to target while chrooted? If so, this would considerably reduce
> space
> > needed.
> >
> > Is the recommended procedure:
> > cd /target/root
> > cp -L /etc/resolv.conf target/root/etc
> > mount -t proc none target/root/proc
> > chroot target/root/ /bin/bash
> > If so, it wouldn't seem to have a path outside to mipsel-linux-gcc, etc.
> > Maybe symlink these in the target before chroot?
> >
> > Is the libelf package needed, if simply the target apps will be elf?
> >
> > When I select less, then ncurses is ---'d out. Does this mean *selected*?
> I
> > don't end up with libncurses in the target root after compile.
> >
> > Thanks for the input.
> >
> > Best,
> >
> > Carl Cook
> >
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://uclibc.org/mailman/listinfo/uclibc
>
>
>
More information about the uClibc
mailing list