[Slackbuilds-users] /usr/include/python3.7 or 3.7m ?

[Christoph Willing]

On 26/4/20 4:37 am, Dave Woodfall wrote:
> On 2020-04-24 22:42,
> Christoph Willing <chris.willing at linux.com> put forth the proposition:
>> On 24/4/20 10:30 pm, Dave Woodfall wrote:
>>> On 2020-04-24 13:24,
>>> Dave Woodfall <dave at slackbuilds.org> put forth the proposition:
>>>> On 2020-04-24 22:18,
>>>> Christoph Willing <chris.willing at linux.com> put forth the proposition:
>>>>> On 24/4/20 7:45 pm, Tim Dickson via SlackBuilds-users wrote:
>>>>>> i've a reasonable collection of python .sbo packages installed, and
>>>>>> sip.h is the only file in /usr/include/python3.7
>>>>>> which is from stock slackware 14.2 sip-4.18 package
>>>>>> Regards, Tim
>>>>>>
>>>>>
>>>>> Thanks all for the replies confirming the python3 include directories.
>>>>>
>>>>> Tim, I think you mean /usr/include/python2.7 for the sip.h from stock
>>>>> Slackware sip-4.18-x86_64-1 package?
>>>>>
>>>>> If you have a /usr/include/python3.7/sip.h (the one which should be in
>>>>> /usr/include/python3.7m) then it's from the SBo python3-sip SlackBuild.
>>>>>
>>>>> I emailed the maintainer a few days ago with a version-independent
>>>>> method to install in the correct location but haven't heard back about
>>>>> it yet (so cc'd here now as a reminder). I just thought I should also
>>>>> check here in case there was something whacky about my own setup but
>>>>> based on the feedback, as well as noticing that AlienBob's python3
>>>>> package uses /usr/include/python3.7m, I"m sure now that the problem is
>>>>> with the python3-sip SlackBuild. It looks very close to the SlackBuild
>>>>> in -current but of course -current uses python 3.8 where the issue has
>>>>> been fixed, rather than python 3.7 as on SBo.
>>>>>
>>>>> chris
>>>>
>>>> I maintain python3-sip now, so if we are all in agreement that we use
>>>> python3.7 I'll fix that this week.
>>>
>>> I got that the wrong way around.
>>>
>>> We're want to use /usr/include/python3.7m right?
>>>
>>
>> Yes Dave, that's correct.
>>
>> Although you could hard code it to python3.7m, I"d suggest a
>> version-independent mechanism like changing the existing line:
>>     -e "/usr/include/python$PYTHONVER" \
>> to:
>>     -e $(pkg-config --cflags-only-I python3 | sed -e 's/^-I//' ) \
>>
>> This uses pkg-config to find the "official" include path and strips the
>> leading '-I'. Then sip.h would be installed in the correct location
>> regardless of the python version.
>>
>> chris
> 
> I've changed both python3-sip and python3-PyQt5 to use that instead
> of hardcoding the paths in.  The only two applications that directly
> depend on python3-sip are python3-PyQt5 and wxPython4, which seems to
> build fine.
> 
> 

Looks good - will help pkgs which indirectly depend on it too (in my
case QScintilla-qt5 but maybe/probably others).

Thanks,
chris

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200426/3a68285e/attachment.asc>