From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-07
Date: Fri, 19 Aug 2016 09:21:08 +0200 [thread overview]
Message-ID: <20160819092108.7b175cec@free-electrons.com> (raw)
In-Reply-To: <CAGm1_kvHgEDQrs0bjMNO94pMvS2WgBDU8G8W956mT3MTe8u+oQ@mail.gmail.com>
Hello,
On Fri, 19 Aug 2016 07:29:29 +0200, Yegor Yefremov wrote:
> > x86_64 | python-psutil-4.3.0 | NOK | http://autobuild.buildroot.net/results/2a67d1580787e9fe2781bf2db91bb5e3e23ab2ea/
>
> Have opened an issue: https://github.com/giampaolo/psutil/issues/872
>
> Any idea how to properly fix this issue?
I would suggest you to ask on the musl mailing list. They are the ones
knowing best how to deal with this conflicting header issue.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-08-19 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-07 Thomas Petazzoni
2016-08-19 5:29 ` Yegor Yefremov
2016-08-19 7:21 ` Thomas Petazzoni [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=20160819092108.7b175cec@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox