From: Klaus Schwarzkopf <schwarzkopf@sensortherm.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: buildserver
Date: Sat, 20 Nov 2010 14:29:47 +0100 [thread overview]
Message-ID: <4CE7CD4B.2030804@sensortherm.de> (raw)
In-Reply-To: <ic5k25$ksc$2@dough.gmane.org>
Hi,
i think, ti and oe make a great job and i love the framework!!!
But the ti-codecs-dm355_3.10.00.00.bb don't work on my machine.
Could it be, that the autobuilder doesn't clean the download and temp
directory?
I can also have a misconfiguration!
Greetings
Klaus
Am 19.11.2010 11:37, schrieb Koen Kooi:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 19-11-10 10:46, Klaus Schwarzkopf wrote:
>> Hi,
>>
>> i have some problems with the ti recipes, see my emails on the list.
>>
>> The two problems are:
>> * the recipes are out of date and don't work.
>
> Why do you say that? They are currently tracking the state of the
> unreleased upcoming SDK, so from a TI POV they are from the future!
> Furthermore, they all build and work. An autobuilder builds them for all
> TI boards multiple times per day and tinderbox is all green.
> And on the boards we test, the resulting packages work.
>
>> * the recipes can't download the source files.
>
> Read the recipes, not all sources can be downloaded with wget, some
> require certification.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFM5lOFMkyGM64RGpERAqWbAJ0a8vPcNVIo8WI/V3Yf/MdEGofS3ACeLbQJ
> vimYfl63vA/AAWPLik6M7OM=
> =wlhc
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-11-20 13:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 9:46 buildserver Klaus Schwarzkopf
2010-11-19 10:37 ` buildserver Koen Kooi
2010-11-19 11:48 ` buildserver Klaus Schwarzkopf
2010-11-20 13:29 ` Klaus Schwarzkopf [this message]
2010-11-19 10:42 ` buildserver Yury Bushmelev
2010-11-19 11:24 ` buildserver Martin Jansa
2010-11-19 12:21 ` buildserver Frans Meulenbroeks
2010-11-19 11:55 ` buildserver Klaus Schwarzkopf
2010-11-19 12:04 ` buildserver Dvorkin Dmitry
2010-11-20 13:49 ` buildserver Klaus Schwarzkopf
2010-11-21 18:08 ` buildserver Chris Larson
2010-11-22 8:38 ` buildserver Klaus Schwarzkopf
2010-11-22 8:56 ` buildserver Frans Meulenbroeks
2010-11-22 15:14 ` buildserver Klaus Schwarzkopf
2010-11-22 17:25 ` buildserver Frans Meulenbroeks
2010-11-22 17:31 ` buildserver Eric Bénard
2010-11-22 18:21 ` buildserver Frans Meulenbroeks
2010-11-22 18:41 ` buildserver Eric Bénard
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=4CE7CD4B.2030804@sensortherm.de \
--to=schwarzkopf@sensortherm.de \
--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.