Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Hauser, Wolfgang (external)]

Hello,

I added a new machine definition for our hardware (hardware is almost
like beagleboard xM) and want to add the specific patches and
configurations by using the amend class in my additional layer.

If I amend the kernel recipe (linux-omap-psp_2.6.32.bb) for machines
contained in COMPATIBLE_MACHINE, the amend.inc is found and my
amendments are done well (for omap3evm and beagleboard).

If I want to build the kernel for my machine, the kernel recipe
linux-omap-psp_2.6.32.bb was skipped in case of not containing my new
machine in COMPATIBLE_MACHINE and the wrong kernel is build.

I need only a view additions to the linux-omap-psp-2.6.32 kernel so I
don't want to copy the original recipe into my layer and change it. I
have to build my system for omap3evm, beagleboard and our specific
hardware.

Is there a possibility to avoid the skipping of the kernel recipe for a
machine not contained in COMPATIBLE_MACHINE ? Or add the machine for
amending somewhere ?

I use the 2011.03 release and bitbake version 1.10.2.

Regards
Wolfgang

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08-06-11 13:44, Hauser, Wolfgang (external) wrote:
> Hello,
> 
> I added a new machine definition for our hardware (hardware is almost
> like beagleboard xM) and want to add the specific patches and
> configurations by using the amend class in my additional layer.
> 
> If I amend the kernel recipe (linux-omap-psp_2.6.32.bb) for machines
> contained in COMPATIBLE_MACHINE, the amend.inc is found and my
> amendments are done well (for omap3evm and beagleboard).
> 
> If I want to build the kernel for my machine, the kernel recipe
> linux-omap-psp_2.6.32.bb was skipped in case of not containing my new
> machine in COMPATIBLE_MACHINE and the wrong kernel is build.
> 
> I need only a view additions to the linux-omap-psp-2.6.32 kernel so I
> don't want to copy the original recipe into my layer and change it. I
> have to build my system for omap3evm, beagleboard and our specific
> hardware.
> 
> Is there a possibility to avoid the skipping of the kernel recipe for a
> machine not contained in COMPATIBLE_MACHINE ? Or add the machine for
> amending somewhere ?

Stupid question: why not send patches to add your machine to OE?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN72M/MkyGM64RGpERAhLTAJ9qHNv0eInsZR/TlEroTi9tEV2aawCfdVJg
OpHnn2F0ulVD9E8Jh6fPMDc=
=S3P7
-----END PGP SIGNATURE-----

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Phil Blundell]

On Wed, 2011-06-08 at 13:44 +0200, Hauser, Wolfgang (external) wrote:
> Is there a possibility to avoid the skipping of the kernel recipe for a
> machine not contained in COMPATIBLE_MACHINE ? Or add the machine for
> amending somewhere ?

Can you not just arrange for your layer to add your own machine to the
recipe's COMPATIBLE_MACHINE definition?

p.

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Hauser, Wolfgang (external)]

>Stupid question: why not send patches to add your machine to OE?

Because it is a uncommon special hardware, not available on the shelf.

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Hauser, Wolfgang (external)]

>Can you not just arrange for your layer to add your own machine to the
>recipe's COMPATIBLE_MACHINE definition?
>
>p.

Sure, but then I have to copy the whole files used by the recipe into my
layer, that cuts me off from the maintenance of the release.

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Phil Blundell]

On Wed, 2011-06-08 at 14:17 +0200, Hauser, Wolfgang (external) wrote:
> >Can you not just arrange for your layer to add your own machine to the
> >recipe's COMPATIBLE_MACHINE definition?
> >
> >p.
> 
> Sure, but then I have to copy the whole files used by the recipe into my
> layer, that cuts me off from the maintenance of the release.

Why's that?  I can't think of any reason why copying the recipe ought to
be necessary, and certainly not the other files that it uses. 

I guess you might not be able to append to COMPATIBLE_MACHINE from
amend.inc since amend.bbclass probably doesn't get run early enough.
But you should be able to use COMPATIBLE_MACHINE_append_pn-... in your
layer.conf, or COMPATIBLE_MACHINE += in a .bbappend file.  Are those not
working for you?

p.

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Hauser, Wolfgang (external)]

>I guess you might not be able to append to COMPATIBLE_MACHINE from
>amend.inc since amend.bbclass probably doesn't get run early enough.
>But you should be able to use COMPATIBLE_MACHINE_append_pn-... in your
>layer.conf, or COMPATIBLE_MACHINE += in a .bbappend file.  Are those
not
>working for you?

