From: Holger Sunke <holger.sunke@posteo.de>
To: development@lists.ipfire.org
Subject: Fwd: [PATCH 1/2] Added i586/386 support for GO language required for node_exporter.
Date: Fri, 07 May 2021 17:39:26 +0000 [thread overview]
Message-ID: <bcf8ab38-337f-5204-b639-05bfa69d0b9f@posteo.de> (raw)
In-Reply-To: <23a003ef-a311-b758-7fd5-1afb6a2f6252@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]
Am 06.05.21 um 22:26 schrieb Adolf Belka:
> Hi Holger,
>
> On 06/05/2021 21:46, Holger Sunke wrote:
>> ---
>> lfs/Config | 4 ++++
>> lfs/go | 6 +++---
>> 2 files changed, 7 insertions(+), 3 deletions(-)
>>
>> diff --git a/lfs/Config b/lfs/Config
>> index eadbbc408..4d0f2f00b 100644
>> --- a/lfs/Config
>> +++ b/lfs/Config
>> @@ -138,6 +138,10 @@ ifeq "$(BUILD_ARCH)" "aarch64"
>> GOARCH = arm64
>> endif
>> +ifeq "$(BUILD_ARCH)" "i586"
>> + GOARCH = 386
>> +endif
>> +
>
> A question I would have here is if creating this package in i586
> architecture makes sense when in 7 months the i586 version of IPFire
> will have reached End Of Life and will no longer be updated.
>
> Regards,
>
> Adolf
I now remember having red about this but I forgot that fact and I even
believed my device is a 32bit one. Luckily it is x86_64 ...
So on the one hand we can drop this, or expand support for all
architecutres supported by ipfire now and in the longer future.
Kind regards
Holger
>
>>
>> ###############################################################################
>>
>> # Common Macro Definitions
>>
>> ###############################################################################
>>
>> diff --git a/lfs/go b/lfs/go
>> index 6ebb37080..97effcb84 100644
>> --- a/lfs/go
>> +++ b/lfs/go
>> @@ -28,10 +28,9 @@ VER = 1.15.4
>> THISAPP = go-$(VER)
>> DL_FILE = go$(VER).$(GOOS)-$(GOARCH).tar.gz
>> -DL_FROM = $(URL_IPFIRE)
>> +DL_FROM = https://golang.org/dl/
>> DIR_APP = $(DIR_SRC)/go
>> TARGET = $(DIR_INFO)/$(THISAPP)
>> -SUP_ARCH = x86_64
>>
>> ###############################################################################
>>
>> # Top-level Rules
>> @@ -41,7 +40,8 @@ objects = $(DL_FILE)
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>> -$(DL_FILE)_MD5 = 8e9d11a16f03372c82c5134278a0bd7d
>> +go$(VER).$(GOOS)-amd64.tar.gz_MD5 = 8e9d11a16f03372c82c5134278a0bd7d
>> +go$(VER).$(GOOS)-386.tar.gz_MD5 = 8d1c3539c88710273f61b0c810b7448c
>> install : $(TARGET)
parent reply other threads:[~2021-05-07 17:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <23a003ef-a311-b758-7fd5-1afb6a2f6252@posteo.de>]
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=bcf8ab38-337f-5204-b639-05bfa69d0b9f@posteo.de \
--to=holger.sunke@posteo.de \
--cc=development@lists.ipfire.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