Hi!
First of all congratulations for arriving at 1.0! I'm following the
progress you're doing with this project and I must say I'm very
impressed - not only by the endless amount of options but especially by
the overall functionality & very slick hacking, gluing together various
solutions/standards - simply amazing.
OK, so I've seen the release today morning & tried compiling it, this is
what I got:
python uwsgiconfig.py --build
using profile: buildconf/default.ini
detected include path: ['/usr/local/include',
'/usr/lib/gcc/x86_64-redhat-linux/4.1.2/include', '/usr/include']
configured CFLAGS: -O2 -Wall -Werror -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -fno-strict-aliasing -Wextra
-Wno-unused-parameter -Wno-missing-field-initializers
-DUWSGI_BUILD_DATE="\"30 December 2011 09:16:56\"" -DUWSGI_HAS_IFADDRS
-DUWSGI_LOCK_USE_MUTEX -DUWSGI_EVENT_USE_EPOLL
-DUWSGI_EVENT_TIMER_USE_NONE -DUWSGI_EVENT_FILEMONITOR_USE_INOTIFY
-DUWSGI_EMBEDDED -DUWSGI_UDP -DUWSGI_CAP -DUWSGI_UUID
-DUWSGI_VERSION="\"1.0\"" -DUWSGI_VERSION_BASE="1"
-DUWSGI_VERSION_MAJOR="0" -DUWSGI_VERSION_MINOR="0"
-DUWSGI_VERSION_REVISION="0" -DUWSGI_VERSION_CUSTOM="\"\""
-DUWSGI_ASYNC -DUWSGI_MULTICAST -DUWSGI_MINTERPRETERS -DUWSGI_INI
-DUWSGI_YAML -DUWSGI_LDAP -DUWSGI_SNMP -DUWSGI_THREADING
-DUWSGI_SENDFILE -I/usr/include/libxml2 -DUWSGI_XML
-DUWSGI_XML_LIBXML2 -DUWSGI_SQLITE3 -DUWSGI_PLUGIN_DIR=\".\"
-DUWSGI_SPOOLER
-DUWSGI_DECLARE_EMBEDDED_PLUGINS="UDEP(python);UDEP(ping);UDEP(cache);UDEP(nagios);UDEP(rrdtool);UDEP(carbon);UDEP(rpc);UDEP(fastrouter);UDEP(http);UDEP(ugreen);UDEP(signal);UDEP(syslog);UDEP(rsyslog);UDEP(logsocket);"
-DUWSGI_LOAD_EMBEDDED_PLUGINS="ULEP(python);ULEP(ping);ULEP(cache);ULEP(nagios);ULEP(rrdtool);ULEP(carbon);ULEP(rpc);ULEP(fastrouter);ULEP(http);ULEP(ugreen);ULEP(signal);ULEP(syslog);ULEP(rsyslog);ULEP(logsocket);"
*** uWSGI compiling server core ***
[gcc -pthread] utils.o
[gcc -pthread] protocol.o
[gcc -pthread] socket.o
[gcc -pthread] logging.o
[gcc -pthread] master.o
[gcc -pthread] master_utils.o
[gcc -pthread] emperor.o
[gcc -pthread] notify.o
[gcc -pthread] mule.o
[gcc -pthread] subscription.o
[gcc -pthread] plugins.o
[gcc -pthread] lock.o
[gcc -pthread] cache.o
[gcc -pthread] queue.o
[gcc -pthread] event.o
[gcc -pthread] signal.o
[gcc -pthread] cluster.o
[gcc -pthread] rpc.o
[gcc -pthread] gateway.o
[gcc -pthread] loop.o
[gcc -pthread] lib/rbtree.o
[gcc -pthread] lib/amqp.o
[gcc -pthread] rb_timers.o
[gcc -pthread] main.o
[gcc -pthread] proto/base.o
[gcc -pthread] proto/uwsgi.o
[gcc -pthread] proto/http.o
[gcc -pthread] proto/fastcgi.o
[gcc -pthread] lib/linux_ns.o
[gcc -pthread] lib/netlink.o
In file included from lib/netlink.c:18:
/usr/include/linux/netlink.h:41: error: expected
specifier-qualifier-list before ‘__u16’
/usr/include/linux/netlink.h:128: error: expected
specifier-qualifier-list before ‘__u16’
In file included from /usr/include/linux/rtnetlink.h:5,
from lib/netlink.c:19:
/usr/include/linux/if_addr.h:8: error: expected
specifier-qualifier-list before ‘__u8’
In file included from lib/netlink.c:19:
/usr/include/linux/rtnetlink.h:321: error: expected
specifier-qualifier-list before ‘__s32’
/usr/include/linux/rtnetlink.h:375: error: expected
specifier-qualifier-list before ‘__u8’
/usr/include/linux/rtnetlink.h:407: error: expected
specifier-qualifier-list before ‘__u16’
/usr/include/linux/rtnetlink.h:487: error: expected
specifier-qualifier-list before ‘__u64’
/usr/include/linux/rtnetlink.h:522: error: expected
specifier-qualifier-list before ‘__u8’
/usr/include/linux/rtnetlink.h:529: error: expected
specifier-qualifier-list before ‘__u16’
/usr/include/linux/rtnetlink.h:656: error: expected
specifier-qualifier-list before ‘__u64’
make: *** [all] Error 1
The OS is CentOS 5.7 64bit (same on SL 5.5), Python 2.7.2. I ran only
'make' on extracted sources. It seems some type defs are missing.
0.9.9.2 compiled without problems
Am I missing a -dev package or is this a uwsgi issue?
Thanks in advance.
W dniu 30.12.2011 08:56, Roberto De Ioris pisze:
After 2 years of development, the uWSGI project is at 1.0
This major release focuses on adaptive process spawning (--cheaper mode),
the new stats framework, Mules and an incredible amount of bug fixes and
code refactoring.
Changelog:
- adaptive process spawning (--cheaper option)
- new control options --stop, --reload, --suspend, --resume, --pause
- stats framework
http://projects.unbit.it/uwsgi/wiki/StatsServer
- new subscription system
- support for mime types in static file serving
- posix capablities support
http://projects.unbit.it/uwsgi/wiki/Capabilities
- uWSGI mules and farms
http://projects.unbit.it/uwsgi/wiki/Mules
- support for multiple --touch-reload options
- new logging subsystem
- new custom locking subsystem
http://projects.unbit.it/uwsgi/wiki/Locks
- process name handling
- better (and faster) HTTP parser
- perl and python threading improvements
- new plugins: rrdtool, carbon, cgi, php
http://projects.unbit.it/uwsgi/wiki/Carbon
http://projects.unbit.it/uwsgi/wiki/CGI
http://projects.unbit.it/uwsgi/wiki/PHP
- various improvements in the Rack/ruby plugin
http://projects.unbit.it/uwsgi/wiki/rubyDSL
- Linux KSM support
http://projects.unbit.it/uwsgi/wiki/KSM
- refactored ping and nagios plugins
- support for signals in lazy mode
- optimized static-file serving
- support for linux unshare()
You can download the tarball from
http://projects.unbit.it/downloads/uwsgi-1.0.tar.gz
* Special Thanks *
Lukasz Mierzwa for its incredible amount of test reports with complex
configurations
Giacomo Bagnoli for the KSM idea
Graham Dumpleton (mod_wsgi/newrelic) for help in addressing various
threading issues in the python plugin
* Issues *
A bunch of patches are left out from 1.0, they will be committed in the
future
- you cannot compile the rack plugin with the spooler disabled
- the httprouter subscription system is not solid as the fastrouter one -
support for multiple perl interpreters is post-poned to 1.1
- the graphite/carbon plugin should export more metrics
* Notes *
uWSGI 1.0 is the new LTS release
KSM does not grant you memory gain, it is completely app-dependent
The ruby/rack plugin has an extremely aggressive GC policy, do not expect
extreme performance without tuning it
If you run uWSGI on some hosting provider/PaaS supporting only HTTP, be
sure to use --http-socket instead of --http (extreme performance gain)
Bye
--
Pozdrawiam,
Łukasz Czuja
Programista / Analityk / Architekt IT
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
