All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] nginx-dav-ext: New package
Date: Mon, 5 Dec 2016 12:14:42 +0100	[thread overview]
Message-ID: <20161205121442.51bb6c46@free-electrons.com> (raw)
In-Reply-To: <CAJtjsKY2yT_EekNg2F_-K-PyLN5Zp47ykhRwVK4Kg3PixY4K9A@mail.gmail.com>

Hello,

On Mon, 5 Dec 2016 11:58:33 +0100, Johan Oudinet wrote:

> > I've applied to master, but after doing a number of changes. See below.  
> 
> Thanks Thomas.
> 
> > I've also added a separate patch to add you in the DEVELOPERS file for
> > nginx-dav-ext (even though you will never receive a build failure about
> > it, since the build really takes place inside the nginx package).
> 
> Oops, so many changes since I've sent a patch to BR. I should have
> read the documentation more carefully. Thanks.

Seems like my changes broke the build:

   http://autobuild.buildroot.net/?reason=nginx-1.10.2

So, it might be that the location in which modules are added in
nginx.mk might be important. Weird, because I did a number of test
builds before pushing and never got a failure.

Do you have the time to investigate? One of the failure,
http://autobuild.buildroot.net/results/3c8/3c8798f122a421e8fae741de76b2504c20e2da91/build-end.log,
is related to dav-ext.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-12-05 11:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 16:47 [Buildroot] [PATCH 1/1] nginx-dav-ext: New package Johan Oudinet
2016-12-01 10:34 ` Johan Oudinet
2016-12-04 22:52 ` Thomas Petazzoni
2016-12-05 10:58   ` Johan Oudinet
2016-12-05 11:14     ` Thomas Petazzoni [this message]
2016-12-05 13:20       ` Johan Oudinet
2016-12-05 13:33         ` Thomas Petazzoni
2016-12-05 13:41           ` Johan Oudinet
2016-12-05 13:53             ` Thomas Petazzoni
2016-12-05 14:31               ` Johan Oudinet

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=20161205121442.51bb6c46@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.