The .bbappend files don't work with bitbake version 1.10.2 which is
required by OE release 2011.03.

I want to use linux-omap-psp_2.6.32.bb as kernel recipe, how is the
exact format for COMPATIBLE_MACHINE_append_pn-... ?

I tried COMPATIBLE_MACHINE_append_linux-omap-psp = "mymachine" and
COMPATIBLE_MACHINE_append_pn-linux-omap-psp = "mymachine", both don't
work for me.

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Denys Dmytriyenko]

On Wed, Jun 08, 2011 at 05:46:19PM +0200, Hauser, Wolfgang (external) wrote:
> >I guess you might not be able to append to COMPATIBLE_MACHINE from
> >amend.inc since amend.bbclass probably doesn't get run early enough.
> >But you should be able to use COMPATIBLE_MACHINE_append_pn-... in your
> >layer.conf, or COMPATIBLE_MACHINE += in a .bbappend file.  Are those
> not
> >working for you?
> 
> The .bbappend files don't work with bitbake version 1.10.2 which is
> required by OE release 2011.03.
> 
> I want to use linux-omap-psp_2.6.32.bb as kernel recipe, how is the
> exact format for COMPATIBLE_MACHINE_append_pn-... ?
> 
> I tried COMPATIBLE_MACHINE_append_linux-omap-psp = "mymachine" and
> COMPATIBLE_MACHINE_append_pn-linux-omap-psp = "mymachine", both don't
> work for me.

COMPATIBLE_MACHINE is a regular expression, so you need to make sure the 
syntax is not broken when you append to it. In the case of linux-omap-psp, you 
can try adding "|mymachine"...

-- 
Denys

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Phil Blundell]

On Wed, 2011-06-08 at 17:46 +0200, Hauser, Wolfgang (external) wrote:
> I tried COMPATIBLE_MACHINE_append_linux-omap-psp = "mymachine" and
> COMPATIBLE_MACHINE_append_pn-linux-omap-psp = "mymachine", both don't
> work for me.

It's a regexp, so you need to do something like:

COMPATIBLE_MACHINE_append_pn-linux-omap-psp = "|mymachine"

p.

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08-06-11 17:46, Hauser, Wolfgang (external) wrote:
>> I guess you might not be able to append to COMPATIBLE_MACHINE from
>> amend.inc since amend.bbclass probably doesn't get run early enough.
>> But you should be able to use COMPATIBLE_MACHINE_append_pn-... in your
>> layer.conf, or COMPATIBLE_MACHINE += in a .bbappend file.  Are those
> not
>> working for you?
> 
> The .bbappend files don't work with bitbake version 1.10.2 which is
> required by OE release 2011.03.

Really? A default angstrom install will use bitbake 1.12.x and
2011.03-maintenances and that has been building perfectly for a while now.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN75yvMkyGM64RGpERAgudAJ0S7vkYWN+8ry/hH0Gmdkapt/jWSwCguypj
OJU3p2slcGv6ovKUtNDJhms=
=uD84
-----END PGP SIGNATURE-----

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Hauser, Wolfgang (external)]

>COMPATIBLE_MACHINE is a regular expression, so you need to make sure
the 
>syntax is not broken when you append to it. In the case of
linux-omap-psp, you 
>can try adding "|mymachine"...

Well, COMPATIBLE_MACHINE_append_pn-linux-omap-psp = "|mymachine" is the
working one.

Thanks to all, helped me getting forward.

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Hauser, Wolfgang (external)]

>Really? A default angstrom install will use bitbake 1.12.x and
>2011.03-maintenances and that has been building perfectly for a while
now.

I use the release archive as base and got errors using bitbake 1.12.0.

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Stefan Schmidt]

Hello.

On Wed, 2011-06-08 at 18:13, Hauser, Wolfgang (external) wrote:
> >Really? A default angstrom install will use bitbake 1.12.x and
> >2011.03-maintenances and that has been building perfectly for a while
> now.
> 
> I use the release archive as base and got errors using bitbake 1.12.0.

With archive you mean the release bracnh with all maintenance patches?

I recently switched our build, 2011.03 based, at BugLabs to bitbake 1.12
and did not hit a single problem. And that image contains a lot stuff
(12000 tasks).

