Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Keroulas <patrick.keroulas@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/4] libpjsip: add gnutls support and fix various things
Date: Tue, 3 May 2016 17:08:31 -0400 (EDT)	[thread overview]
Message-ID: <1719666448.88685.1462309711357.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <20160422232155.6ac9c7e2@free-electrons.com>

Hello Thomas,

On Apr 22, 2016, at 5:21 PM, Thomas Petazzoni thomas.petazzoni at free-electrons.com wrote:
> On Fri, 22 Apr 2016 16:57:05 -0400, Patrick Keroulas wrote:
>> Endianness for ARM.
>> Add missing errno.
>> Add multiple listeners.
>> Fix ICE config and session.
> 
> As the commit title suggests, this patch does too many things in one
> patch. Each of the things that you list here should be done by a
> separate patch.

Understood.

> 
>>  package/libpjsip/0003-Add-gnutls-support.patch     | 3373 ++++++++++++++++++++
> 
> Please don't include the generated configure script changes. Just patch
> configure.ac, and mark the package with <pkg>_AUTORECONF = YES.

For some reason, configure.ac was replaced with aconfigure.ac and it seems that 
autoconf is excluded from the build process. Then, configure script actually points
at pre-generated aconfigure.

Q: Should I add a link to aconfigure.ac to avoid autoconf error?
Or should I adjust <pkg>_AUTORECONF_(OPTS|ENV)

> 
> However, Buildroot has the policy of not carrying feature patches,
> which this one clearly is. Some please get this patch integrated
> upstream first, and then we can benefit from this feature in Buildroot.
> 
> Having large feature patches like this one in Buildroot would prevent
> us from easily updating libpjsip in the future, which is not a
> situation we like.

We've been trying to push these patches up-stream for 2 years now, without response from pjproject.
http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2014-May/017492.html
http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2015-January/018072.html

Thanks,

Patrick

  reply	other threads:[~2016-05-03 21:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 20:57 [Buildroot] [PATCH v1 0/4] Patrick Keroulas
2016-04-22 20:57 ` [Buildroot] [PATCH v1 1/4] libpjsip: add gnutls support and fix various things Patrick Keroulas
2016-04-22 21:21   ` Thomas Petazzoni
2016-05-03 21:08     ` Patrick Keroulas [this message]
2016-05-03 21:43       ` Arnout Vandecappelle
2016-05-04 15:22         ` Patrick Keroulas
2016-05-04 19:23           ` Arnout Vandecappelle
2016-04-22 20:57 ` [Buildroot] [PATCH v1 2/4] msgpack: bump to version 1.4.0 Patrick Keroulas
2016-04-22 21:23   ` Thomas Petazzoni
2016-05-02 20:57     ` Patrick Keroulas
2016-04-22 21:52   ` Thomas Petazzoni
2016-04-22 20:57 ` [Buildroot] [PATCH v1 3/4] openDHT: new package Patrick Keroulas
2016-04-22 21:30   ` Thomas Petazzoni
2016-04-22 20:57 ` [Buildroot] [PATCH v1 4/4] ring-daemon: " Patrick Keroulas
2016-04-22 22:19   ` Thomas Petazzoni
2016-04-25 14:29     ` Jérôme Oufella
2016-04-25 18:18     ` Patrick Keroulas
2016-04-25 19:24       ` Thomas Petazzoni
2016-04-25 21:20         ` Patrick Keroulas

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=1719666448.88685.1462309711357.JavaMail.zimbra@savoirfairelinux.com \
    --to=patrick.keroulas@savoirfairelinux.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