Date: Mon, 9 Jan 2012 16:13:01 +0100 From: Roberto De Ioris <roberto@unbit.it> To: Maxim Khitrov <max@mxcrypt.com> Cc: Daniel Gerzo <danger@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: [patch] Problem building www/uwsgi on FreeBSD 9 Message-ID: <0683987E-9D15-41BD-8CFB-D76F693A89E1@unbit.it> In-Reply-To: <CAJcQMWdXABvnQYENGpWEUPm6N7tTFc0rkiYC2jHCZtrMBpX5Jg@mail.gmail.com> References: <CAJcQMWdXABvnQYENGpWEUPm6N7tTFc0rkiYC2jHCZtrMBpX5Jg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Il giorno 08/gen/2012, alle ore 21:43, Maxim Khitrov ha scritto: > Hi all, > > I'm not sure whether this is a FreeBSD or uwsgi problem, but the > current port (uwsgi 1.0) isn't compiling on FreeBSD 9.0-RELEASE amd64 > for the following reasons: > > 1. In uwsgiconfig.py:534 uwsgi checks for the existence of > sys/capability.h. This header isn't present on my 7.x or 8.x systems, > but it is there in FreeBSD 9. > > 2. If the check succeeds, UWSGI_CAP is defined for compilation. > > 3. In uwsgi.h:1169 the presence of UWSGI_CAP causes "cap_value_t > *cap;" to be defined. > > 4. The FreeBSD version of sys/capability.h does not define cap_value_t > (which seems to be a simple int typedef on Linux). > > The net effect of this is a long series of errors when compiling utils.c: FreeBSD9 capabilities are completely different from linux one. I will try to make a port, otherwise i will enable to check only for linux. -- Roberto De Ioris http://unbit.it JID: roberto@jabber.unbit.it
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0683987E-9D15-41BD-8CFB-D76F693A89E1>