Building minimal-image with kernel24

Building minimal-image with kernel24

[Joshua Lamorie]

Gidday there,

I'm trying to move my development system from buildroot to
openembedded.  

My embedded platform is based on a Virtex-II Pro/Virtex-4 PPC405 and for
various reasons is stuck in linux 2.4.  I've used the xilinx-ml430
machine as an example, and the minimal distro and modified
PREFERRED_PROVIDER_virtual/kernel to refer to a .bb file that I've made
for my 2.4 kernel.

However, when I go to bitbake minimal-image, it keeps trying to build
kernel 2.6.

Are there examples of machines/distros that use 2.4?  How can I tell
where the currently building package was commanded from?  I've tried to
add more debugging, but is there a log somewhere which is insanely
verbose?

Is there a way to build a simple image without the kernel?

Part of the output when I run 'bitbake -v minimal-image' is the
following.

NOTE: checking PREFERRED_PROVIDER_virtual/kernel
NOTE: checking PREFERRED_PROVIDER_linux-rt-2.6.24
NOTE: checking PREFERRED_PROVIDER_linux-rt-2.6.24-r6
NOTE: multiple providers are available for runtime kernel-image (linux,
gumstix-kernel, linux-rt);
NOTE: consider defining a PREFERRED_PROVIDER entry to match runtime
kernel-image

What does this mean define a PREFERRED_PROVIDER entry to match 'runtime
kernel-image'?  What is the 'runtime kernel-image'?

When I run this interactively, (with build minimal-image) and I ask to
display some variables, I get the following:

BB>> getvar PREFERRED_PROVIDER_virtual/kernel
linux-q5-2.4.32.2

That is the kernel that I want.

So, why does it do so much checking?  Where can I see some debug output that says, here
are all the packages I'm going to build?

Thanks in advance for your assistance.

Joshua

p.s. Where is it possible to contribute to the OE manual?

-- 
Xiphos Technologies Inc.
T: 514.847.9474 x 227
F: 514.847.9474

________________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. If you have received this in error, please contact the sender
and delete this communication and any copy immediately. Thank you.

Re: Building minimal-image with kernel24

[Cliff Brake]

On Wed, Dec 10, 2008 at 4:40 PM, Joshua Lamorie <jpl@xiphos.ca> wrote:

> p.s. Where is it possible to contribute to the OE manual?

Check the following branch out of git, and then post patch to bugzilla.

http://git.openembedded.net/?p=openembedded.git;a=shortlog;h=refs/heads/org.openembedded.documentation

Thanks,
Cliff

-- 
=======================
Cliff Brake
http://bec-systems.com

Re: Building minimal-image with kernel24

[Joshua Lamorie]

Gidday there,

Sorry for this simple question, but I've been using subversion up to now, and I can't figure out how to use git to checkout/pull/clone the documentation.  I can see the results of ...

git-ls-remote  --heads git://git.openembedded.net/openembedded.git refs/heads/org.openembedded.documentation

Then, inside the openembedded repository that I cloned with

git clone git://git.openemebbeded.net/openembedded.git

I can see the other branches with

[jpl@megatron openembedded]$ git branch -r

However, as suggested in http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#examining-remote-branches, I do a checkout and I get the following.

[jpl@megatron openembedded]$ git checkout -b documentation origin/org.openembedded.documentation
fatal: Entry 'packages/tinylogin/tinylogin_1.4.bb' not uptodate. Cannot merge.

There is an error in that .bb file (I just added a patch to bugzilla) but shouldn't I be able to get this branch without dealing with the uncommited changes to that file?


Thanks

Joshua

On Wednesday, 10 December, 2008 17:27, "Cliff Brake" <cliff.brake@gmail.com> said:

> On Wed, Dec 10, 2008 at 4:40 PM, Joshua Lamorie <jpl@xiphos.ca> wrote:
> 
>> p.s. Where is it possible to contribute to the OE manual?
> 
> Check the following branch out of git, and then post patch to bugzilla.
> 
> http://git.openembedded.net/?p=openembedded.git;a=shortlog;h=refs/heads/org.openembedded.documentation
> 
> Thanks,
> Cliff
> 
> --
> =======================
> Cliff Brake
> http://bec-systems.com
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 


-- 
Xiphos Technologies
(514) 847-9474 x227
(514) 848-9644 fax

www.xiphos.com
_______________________________________________
The information transmitted is intended only for the
person or entity to which it is addressed and may contain
confidential and/or privileged material.  If you have
received this in error, please contact the sender and delete
this communication and any copy immediately. Thank you.

Re: Building minimal-image with kernel24

[Cliff Brake]

On Thu, Dec 11, 2008 at 12:08 AM, Joshua Lamorie <jpl@xiphos.ca> wrote:
> Gidday there,
>
> Sorry for this simple question, but I've been using subversion up to now, and I can't figure out how to use git to checkout/pull/clone the documentation.  I can see the results of ...
>
> git-ls-remote  --heads git://git.openembedded.net/openembedded.git refs/heads/org.openembedded.documentation
>
> Then, inside the openembedded repository that I cloned with
>
> git clone git://git.openemebbeded.net/openembedded.git
>
> I can see the other branches with
>
> [jpl@megatron openembedded]$ git branch -r
>
> However, as suggested in http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#examining-remote-branches, I do a checkout and I get the following.
>
> [jpl@megatron openembedded]$ git checkout -b documentation origin/org.openembedded.documentation
> fatal: Entry 'packages/tinylogin/tinylogin_1.4.bb' not uptodate. Cannot merge.
>
> There is an error in that .bb file (I just added a patch to bugzilla) but shouldn't I be able to get this branch without dealing with the uncommited changes to that file?

You will need to commit your local changes to a temp branch first.

git checkout -b myfixes org.openembedded.dev
git add ...
git commit

Now that you have no local changes, you can check out the doc

Cliff

-- 
=======================
Cliff Brake
http://bec-systems.com

Re: Building minimal-image with kernel24

[Philip Balister]

[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]

Cliff Brake wrote:
> On Thu, Dec 11, 2008 at 12:08 AM, Joshua Lamorie <jpl@xiphos.ca> wrote:
>> Gidday there,
>>
>> Sorry for this simple question, but I've been using subversion up to now, and I can't figure out how to use git to checkout/pull/clone the documentation.  I can see the results of ...
>>
>> git-ls-remote  --heads git://git.openembedded.net/openembedded.git refs/heads/org.openembedded.documentation
>>
>> Then, inside the openembedded repository that I cloned with
>>
>> git clone git://git.openemebbeded.net/openembedded.git
>>
>> I can see the other branches with
>>
>> [jpl@megatron openembedded]$ git branch -r
>>
>> However, as suggested in http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#examining-remote-branches, I do a checkout and I get the following.
>>
>> [jpl@megatron openembedded]$ git checkout -b documentation origin/org.openembedded.documentation
>> fatal: Entry 'packages/tinylogin/tinylogin_1.4.bb' not uptodate. Cannot merge.
>>
>> There is an error in that .bb file (I just added a patch to bugzilla) but shouldn't I be able to get this branch without dealing with the uncommited changes to that file?
> 
> You will need to commit your local changes to a temp branch first.
> 
> git checkout -b myfixes org.openembedded.dev
> git add ...
> git commit
> 
> Now that you have no local changes, you can check out the doc

You can also use git stash to save local changes. Then can update your 
working copy and re-apply the changes from the "stash". This avoids the 
need to commit stuff you are not certain about.

Philip


> 
> Cliff
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]