Re: help bitbaking bootstrap-image on org.openembedded.oz354x
George Hartzell <[email protected]>
| Newsgroups | gmane.comp.handhelds.openzaurus.devel |
|---|---|
| Message-ID | <[email protected]> |
Dirk Opfer writes:
> Hi George,
>
> George Hartzell schrieb:
> > I'm trying to learn how to use the OE tools to build an openzaurs
> > distribution for a tosa. I'd like to use kernel 2.6.
> >
> > It dies w/ the following message:
> >
> > ----------------------------------------------------------------
> >
> > | Nothing to be done
> > | An error ocurred, return value: 1.
> > | Collected errors:
> > | ERROR: Cannot satisfy the following dependencies for task-bootstrap:
> > | wlan-ng-modules-usb
> > NOTE: Task failed: /home/hartzell/openembedded/tmp/work/bootstrap-image-1.0-r1/temp/log.do_rootfs.28048
> > NOTE: package bootstrap-image-1.0-r1: task do_rootfs: failed
> > ERROR: TaskFailed event exception, aborting
> >
> > ----------------------------------------------------------------
> >
> > I'm not sure how to read it, but I *think* it's telling me that there
> > were several recommendations that it couldn't satisfy but that it died
> > because it couldn't satisfy the wlan-ng-modules-usb requirement.
> >
> > So, I have two questions:
> >
> > 1) how do I fix this?
> >
> >
> I just checked in a patch to solve this issue. Now bitbake should build
> the wlan-ng-modules.
>
Thanks for the fix!
It would help me a lot if you said a few words about what the fix
is/does and why it works.
You've probably heard the addage:
Give a man a fish and you feed him for a day. Teach a man to fish
and you feed him for a lifetime.
I'm trying to understand how bitbake works, and issues like this are
great opportunities for those of you who understand this stuff to pass
on some info. Once it's posted here people will read it, google will
find it, etc....
It looks like you just added a BOOTSTRAP_EXTRA_DEPENDS line for
wlan-ng-modules. I'd discovered that bitbaking that recipe by hand
after task-bootstrap failed, then re-bitbaking task-bootstrap and/or
bootstrap-image was enough to successfully build an image.
But it looks like the wlan-ng-modules recipe builds a
wlan-ng-modules-usb ipk file. If so, why do we still need to add
wlan-ng-modules-usb to the BOOTSTRAP_EXTRA_RDEPENDS?
Can someone say a few words about the relationship between DEPENDS and
RDEPENDS?
Even with my hacky work around, I still wasn't able to get wireless to
work:
- I was using ifup wlan0 to bring up the interface. That tries to
run usbctl, presumably to start up the hardware?
I didn't have a usbctl though I was able to build one with the
wlan-ng-utils recipe.
But, it doesn't work, it exits after complaining 'No such file or
directory'.
I tried to look at the source for usbctl, but it seems to be
checked into the tree as a compiled binary. What's up with that?
Running strings on the binary shows the path '/dev/usb/ohci',
which doesn't exist.
Have I missed a configuration step?
What is the proper way to bring up the wireless interface on a
tosa running a 2.6 kernel?
And worse still, the branch is broken in a different place. It dies
trying to build qemu as a dependency to glibc. I'll post a question
about that as a separate thread.
Thanks!
g.
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642