mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] nginx: new package
Date: Tue, 29 Nov 2016 15:03:03 +0100	[thread overview]
Message-ID: <20161129140303.GA9385@archie.localdomain> (raw)
In-Reply-To: <20161129091001.yvkwo55mrmmh476o@pengutronix.de>

Hi Michael, Hi Jürgen,

thanks for the comments!

On Tue, Nov 29, 2016 at 10:10:01AM +0100, Michael Olbrich wrote:
> On Sun, Nov 06, 2016 at 08:12:18PM +0100, Clemens Gruber wrote:
> > Add nginx package. Heavily inspired by Buildroot's nginx.mk, using their
> > revised patches for 1.10.x and the endian patch from Marc Kleine-Budde,
> > as well as the nginx.make from the patchset Robert sent, as a starting
> > point.
> 
> Do you know if anyone has tried to upstream the cross-compile patches?

Yes, but they were not accepted:
http://mailman.nginx.org/pipermail/nginx-devel/2014-May/005318.html
http://mailman.nginx.org/pipermail/nginx-devel/2014-September/006013.html
They want them to be less intrusive, more portable (+MSVC), without
deactivating all tests. They seem to be pretty strict in what they
accept. Looks like the author of the patch series gave up and is afaik
now maintaining them out of tree in the Buildroot repo.

> 
> > But instead of building the modules by default, each module is
> > selectable in PTXdist, to allow reducing the binary size.
> > 
> > Most popular modules are supported, systemd unit file and basic
> > configuration files are included as well.
> > Supports SSL, HTTP/2, HTTP Proxying, GZIP, Auth Basic, Rewrite, FastCGI,
> > SCGI, uWSGI, etc.
> > 
> > Signed-off-by: Clemens Gruber <clemens.gruber@pqgruber.com>
> > ---
> >  ...izeof-rework-autotest-to-be-cross-compila.patch |  87 +++++++++
> >  ...e-add-mechanism-allowing-to-force-feature.patch | 135 +++++++++++++
> >  ...x_feature_run_force_result-for-each-featu.patch | 213 +++++++++++++++++++++
> >  ...0004-auto-lib-libxslt-conf-use-pkg-config.patch |  31 +++
> >  ...nix-make-sys_nerr-guessing-cross-friendly.patch | 138 +++++++++++++
> >  ...0006-auto-lib-openssl-conf-use-pkg-config.patch |  31 +++
> >  .../0007-auto-lib-libgd-conf-use-pkg-config.patch  |  31 +++
> >  ...-ngx_linux_config.h-only-include-dlfcn.h-.patch |  33 ++++
> >  ...ness-add-mechanism-allowing-to-force-resu.patch |  26 +++
> >  patches/nginx-1.10.2/series                        |  11 ++
> >  projectroot/etc/nginx/mime.types                   |  89 +++++++++
> 
> Why did you add this file? nginx installs it into pkgdir and
> install_alternative will use that as a fallback.

Right, I'll remove it.

(snip)

> > +# Note: Settings and module options are *not* symmetric.
> > +#       If a module is on by default, a without option exists.
> > +#       If it is off by default, a with option exists.
> > +
> > +# Opt-in settings
> > +
> 
> NGINX_CONF_OPT += \
> 	$(call ptx/ifdef, PTXCONF_*,--with-*) \
> 	[...]
> 
> For each Opt-in/Opt-out etc. group. Or just one block with all modules. Or
> make list + foreach magic like I handled the gstreamer plugins. Either way
> is fine, I just want this to be more compact.

Will do.

(snip)

> > +
> > +ifdef PTXCONF_SYSTEMD
> 
> No, never use an option from a different package directly. Either install
> this unconditionally (I'd prefer that) or add an options without prompt
> that defaults to SYSTEMD.

OK.

I'd also remove the NGINX_OPENSSL setting from the "Base settings"
menu, because the http_ssl and http_v2 modules select it anyway and we
could select OPENSSL at the top if those modules are enabled.
Or would you prefer that I keep NGINX_OPENSSL but remove its prompt?

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-11-29 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-06 19:12 Clemens Gruber
2016-11-29  7:43 ` Juergen Borleis
2016-11-29  9:10 ` Michael Olbrich
2016-11-29 14:03   ` Clemens Gruber [this message]
2016-11-29 16:24   ` Clemens Gruber
2016-11-30 13:15     ` Michael Olbrich

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=20161129140303.GA9385@archie.localdomain \
    --to=clemens.gruber@pqgruber.com \
    --cc=ptxdist@pengutronix.de \
    /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