public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] binutils: update to 2.34
Date: Sun, 08 Mar 2020 11:37:47 +0000	[thread overview]
Message-ID: <D1BB7570-2020-4224-856F-86FEABC84C7C@ipfire.org> (raw)
In-Reply-To: <073c253b-ced9-e92f-2b91-ced6d1043c6b@ipfire.org>

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

Hello,

First of all, it sounds like this patch is breaking the build:

  https://lists.ipfire.org/pipermail/development/2020-March/007159.html

Secondly, you can log in to any of the ARM builders, check out the source somewhere and build it on there.

-Michael

> On 7 Mar 2020, at 10:36, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Due to missing build hardware for ARMv5 and ARM64 architecture, this patch
> updates the rootfiles for i586 and x86_64 only. I would like to ask
> somebody capable of the missing architectures to do the corresponding
> rootfile updates for me. Thank you.
> 
> Cc: Arne Fitzenreiter <arne.fitzenreiter(a)ipfire.org>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/rootfiles/common/i586/binutils   | 17 +++++++++++++++--
> config/rootfiles/common/x86_64/binutils | 17 +++++++++++++++--
> lfs/binutils                            |  6 +++---
> 3 files changed, 33 insertions(+), 7 deletions(-)
> 
> diff --git a/config/rootfiles/common/i586/binutils b/config/rootfiles/common/i586/binutils
> index 2d4f12a33..4e2014d02 100644
> --- a/config/rootfiles/common/i586/binutils
> +++ b/config/rootfiles/common/i586/binutils
> @@ -18,11 +18,24 @@ usr/bin/strings
> #usr/include/bfd.h
> #usr/include/bfd_stdint.h
> #usr/include/bfdlink.h
> +#usr/include/ctf-api.h
> +#usr/include/ctf.h
> #usr/include/diagnostics.h
> #usr/include/dis-asm.h
> #usr/include/libiberty.h
> #usr/include/plugin-api.h
> #usr/include/symcat.h
> +#usr/lib/libbfd-2.34.so
> +#usr/lib/libctf-nobfd.a
> +#usr/lib/libctf-nobfd.la
> +#usr/lib/libctf-nobfd.so
> +#usr/lib/libctf-nobfd.so.0
> +#usr/lib/libctf-nobfd.so.0.0.0
> +#usr/lib/libctf.a
> +#usr/lib/libctf.la
> +#usr/lib/libctf.so
> +#usr/lib/libctf.so.0
> +#usr/lib/libctf.so.0.0.0
> #usr/lib/ldscripts
> #usr/lib/ldscripts/elf32_x86_64.x
> #usr/lib/ldscripts/elf32_x86_64.xbn
> @@ -156,11 +169,11 @@ usr/bin/strings
> #usr/lib/ldscripts/elf_x86_64.xu
> #usr/lib/ldscripts/elf_x86_64.xw
> #usr/lib/ldscripts/elf_x86_64.xwe
> -usr/lib/libbfd-2.32.so
> +usr/lib/libbfd-2.34.so
> #usr/lib/libbfd.a
> #usr/lib/libbfd.la
> #usr/lib/libbfd.so
> -usr/lib/libopcodes-2.32.so
> +usr/lib/libopcodes-2.34.so
> #usr/lib/libopcodes.a
> #usr/lib/libopcodes.la
> #usr/lib/libopcodes.so
> diff --git a/config/rootfiles/common/x86_64/binutils b/config/rootfiles/common/x86_64/binutils
> index 2d4f12a33..4e2014d02 100644
> --- a/config/rootfiles/common/x86_64/binutils
> +++ b/config/rootfiles/common/x86_64/binutils
> @@ -18,11 +18,24 @@ usr/bin/strings
> #usr/include/bfd.h
> #usr/include/bfd_stdint.h
> #usr/include/bfdlink.h
> +#usr/include/ctf-api.h
> +#usr/include/ctf.h
> #usr/include/diagnostics.h
> #usr/include/dis-asm.h
> #usr/include/libiberty.h
> #usr/include/plugin-api.h
> #usr/include/symcat.h
> +#usr/lib/libbfd-2.34.so
> +#usr/lib/libctf-nobfd.a
> +#usr/lib/libctf-nobfd.la
> +#usr/lib/libctf-nobfd.so
> +#usr/lib/libctf-nobfd.so.0
> +#usr/lib/libctf-nobfd.so.0.0.0
> +#usr/lib/libctf.a
> +#usr/lib/libctf.la
> +#usr/lib/libctf.so
> +#usr/lib/libctf.so.0
> +#usr/lib/libctf.so.0.0.0
> #usr/lib/ldscripts
> #usr/lib/ldscripts/elf32_x86_64.x
> #usr/lib/ldscripts/elf32_x86_64.xbn
> @@ -156,11 +169,11 @@ usr/bin/strings
> #usr/lib/ldscripts/elf_x86_64.xu
> #usr/lib/ldscripts/elf_x86_64.xw
> #usr/lib/ldscripts/elf_x86_64.xwe
> -usr/lib/libbfd-2.32.so
> +usr/lib/libbfd-2.34.so
> #usr/lib/libbfd.a
> #usr/lib/libbfd.la
> #usr/lib/libbfd.so
> -usr/lib/libopcodes-2.32.so
> +usr/lib/libopcodes-2.34.so
> #usr/lib/libopcodes.a
> #usr/lib/libopcodes.la
> #usr/lib/libopcodes.so
> diff --git a/lfs/binutils b/lfs/binutils
> index 7df005146..334adad25 100644
> --- a/lfs/binutils
> +++ b/lfs/binutils
> @@ -1,7 +1,7 @@
> ###############################################################################
> #                                                                             #
> # IPFire.org - A linux based firewall                                         #
> -# Copyright (C) 2007-2017  IPFire Team  <info(a)ipfire.org>                     #
> +# Copyright (C) 2007-2020  IPFire Team  <info(a)ipfire.org>                     #
> #                                                                             #
> # This program is free software: you can redistribute it and/or modify        #
> # it under the terms of the GNU General Public License as published by        #
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 2.32
> +VER        = 2.34
> 
> THISAPP    = binutils-$(VER)
> DL_FILE    = $(THISAPP).tar.xz
> @@ -94,7 +94,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = 0d174cdaf85721c5723bf52355be41e6
> +$(DL_FILE)_MD5 = 664ec3a2df7805ed3464639aaae332d6
> 
> install : $(TARGET)
> 
> -- 
> 2.16.4


  reply	other threads:[~2020-03-08 11:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07 10:36 Peter Müller
2020-03-08 11:37 ` Michael Tremer [this message]
2020-03-20 13:37 ` [PATCH v2 1/2] cairo: Update to 1.16.0 Michael Tremer
2020-03-20 13:37   ` [PATCH v2 2/2] binutils: update to 2.34 Michael Tremer
2020-03-20 17:21   ` [PATCH v2 1/2] cairo: Update to 1.16.0 Peter Müller

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=D1BB7570-2020-4224-856F-86FEABC84C7C@ipfire.org \
    --to=michael.tremer@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