public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] Added i586/386 support for GO language required for node_exporter.
Date: Thu, 06 May 2021 22:26:46 +0200	[thread overview]
Message-ID: <96ac7a19-8221-ca7c-a7db-3d7a14101bfe@ipfire.org> (raw)
In-Reply-To: <20210506194616.2972714-2-holger.sunke@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]

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

>   ###############################################################################
>   # 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)
>   

  reply	other threads:[~2021-05-06 20:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 19:46 [PATCH 0/2] Added new Package node_exporter Holger Sunke
2021-05-06 19:46 ` [PATCH 1/2] Added i586/386 support for GO language required for node_exporter Holger Sunke
2021-05-06 20:26   ` Adolf Belka [this message]
2021-05-07 11:28   ` Michael Tremer
2021-05-07 18:19     ` Holger Sunke
2021-05-11  9:53       ` Michael Tremer
2021-05-21  8:56         ` Holger Sunke
2021-05-21  8:59           ` Michael Tremer
2021-05-06 19:46 ` [PATCH 2/2] Added new node_exporter package Holger Sunke
2021-05-06 20:58   ` Adolf Belka
2021-05-06 20:43 ` [PATCH 0/2] Added new Package node_exporter Adolf Belka
2021-05-07 18:05   ` Holger Sunke
2021-05-24 20:45     ` Robin Roevens

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=96ac7a19-8221-ca7c-a7db-3d7a14101bfe@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --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