All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] procps-ng: bump to version 3.3.14
Date: Wed, 18 Apr 2018 13:22:51 +0200	[thread overview]
Message-ID: <20180418132251.0d1d735c@windsurf.numericable.fr> (raw)
In-Reply-To: <20180418101334.wq7wxgd5owwsiona@tarshish>

Hello,

On Wed, 18 Apr 2018 13:13:34 +0300, Baruch Siach wrote:

> > I have started a new build of all the br-* pre-built toolchains with
> > the latest Git master. I'll wait for this to finish, deploy the
> > toolchains, and then apply this patch, if that's OK for you.  
> 
> That's perfectly fine with me.

OK, thanks.

> While at it, you might want to look into the issue of libgcc link failure in 
> static musl toolchains. This issue currently affects lm-sensors and multicat. 
> See http://patchwork.ozlabs.org/patch/883243/.

I did have a look at this issue two weeks ago or so, and like you, I
concluded that there was a toolchain issue. I guess it should be
reported to musl upstream. It may not be a musl issue per-se, perhaps
more a musl-into-gcc integration issue, but they might be able to help.
Do you think you could contact the musl folks about this ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-04-18 11:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 19:58 [Buildroot] [PATCH v2] procps-ng: bump to version 3.3.14 Baruch Siach
2018-04-18 10:04 ` Thomas Petazzoni
2018-04-18 10:13   ` Baruch Siach
2018-04-18 11:22     ` Thomas Petazzoni [this message]
2018-04-18 19:56       ` Baruch Siach
2018-04-19  4:50         ` Baruch Siach
2018-04-25 21:01 ` Thomas Petazzoni

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=20180418132251.0d1d735c@windsurf.numericable.fr \
    --to=thomas.petazzoni@bootlin.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.