From: Enrico Castro <castroenrico@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: ti-codec-engine_2.23.bb failed
Date: Wed, 27 May 2009 17:24:15 +0200 [thread overview]
Message-ID: <4A1D5B1F.4060608@gmail.com> (raw)
I build ti-codec-engine_2.23.bb, but the source codec_engine_2_23_01.tar.gz did not found in
www.angstrom-distribution.org
NOTE: Running task 1786 of 5760 (ID: 475,
/home/enrico/oe/openembedded/recipes/dsplink/ti-codec-engine_2.23.bb, do_fetch)
NOTE: fetch http://install.tarball.in.source.dir/codec_engine_2_23_01.tar.gz
--16:48:23-- http://install.tarball.in.source.dir/codec_engine_2_23_01.tar.gz
=> `/home/enrico/oe/tmp/downloads/codec_engine_2_23_01.tar.gz'
Resolving install.tarball.in.source.dir... failed: Name or service not known.
NOTE: fetch http://www.angstrom-distribution.org/unstable/sources/codec_engine_2_23_01.tar.gz
--16:48:23-- http://www.angstrom-distribution.org/unstable/sources/codec_engine_2_23_01.tar.gz
=> `/home/enrico/oe/tmp/downloads/codec_engine_2_23_01.tar.gz'
Resolving www.angstrom-distribution.org... 85.214.40.226
Connecting to www.angstrom-distribution.org|85.214.40.226|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
16:48:36 ERROR 404: Not Found.
NOTE: Task failed: Fetch failed: http://install.tarball.in.source.dir/codec_engine_2_23_01.tar.gz
ERROR: TaskFailed event exception, aborting
ERROR: Build of /home/enrico/oe/openembedded/recipes/dsplink/ti-codec-engine_2.23.bb do_fetch failed
ERROR: Task 475 (/home/enrico/oe/openembedded/recipes/dsplink/ti-codec-engine_2.23.bb, do_fetch) failed
NOTE: Tasks Summary: Attempted 1785 tasks of which 1785 didn't need to be rerun and 1 failed.
ERROR: '/home/enrico/oe/openembedded/recipes/dsplink/ti-codec-engine_2.23.bb' failed
Regards,
Enrico
next reply other threads:[~2009-05-27 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 15:24 Enrico Castro [this message]
2009-05-27 15:30 ` ti-codec-engine_2.23.bb failed Philip Balister
2009-05-28 15:16 ` Enrico Castro
2009-05-28 15:34 ` Philip Balister
2009-05-27 18:30 ` Denys Dmytriyenko
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=4A1D5B1F.4060608@gmail.com \
--to=castroenrico@gmail.com \
--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.