You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Jun He (Jira)" <ji...@apache.org> on 2019/11/25 07:29:00 UTC
[jira] [Updated] (BIGTOP-3274) Protocbuf build failed due to
git.savannah.gnu.org is not accessible
[ https://issues.apache.org/jira/browse/BIGTOP-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun He updated BIGTOP-3274:
---------------------------
Description:
In BIGTOP-2698, protocbuf is set to build from source with patche and new config.guess from git.savannah.gnu.org.
Recently when I was trying to build toolchain, I noticed that confgi.guess was failed to download due to git.savannah.gnu.org was not accessible.
To fix this I think we can use a included config.guess, just like the patch (_0001-Add-generic-GCC-support-for-atomic-operations.patch_), instead of downloading it every time. This will minimize failure due to network issue and keep a consistent file for the given v2.5 protocbuf
was:
In BIGTOP-2698, protocbuf is set to build from source with patche and new config.guess from git.savannah.gnu.org.
Recently when I was trying to build toolchain locally, I noticed that confgi.guess was failed to download due to git.savannah.gnu.org was not accessible.
To fix this I think we can use a included config.guess, just like the patch (0001-Add-generic-GCC-support-for-atomic-operations.patch), instead of downloading it every time.
> Protocbuf build failed due to git.savannah.gnu.org is not accessible
> --------------------------------------------------------------------
>
> Key: BIGTOP-3274
> URL: https://issues.apache.org/jira/browse/BIGTOP-3274
> Project: Bigtop
> Issue Type: Bug
> Reporter: Jun He
> Priority: Major
>
> In BIGTOP-2698, protocbuf is set to build from source with patche and new config.guess from git.savannah.gnu.org.
> Recently when I was trying to build toolchain, I noticed that confgi.guess was failed to download due to git.savannah.gnu.org was not accessible.
> To fix this I think we can use a included config.guess, just like the patch (_0001-Add-generic-GCC-support-for-atomic-operations.patch_), instead of downloading it every time. This will minimize failure due to network issue and keep a consistent file for the given v2.5 protocbuf
--
This message was sent by Atlassian Jira
(v8.3.4#803005)