On 2012-03-10 08:46, Robert P. J. Day wrote:
On Sat, 10 Mar 2012, Gary Thomas wrote:
On 2012-03-10 08:29, Robert P. J. Day wrote:
On Sat, 10 Mar 2012, Gary Thomas wrote:
On 2012-03-10 06:39, Robert P. J. Day wrote:
... snip ...
$ bitbake -c fetchall core-image-minimal
and got somet
On Sat, 10 Mar 2012, Gary Thomas wrote:
> On 2012-03-10 08:29, Robert P. J. Day wrote:
> > On Sat, 10 Mar 2012, Gary Thomas wrote:
> >
> > > On 2012-03-10 06:39, Robert P. J. Day wrote:
> >
> > ... snip ...
> >
> > > > $ bitbake -c fetchall core-image-minimal
> > > >
> > > > and got something
On 2012-03-10 08:29, Robert P. J. Day wrote:
On Sat, 10 Mar 2012, Gary Thomas wrote:
On 2012-03-10 06:39, Robert P. J. Day wrote:
... snip ...
$ bitbake -c fetchall core-image-minimal
and got something unexpected:
NOTE: package bash-4.2-r1: task do_fetch: Started
ERROR: Function faile
On Sat, 10 Mar 2012, Gary Thomas wrote:
> On 2012-03-10 06:39, Robert P. J. Day wrote:
... snip ...
> >$ bitbake -c fetchall core-image-minimal
> >
> > and got something unexpected:
> >
> > NOTE: package bash-4.2-r1: task do_fetch: Started
> > ERROR: Function failed: Network access disabled
On 2012-03-10 06:39, Robert P. J. Day wrote:
On Sat, 10 Mar 2012, Gary Thomas wrote:
All you really need are these lines:
SOURCE_MIRROR_URL ?= "file://${COREBASE}/sources/"
INHERIT += "own-mirrors"
Adjust the SOURCE_MIRROR_URL to wherever you want the files. I also always
add
BB_GENER
from section B.5 of yocto ref manual:
Tell BitBake to load what you want from the environment into the data
store. You can do so through the BB_ENV_WHITELIST variable. For
example, assume you want to prevent the build system from accessing
your $HOME/.ccache directory. The following command tel
On Sat, 10 Mar 2012, Gary Thomas wrote:
> All you really need are these lines:
> SOURCE_MIRROR_URL ?= "file://${COREBASE}/sources/"
> INHERIT += "own-mirrors"
> Adjust the SOURCE_MIRROR_URL to wherever you want the files. I also always
> add
> BB_GENERATE_MIRROR_TARBALLS = "1"
> This will l
On Sat, 10 Mar 2012, Gary Thomas wrote:
> All you really need are these lines:
> SOURCE_MIRROR_URL ?= "file://${COREBASE}/sources/"
> INHERIT += "own-mirrors"
> Adjust the SOURCE_MIRROR_URL to wherever you want the files. I also always
> add
> BB_GENERATE_MIRROR_TARBALLS = "1"
> This will l
On Sat, 10 Mar 2012, Gary Thomas wrote:
> All you really need are these lines:
> SOURCE_MIRROR_URL ?= "file://${COREBASE}/sources/"
ah ... and i see no mention of that in the variable glossary in the
reference manual. :-P i'm assuming that that value is nothing more
than the name of my massi
On 2012-03-10 03:52, Gary Thomas wrote:
On 2012-03-10 03:35, Robert P. J. Day wrote:
over the years, i've built up a sizable collection of source
tarballs for use in various projects -- top-level directory called
"~/dl", about 5G in size with lots and lots of .tgz and .bz2 files and
so on, and
On 2012-03-10 03:35, Robert P. J. Day wrote:
over the years, i've built up a sizable collection of source
tarballs for use in various projects -- top-level directory called
"~/dl", about 5G in size with lots and lots of .tgz and .bz2 files and
so on, and i'd like to confirm the best way to ta
over the years, i've built up a sizable collection of source
tarballs for use in various projects -- top-level directory called
"~/dl", about 5G in size with lots and lots of .tgz and .bz2 files and
so on, and i'd like to confirm the best way to take advantage of all
that source whenever i confi
while i'm working my thru the docs, i want to verify that yocto is
built on top of oe-core straight from the oe-core repo, is that
correct? as in, yocto doesn't make any yocto-specific mods to the
fundamental, lower-level OE core layers, does it? it simply adds
layers on top, right?
rday
--
13 matches
Mail list logo
