All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3427] New: New package: nginx
Date: Mon,  7 Mar 2011 16:21:59 +0000 (UTC)	[thread overview]
Message-ID: <bug-3427-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=3427

           Summary: New package: nginx
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: info at daccii.it
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 3115
  --> https://bugs.busybox.net/attachment.cgi?id=3115
patch

Add nginx package.

Nginx is a fast and light webserver. While page serving speed is the same of
lighttpd, nginx consumes less resoruces.

NOTE:
actually http_cache and ssl modules are broken: nginx needs to statically
recompile openssl.
If i manually compile nginx from buildroot sources, with the same compilation
command, enabling ssl and openssl, all goes well but if buildroot does it,
compilation fail!
I hope to fix this really soon, i need them.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2011-03-07 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 16:21 bugzilla at busybox.net [this message]
2011-09-18 10:16 ` [Buildroot] [Bug 3427] New package: nginx bugzilla at busybox.net
2014-04-24 21:58 ` bugzilla at busybox.net
2014-08-25 19:02 ` bugzilla at busybox.net
2014-09-02  8:36 ` bugzilla at busybox.net

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=bug-3427-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.