All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: SRC_URI points to local domain:
Date: Thu, 24 Nov 2011 04:09:01 -0700	[thread overview]
Message-ID: <4ECE25CD.9090105@mlbassoc.com> (raw)
In-Reply-To: <4ECDFB92.10203@ts.fujitsu.com>

On 2011-11-24 01:08, Rainer Koenig wrote:
> Hi,
>
> just tried to integrate ti-syslink in my build, but that pulls ti-cgt6x
> in and that can't fetch. Reason:
>
> $ find -type f | xargs grep SRC_URI | grep "local/"
> ./recipes-ti/hdvpss/ti-hdvpss.inc:SRC_URI =
> "http://install.source.dir.local/REL.HDVPSS.${PV}.zip"
> ./recipes-ti/devtools/ti-cgt6x.inc:SRC_URI =
> "http://install.source.dir.local/ti_cgt_c6000_${PVwithdots}_setup_linux_x86.bin;name=cgt6xbin"
> ./recipes-ti/devtools/ti-cgt470.inc:SRC_URI =
> "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin"
>
> So we have 3 recipes that won't fetch. Root cause seems that you need to
> get approved when downloading cgt6x from the TI website. Any hope that
> this will change? Or do I need to setup my own local storage as well and
> change the recipes?

Fetch the files yourself and place in your [local] downloads directory (DL_DIR)
No need to change the recipe as OE will look there first.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2011-11-24 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24  8:08 SRC_URI points to local domain: Rainer Koenig
2011-11-24 11:09 ` Gary Thomas [this message]
2011-11-24 11:37   ` Rainer Koenig
2011-11-24 11:47     ` Gary Thomas
2011-11-24 16:48     ` Koen Kooi

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=4ECE25CD.9090105@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=Rainer.Koenig@ts.fujitsu.com \
    --cc=meta-ti@yoctoproject.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.