If you are hitting a problem with 1.12 it might be worth fixing it for
2011.03. Depending on your use-case of course. What packages do you
see failing and whats your distro, etc?

regards
Stefan Schmidt

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Hauser, Wolfgang (external)]

>With archive you mean the release bracnh with all maintenance patches?

>What packages do you
>see failing and whats your distro, etc?

I took the tar file from OE git server (release-2011.03.tar.gz) and use
distribution angstom-2010x as a base for my own system.

I have to check the exact error again, that may take bit.

Regards
Wolfgang

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Stefan Schmidt]

Hello.

On Wed, 2011-06-08 at 19:02, Hauser, Wolfgang (external) wrote:
> >With archive you mean the release bracnh with all maintenance patches?
> 
> >What packages do you
> >see failing and whats your distro, etc?
> 
> I took the tar file from OE git server (release-2011.03.tar.gz) and use
> distribution angstom-2010x as a base for my own system.

OK so its the fixed release tarball without any patches we applied in
the maintenance branch.

I'm using angstrom 2008 here but I think Koen does build both distros
from 2011.03

> I have to check the exact error again, that may take bit.

No problem, take your time.

regards
Stefan Schmidt

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08-06-11 19:21, Stefan Schmidt wrote:
> Hello.
> 
> On Wed, 2011-06-08 at 19:02, Hauser, Wolfgang (external) wrote:
>>> With archive you mean the release bracnh with all maintenance patches?
>>
>>> What packages do you
>>> see failing and whats your distro, etc?
>>
>> I took the tar file from OE git server (release-2011.03.tar.gz) and use
>> distribution angstom-2010x as a base for my own system.
> 
> OK so its the fixed release tarball without any patches we applied in
> the maintenance branch.
> 
> I'm using angstrom 2008 here but I think Koen does build both distros
> from 2011.03

I built 2008 from maintenance and 2010 from dev, but philip builds 2010
from maintenance for his product, so I know that's working
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN786yMkyGM64RGpERAvHJAJ9ZAy+xjxgM8AGZgAmJ6IPPjciDZwCgrmU5
gTaaaRG6y0/yvEAKT96E2rw=
=Qnmo
-----END PGP SIGNATURE-----

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Hauser, Wolfgang (external)]

>> I have to check the exact error again, that may take bit.

It's not a problem with bitbake 1.12.0, the system (debian lenny) I have
to use to compile my system don't have python 2.6.0 installed, it uses
2.5.2 so bitbake 1.12.0 won't run. Sorry for complaining about an
"error". It was a view month ago I set up the OE environment, so I
forgot the reason why I have to use bitbake 1.10.8.

My amendment is working now, the kernel compiles and I have to test the
"metal".

thanks and regards
Wolfgang

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Stefan Schmidt]

Hello.

On Thu, 2011-06-09 at 11:42, Hauser, Wolfgang (external) wrote:
> 
> >> I have to check the exact error again, that may take bit.
> 
> It's not a problem with bitbake 1.12.0, the system (debian lenny) I have
> to use to compile my system don't have python 2.6.0 installed, it uses
> 2.5.2 so bitbake 1.12.0 won't run.

OK, that is expected.

> Sorry for complaining about an
> "error". It was a view month ago I set up the OE environment, so I
> forgot the reason why I have to use bitbake 1.10.8.

Thanks for checking.

regards
Stefan Schmidt

Re: Amend recipes which do not contain a (new) target machine in COMPATIBLE_MACHINE

[Khem Raj]

On 06/08/2011 08:46 AM, Hauser, Wolfgang (external) wrote:
>> I guess you might not be able to append to COMPATIBLE_MACHINE from
>> amend.inc since amend.bbclass probably doesn't get run early enough.
>> But you should be able to use COMPATIBLE_MACHINE_append_pn-... in your
>> layer.conf, or COMPATIBLE_MACHINE += in a .bbappend file.  Are those
> not
>> working for you?
>
> The .bbappend files don't work with bitbake version 1.10.2 which is
> required by OE release 2011.03.

is something holding you off from using later version of bitbake ?

>
> I want to use linux-omap-psp_2.6.32.bb as kernel recipe, how is the
> exact format for COMPATIBLE_MACHINE_append_pn-... ?
>
> I tried COMPATIBLE_MACHINE_append_linux-omap-psp = "mymachine" and
> COMPATIBLE_MACHINE_append_pn-linux-omap-psp = "mymachine", both don't
> work for me.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel