IOV_MAX patch not required - causes redefinition warnings
Bug #260022 reported by
Neil Wilson
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nginx (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: nginx
The problems previously reported and patched in #247745 (Fix for FTBFS on i386/amd64 and other archs) are no longer an issue. IOV_MAX is again correctly defined when you include <limits.h> as it should be according to the Unix specification.
Related branches
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in nginx: | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package nginx - 0.6.34-2ubuntu1
---------------
nginx (0.6.34-2ubuntu1) jaunty; urgency=low
* Merge from Debian unstable. Remaining Ubuntu changes:
+ debian/control:
- Add Depend on lsb >= 3.2-14, which has the status_of_proc() function.
+ debian/init.d:
- Add sourcing to '. /lib/lsb/
- Add the 'status' action
* Drop unneeded IOV_MAX patch and dpatch system (LP: #260022)
nginx (0.6.34-2) unstable; urgency=low
* Added support for realip module. (Closes: #507419)
-- Lionel Porcheron <email address hidden> Mon, 08 Dec 2008 00:02:46 +0100