From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/freeswitch: bump version to 1.6.13
Date: Sun, 18 Dec 2016 22:25:07 +0100 [thread overview]
Message-ID: <jebjidx41h.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20161207225215.663fca31@free-electrons.com
Am Wed, 07 Dec 2016 22:52:15 +0100 schrieb Thomas Petazzoni:
> Thanks. However, we have a bunch of build failures with 1.6.12, could
> you have a look:
>
> http://autobuild.buildroot.net/?reason=freeswitch-1.6.12
>
> Maybe 1.6.13 fixes those build failures?
Hi Thomas,
no, 1.6.13 did not fix the build failures, freeswitch git master is also
affected, tested with http://autobuild.buildroot.net/results/b37/
b370813ce8bde65a9208d7678e67a3b2f22ef36c/defconfig and personal patches
containing the version bump to fsw git master.
The build failures started on Dec 5th:
http://autobuild.buildroot.net/?reason=freeswitch-1.6.12
only several hours after you updated all pre-built toolchains used on
autobuild.b.o:
http://lists.busybox.net/pipermail/buildroot/2016-December/179017.html
Maybe the failures[1] result from the updated toolchains?
They only occur with uclibc and only on arc/arm/powerpc/xtensa.
Regards, Bernd
[1] Quoting http://autobuild.buildroot.net/results/b37/
b370813ce8bde65a9208d7678e67a3b2f22ef36c/build-end.log
In file included from libs/spandsp/src/alloc.c:43:0:
/home/peko/autobuild/instance-0/output/host/usr/xtensa-buildroot-linux-
uclibc/sysroot/usr/include/stdlib.h:500:35: error: expected ',' or ';'
before '__attribute_alloc_size__'
__THROW __attribute_malloc__ __attribute_alloc_size__ ((2)) __wur;
^
next prev parent reply other threads:[~2016-12-18 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 21:25 [Buildroot] [PATCH 1/1] package/freeswitch: bump version to 1.6.13 Bernd Kuhls
2016-12-07 21:52 ` Thomas Petazzoni
2016-12-18 21:25 ` Bernd Kuhls [this message]
2016-12-19 22:28 ` Thomas Petazzoni
2016-12-07 22:38 ` 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=jebjidx41h.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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