From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Creating a Own Tool chain, some referenced packages are not included into the SDK archive
Date: Thu, 08 Jul 2010 19:11:44 +0200 [thread overview]
Message-ID: <i150sg$mjh$1@dough.gmane.org> (raw)
In-Reply-To: <0B51A1E7C61D114DAE6FC10B0FD0ABA501819D67@deimsg40.de.net.world>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08-07-10 17:22, Hauser, Wolfgang (external) wrote:
> Hello, I have found the problems of creating the toolchain meta-toolchain-qte.bb (and my derived one) !
>
> First problem:
>
> There is a conflict in packages "cups" and "libpam-base-files" (same file "cups" in "/etc/pam.d" was deployed by the packages) this results in a bailing out while installing the packages.
>
> My workaround was: local modified libpam-base-files w/o file "cups" in "libpam-base-files/pam.d"
> (does libpam-base-files really have to install this file and some other package dependent ones ?)
Fixed:
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=81467a049f275dde815b000e25b704e9140c2440
> Second problem:
> meta-toolchain-qte.bb contains following line in do_populate_sdk_append():
>
> >script = "${SDK_OUTPUT}/${SDKPATH}/environment-setup"<
>
> this have to be changed to:
>
> >script="${SDK_OUTPUT}/${SDKPATH}/environment-setup"<
>
> because the code is used as shell commands and not as python code !
>
> The issue above results in a call of "script" with arguments "=" and "${SDK_OUTPUT}/${SDKPATH}/environment-setup".
> "script" opens a "bash -i" and wait for commands. Therefore the processing blocks until this shell exits.
Fixed:
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=479ea460e4fbacd00f26a8903427e674a3b7501f
>
> Is there somebody out there having commit access who will fix that second problem in org.openembedded.dev ?
Sure :) Thanks for finding out these bugs!
>
> regards
> Wolfgang Hauser
>
> -----Ursprüngliche Nachricht-----
> Von: openembedded-devel-bounces@lists.openembedded.org [mailto:openembedded-devel-bounces@lists.openembedded.org] Im Auftrag von Holger Freyther
> Gesendet: Donnerstag, 1. Juli 2010 14:51
> An: openembedded-devel@lists.openembedded.org
> Betreff: Re: [oe] Creating a Own Tool chain, some referenced packages are not included into the SDK archive
>
> On 06/29/2010 11:20 PM, Hauser, Wolfgang (external) wrote:
>> Hello Holger Freyther,
>>
>> here are the diffs for my changes:
>>
>> diff of meta-toolchain-qte.bb <> meta-toolchain-xxx.bb
>
> sorry, this diff is not readable, please use a unified diff for the changes.
>
>>
>> The qte toolchain has created properly, my own do not.
>
> So you say bitbake meta-toolchain-qte is working?
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMNgbQMkyGM64RGpERAuenAJ4r9q5woSg6tZXCB9lPRAHgkGHpogCfZygX
9Ei0MyIj9zB/pNp+F9ik978=
=LLyA
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-07-09 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 14:04 Creating a Own Tool chain, some referenced packages are not included into the SDK archive Hauser, Wolfgang (external)
2010-06-29 14:48 ` Holger Freyther
2010-06-29 15:20 ` Hauser, Wolfgang (external)
2010-07-01 12:50 ` Holger Freyther
2010-07-01 13:00 ` Hauser, Wolfgang (external)
2010-07-01 14:07 ` Hauser, Wolfgang (external)
2010-07-08 15:22 ` Hauser, Wolfgang (external)
2010-07-08 16:55 ` Denys Dmytriyenko
2010-07-09 10:08 ` Hauser, Wolfgang (external)
2010-07-08 17:11 ` Koen Kooi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='i150sg$mjh$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.