From: Tasslehoff Kjappfot <tasskjapp@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Workaround to compile linux-omap_2.6.39.bb?
Date: Wed, 5 Oct 2011 22:31:23 +0200 [thread overview]
Message-ID: <7A8ADFF6-FC88-49F4-97DD-AEFD5FBFC434@gmail.com> (raw)
In-Reply-To: <1317814733.14671.139.camel@ted>
> OE-Core uses fetch2 and that is a tarball from fetch1. You'd need to
> convert that tarball into the form that fetch2 expects and rename it,
> then you stand some chance of it working.
>
> Also note that your recipes needs to be using a fixed source revision
> and that revision needs to be present in that tarball.
>
Thanks for the response, but I managed to find a mirror of linux-omap in the end, and I think I read on the linux-omap ML that the tmlind-repos will be back at kernel.org soon.
- Tasslehoff
prev parent reply other threads:[~2011-10-05 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 10:48 Workaround to compile linux-omap_2.6.39.bb? Tasslehoff Kjappfot
2011-10-05 11:38 ` Richard Purdie
2011-10-05 20:31 ` Tasslehoff Kjappfot [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=7A8ADFF6-FC88-49F4-97DD-AEFD5FBFC434@gmail.com \
--to=tasskjapp@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox