Ronald Oussoren <ronaldousso...@mac.com> added the comment: On 4 Jun, 2009, at 0:59, Benjamin Peterson wrote:
> > Benjamin Peterson <benja...@python.org> added the comment: > > 2009/6/3 Ronald Oussoren <rep...@bugs.python.org>: >> >> Ronald Oussoren <ronaldousso...@mac.com> added the comment: >> >> I just noticed the update of the title. >> >> I propose to close this issue if this is caused by a non-universal >> version >> of libintl that's installed by macports. > > Actually, it can happen with regular builds, but the attached patches > fix that issue. How can it happen with regular builds? This can only happen if there is a non-universal copy of used libraries on the compiler search-path, or rather if there are libraries with incompatible architectures on the search-path. This would also happen with readline, or if you have a ppc-only library on an intel machine. Not having the right archtectures of libraries is IMHO in "don't do that then" territory. Ronald ---------- Added file: http://bugs.python.org/file14182/smime.p7s _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6154> _______________________________________
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
