72 replies to this topic

[littlesat]

Here: http://openpli.pli-images.org/ you can find everything about building your own openpli image...

[xener]

thecount mean that there is no specific makefile for upcoming openpli-2.0 .. at last he`s not the only one who can`t find that file :-) there`s only makefile for present version,
which need some changes to make it work with v2.0 .
for example
GIT_BRANCH (master -> 2.0-pre13
BB_BRANCH (1.4.2-git -> ???)
BBFILES (packages -> recipes)
may be DISTRO ( cant remember right now if and what else)

[pieterg]

bb 1.10 is required

[MiLo]

If I can find the time, I'll cook up a makefile for OE 2.0 this weekend. It's something I've been planning to do for a long time, but never quite got to it.

[xener]

bb 1.10 is required

need to download it from http://developer.ber...rojects/bitbake ,
opendreambox end up with v1.8

[pieterg]

http://git.openembed...it.cgi/bitbake/

[MiLo]

I put together a makefile for 2.0 development, you'll find it on the Wiki page:

http://openpli.pli-i...enembeddedBuild

(it's attached to the page, and under the link in the text)

The makefile will fetch the correct OE branch and download and compile Bitbake 1.10.

[Sjaaky]

Als ik niet ingelogd ben:

ATTACHMENT_VIEW privileges are required to perform this operation on Attachment 'Makefile-openembedded-openpli2' in OpenembeddedBuild

Nu dacht ik admin rechten te hebben zodat ik privileges aan kan passen. Maar dat vind ik nu nergens meer terug. Kan ook zijn dat ik die rechten toen aan kon passen omdat ik toen de maker/eigenaar was.

De makefile zelf ziet er wel goed uit.

[xener]

i think its a time to remove -pre13 suffix :-) master is 1.0 , when 2.0 become stable, just switch current master to 1.0 and current 2.0 to master.

[WanWizard]

ATTACHMENT_VIEW privileges are required to perform this operation on Attachment 'Makefile-openembedded-openpli2' in OpenembeddedBuild

Fixed. The attachment is now public.

[pieterg]

i think its a time to remove -pre13 suffix :-) master is 1.0 , when 2.0 become stable, just switch current master to 1.0 and current 2.0 to master.

-pre13 simply means you might expect more rebasing

[connect]

My error OE2.0

NOTE: Handling BitBake files: \ (7233/7233) [100 %]
NOTE: Parsing finished. 6420 cached, 474 parsed, 339 skipped, 2 masked.
ERROR: Openembedded's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:

Please install following missing utilities: chrpath
Using dash as /bin/sh causes various subtle build problems, please use bash instead.

make: *** [image] Error 1

[pieterg]

so it might be best to follow that advice...

[MiLo]

Just do what it asks.

Install chrpath (ubuntu 10 has it, but 9 does not)

And fix the shell thing. Just google for the message to get a clean way to do this.

[connect]

Is vuduo and solo works oe2?

[connect]

Ubuntu 9

ERROR: Openembedded's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:

Using dash as /bin/sh causes various subtle build problems, please use bash instead.

[connect]

New Error OE2 :

export PATH
export LD_LIBRARY_PATH=
export LANG=C
export CVS_RSH=ssh
umask 0022
git clone -b 1.10 git://git.openembedded.net/bitbake
error: unknown switch `b'
usage: git clone [options] [--] <repo> [<dir>]

-q, --quiet be quiet
-v, --verbose be verbose
-n, --no-checkout don't create a checkout
--bare create a bare repository
--naked create a bare repository
--mirror create a mirror repository (implies bare)
-l, --local to clone from a local repository
--no-hardlinks don't use local hardlinks, always copy
-s, --shared setup as shared repository
--template <path> path the template repository
--reference <repo> reference repository
-o, --origin <branch>
use <branch> instead of 'origin' to track upstream
-u, --upload-pack <path>
path to git-upload-pack on the remote
--depth <depth> create a shallow clone of that depth

make: *** [bitbake] Błąd 129

[xener]

--branch <name>, -b <name>
Instead of pointing the newly created HEAD to the branch pointed to by the cloned repository's HEAD, point to <name> branch instead. In a non-bare repository,
this is the branch that will be checked out.

[MiLo]

Probably your GIT version is too old, upgrade it.

[connect]

Yes actualization git 1.7 and it is ok .