From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bad aterisk url
Date: Fri, 29 Jun 2007 10:16:06 +0200 [thread overview]
Message-ID: <20070629081606.GD8033@aon.at> (raw)
In-Reply-To: <012901c7b9cc$153b6730$ebba820a@atmel.com>
On Thu, Jun 28, 2007 at 10:53:44PM +0200, Ulf Samuelsson wrote:
>
>> wget --passive-ftp -P /home/grhuser/buildroot/dl
>> http://www.zlib.net//zlib-1.2.3.tar.bz2
>> --14:48:33-- http://www.zlib.net//zlib-1.2.3.tar.bz2
>> => `/home/grhuser/buildroot/dl/zlib-1.2.3.tar.bz2'
>> Resolving www.zlib.net... 69.73.181.135
>> Connecting to www.zlib.net|69.73.181.135|:80... failed: No route to host.
>> make: *** [/home/grhuser/buildroot/dl/zlib-1.2.3.tar.bz2] Error 1
>>
>> Checked the url myself. It is a dead link. Is there an alternative to this.
>> Searched the archives and did not find one.
>>
>http://prdownloads.sourceforge.net/libpng/zlib-1.2.3.tar.bz2
applied. Thanks!
prev parent reply other threads:[~2007-06-29 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 19:52 [Buildroot] Bad aterisk url Paul Kavan
2007-06-28 20:53 ` Ulf Samuelsson
2007-06-29 8:16 ` Bernhard Fischer [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=20070629081606.GD8033@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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