[issue4366] cannot find -lpython2.5 when buinding Python 2.5.2 on FreeBSD 4.11

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Since r53691, and issue 1600860, "." is added to library_dirs on Linux and GNU systems. This probably should be extended to FreeBSD, and other systems. The critical point to notice is that the -L option is not only while building Python itse

[issue4366] cannot find -lpython2.5 when buinding Python 2.5.2 on FreeBSD 4.11

Akira Kitada <[EMAIL PROTECTED]> added the comment: Christian's patch fixed this problem! (tested on 4.11-RELEASE) I'm not sure why the other platforms don't suffer this problem. ___ Python tracker <[EMAIL PROTECTED]> __

[issue4366] cannot find -lpython2.5 when buinding Python 2.5.2 on FreeBSD 4.11

Christian Heimes <[EMAIL PROTECTED]> added the comment: Please try this patch with a clean source tree. It adds the current directory to the library search path. Index: setup.py === --- setup.py(revision 67295) +++ setup.py(

[issue4366] cannot find -lpython2.5 when buinding Python 2.5.2 on FreeBSD 4.11

New submission from Akira Kitada <[EMAIL PROTECTED]>: I get a number of "cannot find -lpython2.5" error when building Python 2.5.2 on FreeBSD 2.5.2 with gcc 2.95.4. This problem is only occured when I build it with "--enable-shared" configure option. This is how you can reproduce this problem.