Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/dieharder: fix build with gcc 10
Date: Thu, 20 Aug 2020 22:35:07 +0200	[thread overview]
Message-ID: <20200820203507.GA17579@scaer> (raw)
In-Reply-To: <20200820062118.GA32195@vdg.name>

Julien, All,

On 2020-08-20 08:21 +0200, Julien Viard de Galbert spake thusly:
[--SNIP--]
> As I introduced the package a few years ago, I was wondering if we had a
> way to measure the usage of this package and think about removing it.
> Then I checked with the guardians of the temple aka debian and found
> that the maintainer probably fixed the gcc 10 issue:
> 
> | dieharder (3.31.1.2-1) unstable; urgency=medium
> |
> |   * New upstream minor release accomodating gcc-10 and its treatment of
> |     multiple definitions of global variables		(Closes: #957134)
> |
> |   * Based on new 'upstream' git repo at github.com/eddelbuettel/dieharder
> |     which spawned off the salsa.debian.org repo for this package
> |
> |  -- Dirk Eddelbuettel <edd@debian.org>  Sat, 25 Jul 2020 12:36:49 -0500
> 
> This would not be the first time that debian extended the life of
> unmaintained upstream.
> 
> What do you think ?

I would be OK with switching to the github repo, indeed.

When you send the update patch, could you identify how much it has
diverged from the original upstream, too, so we can assess if that can
be considered for master (only bug fixes), or if it would go to next
(if there are features).

thanks for the heads up! :-)

Regards,
Yann E. MORIN.

> Regards,
> 
> Julien VdG
> 
> > 
> > Applied to master, thanks.
> > 
> > Regards,
> > Yann E. MORIN.
> > 
> > > ---
> > >  package/dieharder/dieharder.mk | 5 +++++
> > >  1 file changed, 5 insertions(+)
> > > 
> > > diff --git a/package/dieharder/dieharder.mk b/package/dieharder/dieharder.mk
> > > index c3eee64553..cbf28922fd 100644
> > > --- a/package/dieharder/dieharder.mk
> > > +++ b/package/dieharder/dieharder.mk
> > > @@ -36,4 +36,9 @@ endif
> > >  # parallel build fail, disable it
> > >  DIEHARDER_MAKE = $(MAKE1)
> > >  
> > > +# Too many fixes needed to build with -fno-common which is default since gcc 10
> > > +ifeq ($(BR2_TOOLCHAIN_GCC_AT_LEAST_10),y)
> > > +DIEHARDER_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -fcommon"
> > > +endif
> > > +
> > >  $(eval $(autotools-package))
> > > -- 
> > > 2.27.0
> > > 
> > > _______________________________________________
> > > buildroot mailing list
> > > buildroot at busybox.net
> > > http://lists.busybox.net/mailman/listinfo/buildroot
> > 
> > -- 
> > .-----------------.--------------------.------------------.--------------------.
> > |  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.  |
> > '------------------------------^-------^------------------^--------------------'

-- 
.-----------------.--------------------.------------------.--------------------.
|  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-08-20 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 16:34 [Buildroot] [PATCH 1/1] package/dieharder: fix build with gcc 10 Fabrice Fontaine
2020-08-19 21:34 ` Yann E. MORIN
2020-08-20  6:21   ` Julien Viard de Galbert
2020-08-20 20:35     ` Yann E. MORIN [this message]

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=20200820203507.GA17579@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