[Patches] [ python-Patches-752671 ] NetBSD needs to link libintl
SourceForge.net
noreply@sourceforge.net
Sat, 14 Jun 2003 08:44:48 -0700
Patches item #752671, was opened at 2003-06-11 17:47
Message generated for change (Settings changed) made by loewis
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=752671&group_id=5470
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Marc Recht (marc)
>Assigned to: Martin v. Löwis (loewis)
Summary: NetBSD needs to link libintl
Initial Comment:
On NetBSD the libintl.h is found, but the libintl to linked.
Therefore the locale module fails to link. The attached patch
changes configure.in to check for textdomain in libintl and if it's
found it adds libintl to $LIBS.
----------------------------------------------------------------------
Comment By: Marc Recht (marc)
Date: 2003-06-14 17:13
Message:
Logged In: YES
user_id=205
OK, changed that. In fact I made two different solutions,
because there was no prior case of configure/setup.py
interaction (or I didn't see it..)
1. configure checks for textdomain in libintl, sets a define
accordingly and setup.py checks for that define
2. setupy checkfs for libintl.h if it's found libintl is
added to list of libs for _locale
Both solutions for on my NetBSD-current system with today's
Python 2.3/cvs.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2003-06-14 07:47
Message:
Logged In: YES
user_id=21627
Linking python with libintl is incorrect as it is needed for
_locale.so. Instead, you should come up with a patch for
setup.py, and perhaps a (comment) patch for
Modules/Setup.dist. While the patch probably "works" on most
systems, it fails when libintl is needed and is a non-shared
library (libintl.a).
It would be IMO safe to assume that -lintl is needed if
libintl.h is present; if you want to, you can still perform
a test for textdomain in configure, and communicate its
result to setup.py through a #define.
P.S. There is no need to compress 600 byte attachments, IMO.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=752671&group_id=5470