Re: [PATCH 2/3] SConstruct: Use target_python when constructing extension name

[Ladislav Michl]

On Thu, Feb 06, 2020 at 07:38:09PM -0800, Gary E. Miller wrote:
> > x86_64-linux-gnu-gcc -pthread -o crc24q-py_3_7_6_final_0.so -c
> > -fno-strict-aliasing -Wdate-time
> > -fdebug-prefix-map=/build/python2.7-x6KfBw/python2.7-2.7.17=.
> > -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv
> > -O2 -Wall -Wstrict-prototypes -fPIC -D_FORTIFY_SOURCE=2 -DNDEBUG
> > -I/usr/include/python2.7 crc24q.c
> 
> You realize where those parameters came from?  Right?

Yes. Parameters, except crc24q-py_3_7_6_final_0.so are right.
I regret you (again) deleted context, so let me repeat it bellow.

> They came from your target_python, not from SCons.  Your target python
> was built weird.  Fix that.

All those options above _except_ "3_7_6_final_0" part of
crc24q-py_3_7_6_final_0.so are comming from target_python.
All those options are right. "3_7_6_final_0" is not as it is
comming from SCons Python.

For this example I decided not to cross-compile to make testing
easier for you. This is Debian, I guess there are Debian developers
reading this list. If you could point out in which way Debian's
python2.7 package is built weird, they (or perhaps myself) could
be able to fix that.

Thank you,
        ladis