In article <201609...@crcomp.net>, Don Kuenz wrote:
>
>The Doctor wrote:
>> In article <201609...@crcomp.net>, Don Kuenz wrote:
>>>
>>>It turns out that the question isn't "How to install Python.h?" The
>>>question is "Why doesn't make find Python.h?"
>>>
>>>---
The Doctor wrote:
> In article <201609...@crcomp.net>, Don Kuenz wrote:
>>
>>It turns out that the question isn't "How to install Python.h?" The
>>question is "Why doesn't make find Python.h?"
>>
>>
>>
>># uname -v
>>FreeBS
In article <201609...@crcomp.net>, Don Kuenz wrote:
>
>It turns out that the question isn't "How to install Python.h?" The
>question is "Why doesn't make find Python.h?"
>
>
>
># uname -v
>FreeBSD 10.0-RELEASE #0 r260789: Thu
It turns out that the question isn't "How to install Python.h?" The
question is "Why doesn't make find Python.h?"
# uname -v
FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014
# cd /
# find . -name 'Python.h'
/u
In article <201609...@crcomp.net>, Don Kuenz wrote:
>
>In article you wrote:
>> In article <201609...@crcomp.net>, Don Kuenz wrote:
>>>
>>>The installed python packages are shown below. Searches lead me to
>>>believe that a PTH option make play a role.
>>>
>>>--
In article you wrote:
> In article <201609...@crcomp.net>, Don Kuenz wrote:
>>
>>The installed python packages are shown below. Searches lead me to
>>believe that a PTH option make play a role.
>>
>>
>>$ uname -v
>>FreeBSD