I realize django-svn is hardmasked and unsupported: This is an 'FYI', not something I'm expecting to get fixed overnight. To build postgresql on freebsd requires python to be built without threads; however, the current trend for django seems to be that python threads are required. Various django commands, such as manage.py syncdb, will fail if threaded python is unavailable. (Note that django 0.96 works fine.) Reproducible: Always Steps to Reproduce: Sloppy Workarounds: - Use a different (or virtual) server for the db than for django; - Take crazy advantage of SLOTting (use one python with threads, one without) - Use Linux instead of BSD (sad) - Use another db (sad) Using: dev-lang/python-2.5.2-r7 USE="berkdb gdbm ncurses readline ssl -bootstrap -build -doc -examples -ipv6 -sqlite -threads -tk -ucs2 -wininst" dev-db/postgresql-8.2.7 USE="nls pam perl python readline ssl zlib -doc (-kerberos) -pg-intdatetime (-selinux) -tcl -test -xml" dev-python/django-9999 USE="postgres -bash-completion -doc -examples -mysql -sqlite -test" Portage 2.2_rc8 (default-bsd/fbsd/6.2/x86, gcc-4.2.4, freebsd-lib-6.2-r4, 6.2-RELEASE i386) ================================================================= System uname: FreeBSD-6.2-RELEASE-i386-32bit Timestamp of tree: Wed, 20 Aug 2008 16:04:01 +0000 app-shells/bash: 3.2_p39 dev-lang/python: 2.5.2-r7 sys-apps/baselayout: 2.0.0 sys-apps/openrc: 0.2.5 sys-devel/autoconf: 2.62-r1 sys-devel/automake: 1.10.1-r1 sys-devel/binutils: 2.17-r2 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 2.2.4 virtual/os-headers: 6.2-r4 ACCEPT_KEYWORDS="x86-fbsd ~x86-fbsd" CBUILD="i686-gentoo-freebsd6.2" CFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" CHOST="i686-gentoo-freebsd6.2" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="collision-protect distlocks parallel-fetch preserve-libs sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LDFLAGS="" MAKEOPTS="-sj3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="berkdb cli cracklib crypt cups dri gdbm iconv java5 ldap midi ncurses nls oss pam pcre perl postgres ppds python readline reflection session spl ssl tcpd unicode x86-fbsd zlib" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" APACHE2_MPMS="prefork" ELIBC="FreeBSD" INPUT_DEVICES="keyboard mouse" KERNEL="FreeBSD" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="BSD" VIDEO_CARDS="apm ark chips cirrus cyrix dummy i128 i810 mach64 mga neomagic nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tga trident tseng vga via vmware" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
A (not perfect but) slightly better option, emerge postgres without python useflag. That way you can have threaded python, and for django just use psycopg2. Not sure but I think this will get solved once fbsd7 gets in.
> A (not perfect but) slightly better option, emerge postgres without python > useflag. That way you can have threaded python, and for django just use > psycopg2. > Not sure but I think this will get solved once fbsd7 gets in. > Now that fbsd7 (and 8) is out, is this still applicable?
The PostgreSQL ebuilds don't require Python to be built with threads. The upstream documentation doesn't mention anything about threads either. Is this still an issue, or is it really fixed?
