From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_SOURCEFORGE_MIRROR issue in package .mk files
Date: Tue, 21 Aug 2012 23:55:52 +0300 [thread overview]
Message-ID: <5033F5D8.2090706@petroprogram.com> (raw)
In-Reply-To: <201208212204.55029.yann.morin.1998@free.fr>
21.8.2012 23:04, Yann E. MORIN kirjoitti:
> Aras, Stefan, All,
>
> On Tuesday 21 August 2012 20:29:43 Stefan Fr?berg wrote:
>> 21.8.2012 20:07, Stefan Fr?berg kirjoitti:
>>> 21.8.2012 18:51, Aras Vaichas kirjoitti:
>>>> I was rebuilding my Buildroot when I noticed that the
>>>> kent.dl.sourceforge.net mirror is down and my build fails.
> [--SNIP--]
>> It seems that it is possible to let sourceforge pick the right mirror
>> automatically with wget
>> wget
>> http://sourceforge.net/projects/boost/files/boost/1.49.0/boost_1_49_0.tar.bz2/download
>>
>> and it produced something like this:
>>
>> --2012-08-21 21:21:40--
>> http://sourceforge.net/projects/boost/files/boost/1.49.0/boost_1_49_0.tar.bz2/download
>> Resolving sourceforge.net... 216.34.181.60
>> Connecting to sourceforge.net|216.34.181.60|:80... connected.
>> HTTP request sent, awaiting response... 302 Found
>> Location:
>> http://downloads.sourceforge.net/project/boost/boost/1.49.0/boost_1_49_0.tar.bz2?r=&ts=1345573301&use_mirror=garr
> ^^^^^^^^^
>> [following]
> [--SNIP--]
>
>> So automatic sourceforge mirror selection should be trivial to do if all
>> the other sourceforge packages also follow the same syntax:
>> http://sourceforge.net/projects/${PACKAGE_NAME}/files/${PACKAGE_NAME}/${PACKAGE_VERSION}/${PACKAGE_FILENAME}/download
> Well, to avoid one 302-redirect, it's possible to directly use their mirror
> selection mechanism. For boost, that'd simply be:
>
> $ wget http://downloads.sourceforge.net/project/boost/boost/1.49.0/boost_1_49_0.tar.bz2
>
> --2012-08-21 21:52:21-- http://downloads.sourceforge.net/project/boost/boost/1.49.0/boost_1_49_0.tar.bz2
> Resolving downloads.sourceforge.net... 216.34.181.59
> Connecting to downloads.sourceforge.net|216.34.181.59|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: http://ignum.dl.sourceforge.net/project/boost/boost/1.49.0/boost_1_49_0.tar.bz2 [following]
> --2012-08-21 21:52:21-- http://ignum.dl.sourceforge.net/project/boost/boost/1.49.0/boost_1_49_0.tar.bz2
> Resolving ignum.dl.sourceforge.net... 62.109.128.11, 2001:1ab0:7e1f:1:230:48ff:fed1:9c0a
> Connecting to ignum.dl.sourceforge.net|62.109.128.11|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 48499961 (46M) [application/x-bzip2]
> Saving to: ?boost_1_49_0.tar.bz2?
> [--SNIP--]
>
> In buildroot, it could be written thus:
> BOOST_SITE = sf://boost/boost/$(BOOST_VERSION)
>
> with 'sf://' automatically turned by the pkg-infa into the canonical SF
> download base URL:
> http://downloads.sourceforge.net/project/
>
> and thus giving the full URL:
> http://downloads.sourceforge.net/project/boost/boost/$(BOOST_VERSION)/$(BOOST_SOURCE)
Thank you!
That sf:// thing did not work for me but I tried this with libpng and
changed LIBPNG_SITE to:
LIBPNG_SITE =
http://downloads.sourceforge.net/project/libpng/libpng${LIBPNG_SERIES}/${LIBPNG_VERSION}
And when I run "make source" it gives:
--2012-08-21 23:46:14--
http://downloads.sourceforge.net/project/libpng/libpng14/1.4.12/libpng-1.4.12.tar.bz2
Resolving downloads.sourceforge.net... 216.34.181.59
Connecting to downloads.sourceforge.net|216.34.181.59|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location:
http://garr.dl.sourceforge.net/project/libpng/libpng14/1.4.12/libpng-1.4.12.tar.bz2
[following]
--2012-08-21 23:46:15--
http://garr.dl.sourceforge.net/project/libpng/libpng14/1.4.12/libpng-1.4.12.tar.bz2
Resolving garr.dl.sourceforge.net... 193.206.140.34, 2001:760:ffff:b0::34
Connecting to garr.dl.sourceforge.net|193.206.140.34|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 652462 (637K) [application/octet-stream]
Saving to: `/work/buildroot/dl/libpng-1.4.12.tar.bz2.tmp'
0K .......... .......... .......... .......... .......... 7% 177K 3s
50K .......... .......... .......... .......... .......... 15% 341K 2s
100K .......... .......... .......... .......... .......... 23% 368K 2s
150K .......... .......... .......... .......... .......... 31% 523K 1s
Works nicely ! :-)
So that BR2_SOURCEFORGE_MIRROR variable could be now (unless somebody
really want's to force mirror) considered deprecated ?
Thanks again!
Stefan
> Regards,
> Yann E. MORIN.
>
next prev parent reply other threads:[~2012-08-21 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 15:51 [Buildroot] BR2_SOURCEFORGE_MIRROR issue in package .mk files Aras Vaichas
2012-08-21 16:59 ` Yann E. MORIN
2012-08-21 17:07 ` Stefan Fröberg
2012-08-21 18:29 ` Stefan Fröberg
2012-08-21 20:04 ` Yann E. MORIN
2012-08-21 20:55 ` Stefan Fröberg [this message]
2012-08-21 21:17 ` Yann E. MORIN
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=5033F5D8.2090706@petroprogram.com \
--to=stefan.froberg@petroprogram.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