Message76596
When using bdist_rpm the %build section of the generated spec file
contains the following:
env CFLAGS="$RPM_OPT_FLAGS" python setup.py build
This works fine until the python is installed using altinstall. In this
situation the spec file will use the default python rather than the one
currently used.
I am currently using python3.0 with the default python being 2.5. As a
result the spec file is created which then calles python (2.5) and my
setup.py contains 3.0 code so the spec file fails.
When the above line is generated it should use the current interpreters
path and name rather than just "python" |
|
Date |
User |
Action |
Args |
2008-11-29 14:42:31 | John5342 | set | recipients:
+ John5342 |
2008-11-29 14:42:31 | John5342 | set | messageid: <1227969751.28.0.990351219395.issue4459@psf.upfronthosting.co.za> |
2008-11-29 14:42:30 | John5342 | link | issue4459 messages |
2008-11-29 14:42:29 | John5342 | create | |
|