public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/dtc: bump version to 1.6.0
Date: Sun, 19 Apr 2020 22:50:03 +0200	[thread overview]
Message-ID: <20200419205003.GC5035@scaer> (raw)
In-Reply-To: <20200419154300.203136-1-juju@cotds.org>

Julien, All,

On 2020-04-19 17:43 +0200, Julien Olivain spake thusly:
> When host compiler is gcc 10 (for example on Fedora 32), dtc 1.5.1
> fail to build with the error:
> /usr/bin/ld: dtc-parser.tab.o:(.bss+0x20): multiple definition of `yylloc'; dtc-lexer.lex.o:(.bss+0x0): first defined here
> collect2: error: ld returned 1 exit status
> 
> dtc 1.6.0 fixes this issue in the commit:
> https://git.kernel.org/pub/scm/utils/dtc/dtc.git/commit/?id=0e9225eb0dfec51def612b928d2f1836b092bc7e
> 
> Also adopt new spacing convention in .hash files (two spaces).

Thanks for the spaces! ;-)

> Signed-off-by: Julien Olivain <juju@cotds.org>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/dtc/dtc.hash | 8 ++++----
>  package/dtc/dtc.mk   | 2 +-
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/package/dtc/dtc.hash b/package/dtc/dtc.hash
> index e4d6c02544..902ce1baf9 100644
> --- a/package/dtc/dtc.hash
> +++ b/package/dtc/dtc.hash
> @@ -1,7 +1,7 @@
>  # from https://www.kernel.org/pub/software/utils/dtc/sha256sums.asc
> -sha256 660b74039690fc37013660544d09191834efb58503c73c555c5513ba75ab031f  dtc-1.5.1.tar.xz
> +sha256  10503b0217e1b07933e29e8d347a00015b2431bea5f59afe0bed3af30340c82d  dtc-1.6.0.tar.xz
>  
>  # Hash for license files
> -sha256 78e1e1ce5728a990d59c7de61d4741c49185d5129daf783b386380a214328d68  README.license
> -sha256 8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643  GPL
> -sha256 6313108c23efffa36948f8b2cff1560a5935373b527b0e1a837cc77e6ed1bacd  BSD-2-Clause
> +sha256  78e1e1ce5728a990d59c7de61d4741c49185d5129daf783b386380a214328d68  README.license
> +sha256  8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643  GPL
> +sha256  6313108c23efffa36948f8b2cff1560a5935373b527b0e1a837cc77e6ed1bacd  BSD-2-Clause
> diff --git a/package/dtc/dtc.mk b/package/dtc/dtc.mk
> index d532487dd1..956a60b29d 100644
> --- a/package/dtc/dtc.mk
> +++ b/package/dtc/dtc.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -DTC_VERSION = 1.5.1
> +DTC_VERSION = 1.6.0
>  DTC_SOURCE = dtc-$(DTC_VERSION).tar.xz
>  DTC_SITE = https://www.kernel.org/pub/software/utils/dtc
>  DTC_LICENSE = GPL-2.0+ or BSD-2-Clause (library)
> -- 
> 2.26.0
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2020-04-19 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 15:43 [Buildroot] [PATCH 1/1] package/dtc: bump version to 1.6.0 Julien Olivain
2020-04-19 20:50 ` Yann E. MORIN [this message]
2020-06-02  7:05 ` Peter Korsgaard

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=20200419205003.GC5035@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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