From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-09-03
Date: Mon, 4 Sep 2017 15:09:03 +0200 [thread overview]
Message-ID: <20170904150903.1ea53556@windsurf.lan> (raw)
In-Reply-To: <CALdGskKWPKBPC8gRdZKhOgMXbWoKgMzVxVOzau6HiBc+Sp6ohg@mail.gmail.com>
Hello,
On Mon, 4 Sep 2017 15:04:33 +0200, Olivier Schonken wrote:
> Hi Thomas
>
> Looks like these errors are from uclibc builds.
>
> In file included from
> /home/buildroot/autobuild/run/instance-3/output/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/sched.h:34:0,
> from
> /home/buildroot/autobuild/run/instance-3/output/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/pthread.h:24,
> from
> /home/buildroot/autobuild/run/instance-3/output/build/openjpeg-2.2.0/src/lib/openjp2/thread.c:288:
> /home/buildroot/autobuild/run/instance-3/output/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/bits/sched.h:210:46:
> error: attempt to use poisoned "malloc"
> # define __sched_cpualloc(cnt) ((cpu_set_t *)malloc(__CPU_ALLOC_SIZE(cnt)))
> ^
> /home/buildroot/autobuild/run/instance-3/output/host/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include/bits/sched.h:211:33:
> error: attempt to use poisoned "free"
> # define __sched_cpufree(__set) free(__set)
>
> Not sure what the best course of action will be. Try to fix it for
> uclibc, do a rollback or disable build for uclibc and open issue on
> github for openjpeg.
>
> Your thoughts?
I'm not sure here, since I haven't investigated those build issues.
Let's Cc the Buildroot mailing list and uClibc-ng maintainer Waldemar
to see what they think.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next parent reply other threads:[~2017-09-04 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170904063112.61D1E2085B@mail.free-electrons.com>
[not found] ` <CALdGskKWPKBPC8gRdZKhOgMXbWoKgMzVxVOzau6HiBc+Sp6ohg@mail.gmail.com>
2017-09-04 13:09 ` Thomas Petazzoni [this message]
2017-09-04 13:38 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-09-03 Olivier Schonken
2017-09-04 17:31 ` Waldemar Brodkorb
2017-09-05 9:11 ` Olivier Schonken
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=20170904150903.1ea53556@windsurf.lan \
--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