From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-13
Date: Mon, 14 Mar 2016 12:00:54 +0100 [thread overview]
Message-ID: <20160314120054.45e1983c@free-electrons.com> (raw)
In-Reply-To: <56E69644.4030002@lucaceresoli.net>
Luca,
On Mon, 14 Mar 2016 11:45:24 +0100, Luca Ceresoli wrote:
> Hi,
>
> On 14/03/2016 08:30, Thomas Petazzoni wrote:
> [...]
> > arm | libpjsip-2.4.5 | NOK | http://autobuild.buildroot.net/results/e5c85272b5561549dfc478264ee6507bb9ad8c9f/
>
> Musl toolchain, and as Thomas already pointed out libpjsip does not
> build with it.
>
> Patches to fix this issue are almost ready here. But it might need a
> little extra time before I can send them to Buildroot because the pjsip
> project requires Copyright Assignment, with associated paperwork... :|
Two options:
1/ You submit your patches to Buildroot before doing the copyright
assignment. From a Buildroot point of view, it is sufficient if
your patches are licensed under the publicly available license of
pjsip. Of course, if they later get merged upstream after doing the
copyright assignment, it is better, but that doesn't prevent from
submitting the patches to Buildroot IMO.
2/ You submit a patch that disables pjsip on musl for the moment, and
you can re-enable it once the patches have been accepted upstream.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-14 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-13 Thomas Petazzoni
2016-03-14 10:45 ` Luca Ceresoli
2016-03-14 11:00 ` Thomas Petazzoni [this message]
2016-03-14 22:21 ` Luca Ceresoli
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=20160314120054.45e1983c@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 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.