Re: [Gumstix-users] How to tell bitbake not to fetch?

[rich105 <ric...@gm...>]

Follow-up with solution for this self-inflicted error.  This generic error
was caused by bitbake not being able to find the makefile.  When I reworked
the recipe to get around my 'git' problems, I used file URLs instead of
network ones, and copied the tar locally, which worked, partially.  The
unpacking mechanism places the files in a uboot directory under the .../temp
tree for this package, which is different than what is done when the files
are pulled via git.  To resolve, I manually moved the unpacked files from 
/tmp/work/overo-angstrom-linux-gnueabi/u-boot-omap3-2009.11.1+r0+git92222b9a44bcf117499f4d48409687cf9c6ebd0d-r0/temp/uboot,
to 
/tmp/work/overo-angstrom-linux-gnueabi/u-boot-omap3-2009.11.1+r0+git92222b9a44bcf117499f4d48409687cf9c6ebd0d-r0/temp/git

and the recipe was satisfied.  I had to rediscover this after a subsequent
rebuild, so this time, I'm logging it where I'll be able to find it again :)

I doubt anyone else will need this, since this was a result of my own
fiddling, but there it is.

-Rich


rich105 wrote:
> 
> I cheated, and commented out the SRC_URI reference to the repository in
> the
> recipe, and it found and unpacked the tar file.  I also created an MD5
> file
> for it to find.   It went further this time, but complained about:
> 
> NOTE: make CROSS_COMPILE=arm-angstrom-linux-gnueabi- omap3_overo_config
> make: *** No rule to make target `omap3_overo_config'.  Stop.
> FATAL: oe_runmake failed
> 
> That was when I bitbaked u-boot-omap3.  I've since started a bitbake of
> omap3-custom-image, to see what else it'll find, so I'll post a follow up
> later if I find anything I think would be valuable to someone else!
> 
> Thanks for the suggestions,
> Rich
> 
> 

-- 
View this message in context: http://old.nabble.com/How-to-tell-bitbake-not-to-fetch--tp28821224p29085661.html
Sent from the Gumstix mailing list archive at Nabble.com.