➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2003-03-11 21:34 by qual, last changed 2022-04-10 16:07 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| 2.3a2.diff | qual, 2003-03-11 21:38 | patch Makefile.pre.in, configure.in | ||
| Messages (2) | |||
|---|---|---|---|
| msg15077 - (view) | Author: Uwe Hoffmann (qual) | Date: 2003-03-11 21:34 | |
on building python 2.3.a2 with the following lines ./configure --prefix=/tmp/python --enable-shared --with-cxx=g++ --with-signal-module --with-threads ; make ; make install; the installed python interpreter cann't be started because libpython2.3.so.1.0 is installed but not libpython2.3.so . the attached patch works in my environment. Linux ; glibc 2.2.5; gcc 3.2; binutils 2.13 at least solaris should suffer from the same problem. (the change for configure.in is not tested, the changes were directly made to configure) the same can be achieved if libpython$(VERSION)$(SO) (actually libpython2.3.so ) is installed and not $(INSTSONAME) ( actually libpython2.3.so.1.0) . |
|||
| msg15078 - (view) | Author: Martin v. Löwis (loewis) *  |
Date: 2003-03-30 15:53 | |
Logged In: YES user_id=21627 This is fixed in Makefile.pre.in 1.119 (in a different way). On Solaris, the same problem does not exists, since SOVERSION is only used on Linux. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-10 16:07:34 | admin | set | github: 38147 |
| 2003-03-11 21:34:53 | qual | create | |