[Buildroot] [PATCH RFC] package/glibc: switch to using the maintenance branch

Romain Naour romain.naour at gmail.com
Sun Oct 22 15:16:21 UTC 2017


Hi Yann, All,

Le 21/10/2017 à 15:12, Romain Naour a écrit :
> Hi Yann, All,
> 
> Le 21/10/2017 à 14:22, Yann E. MORIN a écrit :
>> Romain, All,
>>
>> On 2017-10-21 13:31 +0200, Romain Naour spake thusly:
>>> Le 21/10/2017 à 12:22, Yann E. MORIN a écrit :

[...]

>>>> The version number is obtained with:
>>>>     $ git describe --match 'glibc-*' --abbrev=40 origin/release/2.26/master
>>>>
>>>> The alternative options were:
>>>>   - download the tarball from the git tree
>>>>     --> does nto work; not an option
>>>>   - download the 2.26 tarball, and bundle the individual patches in
>>>>     Buildroot
>>>>     --> maintenance of patches is a burden; not an option
>>>>   - download the 2.26 tarball, maintain the list of patches to download from
>>>>     the git tree
>>>>     --> not an option for the same reason
>>>>
>>>> So we end up just doing a git clone. The git tree is today about ten
>>>> times the size of the tarball, so a rough estimate makes it at about ten
>>>> times the download time.
>>>
>>> I can't clone this repo from here using https:
>>>
>>> error: Unable to get pack index
>>> https://sourceware.org/git/glibc.git/objects/pack/pack-f7640727c0f4d6c3389f46d7d6540bbd74f2c136.idx
>>> error: Failed to connect to sourceware.org port 443: Connection timed out
>>> (curl_result = 7, http_code = 0, sha1 = eb4488dc33fedcd7cdb5907a82f18f1d300d533b)
>>> error: Unable to find a1fd1e8a3e17d0f846df142d93aa2af0bc16ced0 under
>>> https://sourceware.org/git/glibc.git
>>
>> As seen on IRC, you've solved your issue, right?
> 
> Right, the build succeed here.

It seems that using https://sourceware.org/git/glibc.git is not a reliable.
The https connection timeout most of the time.
A lot of build has been broken in my gitlab when I was testing the
toolchain-builder infra.

Since git:// can't be used behind a proxy, we have no choice but use
http://sourceware.org/git/glibc.git

Best regards,
Romain

> 
>>
>> Regards,
>> Yann E. MORIN.
>>



More information about the buildroot mailing list