Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Facing problem while building Angstrom Image with help of openembedded
Date: Mon, 08 Feb 2010 09:24:25 +0100	[thread overview]
Message-ID: <hkohno$vbt$1@ger.gmane.org> (raw)
In-Reply-To: <000001caa883$7bdd6710$73983530$@in>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08-02-10 06:56, Tejas wrote:

Let's trim the log a bit:

> Resolving ftp.gnu.org... failed: Temporary failure in name resolution.
> 
> wget: unable to resolve host address `ftp.gnu.org'
> NOTE: fetch ftp://mirrors.kernel.org/gnu/coreutils/coreutils-7.2.tar.gz
> failed: Temporary failure in name resolution.
> 
> wget: unable to resolve host address `download.savannah.gnu.org'
> 
> NOTE: fetch
> http://www.angstrom-distribution.org/unstable/sources/quilt-0.46.tar.gz
> failed: Temporary failure in name resolution.
> 
> wget: unable to resolve host address `www.angstrom-distribution.org'

That is not an OE problem, that is most likely a problem with your
corporate firewall, contact your IT department to get that fixed.

There is a bug in bitbake where it doesn't honour GIT_PROXY_COMMAND, but
you shouldn't be running into that since all the git stuff for
stable/2009 is already mirrored on htttp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLb8o5MkyGM64RGpERAlfNAJ9FO1WvxJ6Baw4DXLlEok/+KKLuEgCbBVIm
zWiq1kwYJDdanQr7273TId0=
=qLSY
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2010-02-08  8:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  5:56 Facing problem while building Angstrom Image with help of openembedded Tejas
2010-02-08  6:39 ` Frans Meulenbroeks
2010-02-08  6:57   ` Tejas
2010-02-08  7:24     ` Frans Meulenbroeks
2010-02-08  8:24 ` Koen Kooi [this message]
2010-02-08 11:39   ` Tejas
2010-02-08 11:56     ` Holger Hans Peter Freyther
2010-02-08 12:52     ` Philip Balister

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='hkohno$vbt$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox