devel/uwsgi

[Michael Gmelin]

On Sat, 23 Feb 2013 15:38:36 +0200
Daniel Braniss <danny at cs.huji.ac.il> wrote:

> Hi Michael,
> 
> > uname -a
> FreeBSD rnd 9.1-STABLE FreeBSD 9.1-STABLE #46: Tue Feb  5 10:46:56
> IST 2013 danny at rnd:/home/obj/rnd/r+d/stable/9/sys/HUJI  amd64
> 
> > Compilation options you used when building python
> the deaults from ports/lang/python27:
> 	EXAMPLES
> 	NLS
> 	PYMALLOC
> 	UCS4

Hm, THREADS should be on by default too.

cd /usr/ports/devl/python27
make showconfig

===> The following configuration options are available for
python27-2.7.3_6: EXAMPLES=on: Build and/or install examples
     FPECTL=off: Floating point exception handling
     IPV6=on: IPv6 protocol
     NLS=on: Enable Gettext support for the locale module
     PTH=off: Threading/multiprocessing via GNU Pth
     PYMALLOC=on: Use Python's internal malloc
     SEM=off: POSIX semaphores
     THREADS=on: Threading support
====> Options available for the single UCS: you have to select exactly
one of them UCS2=off: Unicode UCS-2 encoding
     UCS4=on: Unicode UCS-4 encoding
===> Use 'make config' to modify these settings

That's:

EXAMPLES
IPV6
NLS
PYMALLOC
THREADS
UCS4

Unless you have a good reason to use different settings I'd suggest to
use the defaults (make rmconfig), especially for threads.

> > Compiled using gcc or clang
> gcc

Ah ok, we're using clang here, that might make a difference too.

> 
> 
> python -V
> 	Python 2.7.3
> 
> btw, I compiled it before for 8.3 without any problems too.
> It seems that CPUCOUNT is only used to compile (faster?) if so,
> then it's not important, unless I have some other real problem.

Might as well be a gcc problem (in that case hunting it down makes
little sense, since gcc will be removed from base in the future
anyway), not clear, I'd still suggest to build python using the
default configuration settings).

> 
> thanks,
> 	danny
> PS: can you reply to me too, since im not subscribed to ports?
> 

ok ;)

Cheers,

> 
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to
> "freebsd-ports-unsubscribe at freebsd.org"





-- 
Michael Gmelin