Re: Compilation problem

2023-05-27 Thread Dr . Jürgen Sauermann 

Hi,

I had a closer look at this. It seems like the right way is to
rename 'python' to 'python3' in *m4/apl_TARGETs.m4*.

Fixed in *SVN 1697*.

Python is quite a mess when it comes to versioning.

Best Regards,
Jürgen


On 5/26/23 22:12, Peter Teeson wrote:

Hi Jürgen:
I put together a brief note for Mac devs wrt Python. Feel free to use 
it if you wish.



best regards
Peter

On May 26, 2023, at 11:03 AM, Dr. Jürgen Sauermann 
http://jrgen-sauermann-zvb.de>> wrote:


Hi Peter,

thanks, generally a good idea. I will look into that. Problem is that
even the "standard places" are not standard these days. Both *apl*
and *python* could live in  either /usr/include or else in 
/usr/local/include

and the ./configure of GNU APL can not easily figure how python was
installed.

It also seems like python does not have *pkg-config* support (which
would tell ./configure these things).

Also thanks for reminding me of *README-10-python*, I had
completely forgotten it.

Best Regards,
Juergen


On 5/25/23 21:11, Peter Teeson wrote:
Why not make a note in the python README for users to  make a 
_symbolic link _
from their actual python location to a _standard_ place such as 
/usr/include/python?

Then configure need only refer to that.


On May 25, 2023, at 5:34 AM, Dr. Jürgen Sauermann 
http://jrgen-sauermann-zvb.de/>> 
wrote:


actually:

*CXXFLAGS="-I /usr/include/python3.10" ./configure --with-python*


On 5/25/23 11:31, Dr. Jürgen Sauermann wrote:

Hi Emmanuel,

could you please translate the french error message to English?

No idea yet what this is about.

In the meantime it may help to copy Python.h from:
|/usr/include/python3.11/Python.h|
to:
|/usr/include/Python.h|

Or configure GNU APL like this:

*CXXFLAGS="-I /usr/include/python3.10" ./configure*

Best Regards,
Jürgen


On 5/24/23 22:45, Emmanuel Charpentier wrote:


Dear Jürgen,

TL,DR : I tried to recompile |gnu-apl| with the Python library, 
but got a compilation error :


|../../src/python_apl.cc :3:10: fatal 
error: Python.h: Aucun fichier ou dossier de ce type 3 | #include 
 | ^~ compilation terminated. |


Some details :

In a fresh |VPATH directory| I did :

|../configure --with-sqlite3 --with-gtk3 --with-python |

which ended with :

|configure:  SUMMARY OF TESTS (please include in error 
reports)  DEVELOP_WANTED: no ASSERT_LEVEL_WANTED: 1 
DYNAMIC_LOG_WANTED: no PERFORMANCE_COUNTERS_WANTED: no 
VALUE_CHECK_WANTED: no VALUE_HISTORY_WANTED: no 
apl_MAINTAINER_MODE: no apl_missing_headers: 0 
apl_missing_functions: 0 apl_FFT: yes (affects: ⎕FFT) apl_PCRE: 
yes (affects: ⎕RE) apl_PNG: yes (affects: ⎕PNG) apl_POSTGRES: yes 
(may affect: ⎕SQL) apl_SQLITE3: yes (may affect: ⎕SQL) apl_SQL 
yes (affects: ⎕SQL) apl_X11 (libxcb): yes (fallback for ⎕PLOT) 
apl_GTK3: yes (affects: ⎕PNG, ⎕GTK, maybe ⎕PLOT) apl_GUI: yes 
(affects: ⎕PNG, ⎕GTK, ⎕PLOT) |


but a compilation, launched by

|time make -j8 2>&1 | tee compilation.log |

failed. The error seems to be :

|libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../src -I.. -Wall 
-Wno-parentheses -I sql -I /home/charpent/Dev/apl/trunk/obj/.. 
-I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 
-I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/harfbuzz -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/x86_64-linux-gnu -I/usr/include/gio-unix-2.0 
-I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread 
-I/usr/include -I/usr/include/postgresql -DNDEBUG 
-D_FORTIFY_SOURCE=2 -fwrapv -fPIC -fstack-protector 
--param=ssp-buffer-size=4 -I/usr/include/python3.6m 
-I/usr/include/python3.8 -g -O2 -I 
/home/charpent/Dev/apl/trunk/obj -MT lib_gnu_apl_la-python_apl.lo 
-MD -MP -MF .deps/lib_gnu_apl_la-python_apl.Tpo -c 
../../src/python_apl.cc  -fPIC -DPIC -o 
.libs/lib_gnu_apl_la-python_apl.o ../../src/python_apl.cc 
:3:10: fatal error: Python.h: Aucun 
fichier ou dossier de ce type 3 | #include  | 
^~ compilation terminated. make[3]: *** [Makefile:2779 : 
lib_gnu_apl_la-python_apl.lo] Erreur 1 make[3]: *** Attente des 
tâches non terminées |


The curious thing is that |Python.h| /is/ present on my system :

|charpent@zen-book-flip:~/Dev/apl/trunk/obj$ locate Python.h 
locate: warning: database ‘/var/cache/locate/locatedb’ is more 
than 8 jours old (actual age is 30,1 jours) 
/usr/include/python3.11/Python.h 
/usr/share/doc/Macaulay2/Python/html/_to__Python.html 
charpent@zen-book-flip:~/Dev/apl/trunk/obj$ ls -l 
/usr/include/python3.11/Python.h -rw-r--r-- 1 root root 2854 13 
mars 13:18 /usr/include/python3.11/Python.h |


I might have to specify some library in an option to 
|../configure|, but can't figure out which.


My setup is

Re: Compilation problem

2023-05-26 Thread Dr . Jürgen Sauermann 

Hi Peter,

thanks, generally a good idea. I will look into that. Problem is that
even the "standard places" are not standard these days. Both *apl*
and *python* could live in  either /usr/include or else in 
/usr/local/include

and the ./configure of GNU APL can not easily figure how python was
installed.

It also seems like python does not have *pkg-config* support (which
would tell ./configure these things).

Also thanks for reminding me of *README-10-python*, I had
completely forgotten it.

Best Regards,
Juergen


On 5/25/23 21:11, Peter Teeson wrote:
Why not make a note in the python README for users to  make a 
_symbolic link _
from their actual python location to a _standard_ place such as 
/usr/include/python?

Then configure need only refer to that.


On May 25, 2023, at 5:34 AM, Dr. Jürgen Sauermann 
http://jrgen-sauermann-zvb.de>> wrote:


actually:

*CXXFLAGS="-I /usr/include/python3.10" ./configure --with-python*


On 5/25/23 11:31, Dr. Jürgen Sauermann wrote:

Hi Emmanuel,

could you please translate the french error message to English?

No idea yet what this is about.

In the meantime it may help to copy Python.h from:
|/usr/include/python3.11/Python.h|
to:
|/usr/include/Python.h|

Or configure GNU APL like this:

*CXXFLAGS="-I /usr/include/python3.10" ./configure*

Best Regards,
Jürgen


On 5/24/23 22:45, Emmanuel Charpentier wrote:


Dear Jürgen,

TL,DR : I tried to recompile |gnu-apl| with the Python library, but 
got a compilation error :


|../../src/python_apl.cc :3:10: fatal error: 
Python.h: Aucun fichier ou dossier de ce type 3 | #include 
 | ^~ compilation terminated. |


Some details :

In a fresh |VPATH directory| I did :

|../configure --with-sqlite3 --with-gtk3 --with-python |

which ended with :

|configure:  SUMMARY OF TESTS (please include in error reports) 
 DEVELOP_WANTED: no ASSERT_LEVEL_WANTED: 1 DYNAMIC_LOG_WANTED: 
no PERFORMANCE_COUNTERS_WANTED: no VALUE_CHECK_WANTED: no 
VALUE_HISTORY_WANTED: no apl_MAINTAINER_MODE: no 
apl_missing_headers: 0 apl_missing_functions: 0 apl_FFT: yes 
(affects: ⎕FFT) apl_PCRE: yes (affects: ⎕RE) apl_PNG: yes (affects: 
⎕PNG) apl_POSTGRES: yes (may affect: ⎕SQL) apl_SQLITE3: yes (may 
affect: ⎕SQL) apl_SQL yes (affects: ⎕SQL) apl_X11 (libxcb): yes 
(fallback for ⎕PLOT) apl_GTK3: yes (affects: ⎕PNG, ⎕GTK, maybe 
⎕PLOT) apl_GUI: yes (affects: ⎕PNG, ⎕GTK, ⎕PLOT) |


but a compilation, launched by

|time make -j8 2>&1 | tee compilation.log |

failed. The error seems to be :

|libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../src -I.. -Wall 
-Wno-parentheses -I sql -I /home/charpent/Dev/apl/trunk/obj/.. 
-I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 
-I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/harfbuzz -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/x86_64-linux-gnu -I/usr/include/gio-unix-2.0 
-I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread 
-I/usr/include -I/usr/include/postgresql -DNDEBUG 
-D_FORTIFY_SOURCE=2 -fwrapv -fPIC -fstack-protector 
--param=ssp-buffer-size=4 -I/usr/include/python3.6m 
-I/usr/include/python3.8 -g -O2 -I /home/charpent/Dev/apl/trunk/obj 
-MT lib_gnu_apl_la-python_apl.lo -MD -MP -MF 
.deps/lib_gnu_apl_la-python_apl.Tpo -c ../../src/python_apl.cc 
 -fPIC -DPIC -o 
.libs/lib_gnu_apl_la-python_apl.o ../../src/python_apl.cc 
:3:10: fatal error: Python.h: Aucun fichier 
ou dossier de ce type 3 | #include  | ^~ 
compilation terminated. make[3]: *** [Makefile:2779 : 
lib_gnu_apl_la-python_apl.lo] Erreur 1 make[3]: *** Attente des 
tâches non terminées |


The curious thing is that |Python.h| /is/ present on my system :

|charpent@zen-book-flip:~/Dev/apl/trunk/obj$ locate Python.h 
locate: warning: database ‘/var/cache/locate/locatedb’ is more than 
8 jours old (actual age is 30,1 jours) 
/usr/include/python3.11/Python.h 
/usr/share/doc/Macaulay2/Python/html/_to__Python.html 
charpent@zen-book-flip:~/Dev/apl/trunk/obj$ ls -l 
/usr/include/python3.11/Python.h -rw-r--r-- 1 root root 2854 13 
mars 13:18 /usr/include/python3.11/Python.h |


I might have to specify some library in an option to 
|../configure|, but can't figure out which.


My setup is Debian testing, used fairly often for development (I'm 
more or less in the Sagemath development group), with as little 
non-Debian software I can manage (two notorious exceptions : 
Zotero, which is a /sine qua non/ of my work) and, of course, 
Sagemath (built from my local |git| clone). And an armfull of |R| 
packages, which are probably quite irrelevant.


Logs attached (I hope).

--
Emmanuel Charpentier

Re: Compilation problem

2023-05-26 Thread Dr . Jürgen Sauermann 

Hi Emmanuel,

the VPATH stuff is not needed for normal mortals, it is just for me to build
multiple configurations in one go. Normally you do this (all in the 
top-level

directory):

1. fetch latest snapshot with subversion (*svn up*)
2. run *./configure* as discussed before
3. run *make* (should succeed). Not strictly required but recommended as 
to detect other faults.
4. run *make DEB* (should also succeed). The result is file 
*apl_1.8-1_amd64.deb*

in directory *debian_tmp* (and a few more).

Step 4 requires some additional packages like *debhelper*.

Hope this helps,
Jürgen


On 5/25/23 16:22, Emmanuel Charpentier wrote:
Never mind : I bit te bullet, installed `subversin` and skimmed a 
tutorial.


I got a functional tree, created a VPATH and obtained a full 
configuration/compilation.


Now to create a Debian package. The instructions aren't exeedingly 
blear, and `make DEB` does not seem to do what I expected it to do. 
Any hint ?


--
Emmanuel Charpentier


Le jeudi 25 mai 2023 à 14:39 +0200, Emmanuel Charpentier a écrit :


Le jeudi 25 mai 2023 à 13:49 +0200, Dr. Jürgen Sauermann a écrit :


Hi Emmanuel,

thanks. Seems like python_apl.cc was not compiled for a while.

Fixed in *SVN 1695*.


Thanks !

Do I need Subversion, or will the |git| mirror be updated in some 
'reasonable" time ?


(Yes, I'm aware of yur feelings towards |git|... Nut that's what 
Sagemath uses, with erious success...).


--
Emmanuel Charpentier

[ Snip... ]

Re: Compilation problem

2023-05-25 Thread Peter Teeson 
Why not make a note in the python README for users to  make a symbolic link 
from their actual python location to a standard place such as 
/usr/include/python?
Then configure need only refer to that.


> On May 25, 2023, at 5:34 AM, Dr. Jürgen Sauermann 
>  wrote:
> 
> actually:
> 
> CXXFLAGS="-I /usr/include/python3.10" ./configure --with-python
> 
> 
> On 5/25/23 11:31, Dr. Jürgen Sauermann wrote:
>> Hi Emmanuel,
>> 
>> could you please translate the french error message to English?
>> 
>> No idea yet what this is about.
>> 
>> In the meantime it may help to copy Python.h from:
>> /usr/include/python3.11/Python.h
>> to:
>> /usr/include/Python.h
>> 
>> Or configure GNU APL like this:
>> 
>> CXXFLAGS="-I /usr/include/python3.10" ./configure
>> 
>> Best Regards,
>> Jürgen
>> 
>> 
>> On 5/24/23 22:45, Emmanuel Charpentier wrote:
>>> Dear Jürgen,
>>> 
>>> TL,DR : I tried to recompile gnu-apl with the Python library, but got a 
>>> compilation error :
>>> 
>>> ../../src/python_apl.cc:3:10: fatal error: Python.h: Aucun fichier ou 
>>> dossier de ce type
>>> 3 | #include 
>>>   |  ^~
>>> compilation terminated.
>>> Some details :
>>> 
>>> In a fresh VPATH directory I did :
>>> 
>>> ../configure --with-sqlite3 --with-gtk3 --with-python
>>> which ended with :
>>> 
>>> configure: SUMMARY OF TESTS (please include in error reports) 
>>> 
>>> DEVELOP_WANTED:  no
>>> ASSERT_LEVEL_WANTED: 1
>>> DYNAMIC_LOG_WANTED:  no
>>> PERFORMANCE_COUNTERS_WANTED: no
>>> VALUE_CHECK_WANTED:  no
>>> VALUE_HISTORY_WANTED:no
>>> 
>>> apl_MAINTAINER_MODE: no
>>> apl_missing_headers: 0
>>> apl_missing_functions:   0
>>> apl_FFT: yes(affects: ⎕FFT)
>>> apl_PCRE:yes(affects: ⎕RE)
>>> apl_PNG: yes(affects: ⎕PNG)
>>> apl_POSTGRES:yes(may affect: ⎕SQL)
>>> apl_SQLITE3: yes(may affect: ⎕SQL)
>>> apl_SQL  yes(affects:⎕SQL)
>>> apl_X11 (libxcb):yes(fallback for   
>>> ⎕PLOT)
>>> apl_GTK3:yes(affects: ⎕PNG, ⎕GTK, maybe 
>>> ⎕PLOT)
>>> apl_GUI: yes(affects: ⎕PNG, ⎕GTK,   
>>> ⎕PLOT)
>>> but a compilation, launched by
>>> 
>>> time make -j8 2>&1 | tee compilation.log
>>> failed. The error seems to be :
>>> 
>>> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../src -I.. -Wall 
>>> -Wno-parentheses -I sql -I /home/charpent/Dev/apl/trunk/obj/.. 
>>> -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
>>> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
>>> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
>>> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
>>> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
>>> -I/usr/include/x86_64-linux-gnu -I/usr/include/gio-unix-2.0 
>>> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
>>> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
>>> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -I/usr/include 
>>> -I/usr/include/postgresql -DNDEBUG -D_FORTIFY_SOURCE=2 -fwrapv -fPIC 
>>> -fstack-protector --param=ssp-buffer-size=4 -I/usr/include/python3.6m 
>>> -I/usr/include/python3.8 -g -O2 -I /home/charpent/Dev/apl/trunk/obj -MT 
>>> lib_gnu_apl_la-python_apl.lo -MD -MP -MF 
>>> .deps/lib_gnu_apl_la-python_apl.Tpo -c ../../src/python_apl.cc  -fPIC -DPIC 
>>> -o .libs/lib_gnu_apl_la-python_apl.o
>>> ../../src/python_apl.cc:3:10: fatal error: Python.h: Aucun fichier ou 
>>> dossier de ce type
>>> 3 | #include 
>>>   |  ^~
>>> compilation terminated.
>>> make[3]: *** [Makefile:2779 : lib_gnu_apl_la-python_apl.lo] Erreur 1
>>> make[3]: *** Attente des tâches non terminées
>>> The curious thing is that Python.h is present on my system :
>>> 
>>> charpent@zen-book-flip:~/Dev/apl/trunk/obj$ locate Python.h
>>> locate: warning: database ‘/var/cache/locate/locatedb’ is more than 8 jours 
>>> old (actual age is 30,1 jours)
>>> /usr/include/python3.11/Python.h
>>> /usr/share/doc/Macaulay2/Python/html/_to__Python.html
>>> charpent@zen-book-flip:~/Dev/apl/trunk/obj$ ls -l 
>>> /usr/include/python3.11/Python.h
>>> -rw-r--r-- 1 root root 2854 13 mars  13:18 /usr/include/python3.11/Python.h
>>> I might have to specify some library in an option to ../configure, but 
>>> can't figure out which.
>>> 
>>> My setup is Debian testing, used fairly often for development (I'm more or 
>>> less in the Sagemath development group), with as little non-Debian software 
>>> I can manage (two notorious exceptions : Zotero, which is a sine qua non of 
>>> my work) and, of course, Sagemath (built from my local git clone). And an 
>>> armfull of R packages, which are probably quite irrelevant.
>>>

Re: Compilation problem

2023-05-25 Thread vvs 
On 5/25/23, Blake McBride  wrote:
> Although you addressed one of its many shortcomings, you conveniently
> failed to mention the others (e.g. complexity, central repo).  In terms of
> complexity, GIT is plenty simple in simple cases but quickly becomes
> unwieldy even for experts.

I've just stated the obvious. And I didn't mean to start a flame war.

Having said that, I can confirm that Git is complex piece of software.
As any non-trivial application sure is. If it would be really so
"unwieldy" then I doubt that Microsoft would buy such useless business
as GitHub.com with 100+ million customers (as they claim).

I really don't care much about which software I'm using as long as
it's useful. If most interesting projects would use Subversion I'd use
it instead. And they probably prefer Git because it has much to offer.
But that makes it more difficult to learn, of course.

That reminds me flame wars about Plan 9 vs. Linux. I actually admire
Plan 9 simplicity, but also admit that it's not very suitable for most
practical purposes. That's a life...

Re: Compilation problem

2023-05-25 Thread Blake McBride 
On Thu, May 25, 2023 at 8:47 AM vvs  wrote:

> On 5/25/23, Blake McBride  wrote:
> > Have a development project going on for several years with a fair-sized
> > team.  The code base grows immensely.  Git forces you to download the
> whole
> > damn thing - every change ever made.  No one wants that!  Sometimes it
> can
> > take more than an hour to clone a repo!  Subversion gives you the version
> > you want and lets you switch to a different version trivially.
>
> Sorry, but that's just not true. Just use --depth with appropriate
> number of last history commits to get only that much history. And it
> still allows you to commit your changes back. I always use it when I'm
> interested only in the project' latest source code.
>
> Another option would be to download repository snapshot archive (this
> depends on Git' hosting, but available on e.g. GitHub).
>
> Not that I'm surprised to see that people do biased judgement all the
> time. And not that I care much anyway.
>

Although you addressed one of its many shortcomings, you conveniently
failed to mention the others (e.g. complexity, central repo).  In terms of
complexity, GIT is plenty simple in simple cases but quickly becomes
unwieldy even for experts.

--blake

Re: Compilation problem

2023-05-25 Thread Emmanuel Charpentier 
Never mind : I bit te bullet, installed `subversin` and skimmed a
tutorial.

I got a functional tree, created a VPATH and obtained a full
configuration/compilation.

Now to create a Debian package. The instructions aren't exeedingly
blear, and `make DEB` does not seem to do what I expected it to do. Any
hint ?

--
Emmanuel Charpentier


Le jeudi 25 mai 2023 à 14:39 +0200, Emmanuel Charpentier a écrit :
> Le jeudi 25 mai 2023 à 13:49 +0200, Dr. Jürgen Sauermann a écrit :
> > Hi Emmanuel,
> > thanks. Seems like python_apl.cc was not compiled for a while.
> > Fixed in SVN 1695.
> Thanks !
> Do I need Subversion, or will the git mirror be updated in some
> 'reasonable" time ?
> (Yes, I'm aware of yur feelings towards git... Nut that's what
> Sagemath uses, with erious success...).
> --
> Emmanuel Charpentier
> [ Snip... ]

Re: Compilation problem

2023-05-25 Thread vvs 
On 5/25/23, Blake McBride  wrote:
> Have a development project going on for several years with a fair-sized
> team.  The code base grows immensely.  Git forces you to download the whole
> damn thing - every change ever made.  No one wants that!  Sometimes it can
> take more than an hour to clone a repo!  Subversion gives you the version
> you want and lets you switch to a different version trivially.

Sorry, but that's just not true. Just use --depth with appropriate
number of last history commits to get only that much history. And it
still allows you to commit your changes back. I always use it when I'm
interested only in the project' latest source code.

Another option would be to download repository snapshot archive (this
depends on Git' hosting, but available on e.g. GitHub).

Not that I'm surprised to see that people do biased judgement all the
time. And not that I care much anyway.

Re: Compilation problem

2023-05-25 Thread Blake McBride 
After 40 years of programming, I have to admit I am not smart enough to
understand GIT.  Yes, it works straightforwardly enough in simple cases.
But it is fairly common to get yourself tied up in a knot with GIT and
spend the entire day trying to straighten it out.  Several times I got
stuck and asked a few "git experts" I was working with.  90% of the time,
they tell me, yea, something is wrong.

For the vast majority of millions (?) of companies worldwide, they all have
a central repository.  GIT doesn't work that way.

Have a development project going on for several years with a fair-sized
team.  The code base grows immensely.  Git forces you to download the whole
damn thing - every change ever made.  No one wants that!  Sometimes it can
take more than an hour to clone a repo!  Subversion gives you the version
you want and lets you switch to a different version trivially.

I know GIT has taken the world by storm.  Without thinking, everyone wants
to use the cool stuff everyone else is using.  But GIT doesn't make sense
in nearly 100% of the case in the commercial world.

[rant off]

Blake McBride




On Thu, May 25, 2023 at 8:18 AM Dr. Jürgen Sauermann <
mail@jürgen-sauermann.de> wrote:

> Hi Emmanuel,
>
> I normally update git together with SVN. But: sometimes I forget
> to and I am not at all familiar with git. I get lots of error messages
> from git which I do not understand.
>
> Maybe some git specialist can have a look at the target SYNC:
> in the top-level Makefile.am and let me know what I am doing
> wrong?
>
> SVN is far more painless for everybody so I can only recommend
> to use it instead of git (command line SVN is perfect, no need for
> any SVN IDE.
>
> Best Regards,
> Jürgen
>
>
>
> On 5/25/23 14:39, Emmanuel Charpentier wrote:
>
> Le jeudi 25 mai 2023 à 13:49 +0200, Dr. Jürgen Sauermann a écrit :
>
> Hi Emmanuel,
>
> thanks. Seems like python_apl.cc was not compiled for a while.
>
> Fixed in *SVN 1695*.
>
> Thanks !
>
> Do I need Subversion, or will the git mirror be updated in some
> 'reasonable" time ?
>
> (Yes, I'm aware of yur feelings towards git... Nut that's what Sagemath
> uses, with erious success...).
>
> --
> Emmanuel Charpentier
>
> [ Snip... ]
>
>
>

Re: Compilation problem

2023-05-25 Thread Dr . Jürgen Sauermann 

Hi Emmanuel,

I normally update git together with SVN. But: sometimes I forget
to and I am not at all familiar with git. I get lots of error messages
from git which I do not understand.

Maybe some git specialist can have a look at the target SYNC:
in the top-level Makefile.am and let me know what I am doing
wrong?

SVN is far more painless for everybody so I can only recommend
to use it instead of git (command line SVN is perfect, no need for
any SVN IDE.

Best Regards,
Jürgen



On 5/25/23 14:39, Emmanuel Charpentier wrote:


Le jeudi 25 mai 2023 à 13:49 +0200, Dr. Jürgen Sauermann a écrit :


Hi Emmanuel,

thanks. Seems like python_apl.cc was not compiled for a while.

Fixed in *SVN 1695*.


Thanks !

Do I need Subversion, or will the |git| mirror be updated in some 
'reasonable" time ?


(Yes, I'm aware of yur feelings towards |git|... Nut that's what 
Sagemath uses, with erious success...).


--
Emmanuel Charpentier

[ Snip... ]

Re: Compilation problem

2023-05-25 Thread Emmanuel Charpentier 
Le jeudi 25 mai 2023 à 13:49 +0200, Dr. Jürgen Sauermann a écrit :

>  Hi Emmanuel,  
>
>  thanks. Seems like python_apl.cc was not compiled for a while.  
>
>  Fixed in **SVN 1695**.  

Thanks !

Do I need Subversion, or will the `git` mirror be updated in some 'reasonable" 
time ?

(Yes, I'm aware of yur feelings towards `git`... Nut that's what Sagemath uses, 
with erious success...).

--
Emmanuel Charpentier

[ Snip... ]

Re: Compilation problem

2023-05-25 Thread Dr . Jürgen Sauermann 

Hi Emmanuel,

thanks. Seems like python_apl.cc was not compiled for a while.

Fixed in *SVN 1695*.

Best Regards,
Jürgen


On 5/25/23 13:10, Emmanuel Charpentier wrote:


Le jeudi 25 mai 2023 à 11:34 +0200, Dr. Jürgen Sauermann a écrit :


CXXFLAGS="-I /usr/include/python3.10" ./configure --with-python

Thanks ! In a fresh |obj|, this (modulo |python.3.11| for me) got rid 
of the initial error. But I got another one :


|/bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. 
-I../../src -I.. -Wall -Wno-parentheses -I sql -I 
/home/charpent/Dev/apl/trunk/obj/.. -I/usr/include/gtk-3.0 
-I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
-I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi 
-I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-pthread -I/usr/include -I/usr/include/postgresql -DNDEBUG 
-D_FORTIFY_SOURCE=2 -fwrapv -fPIC -fstack-protector 
--param=ssp-buffer-size=4 -I/usr/include/python3.6m 
-I/usr/include/python3.8 -I /usr/include/python3.11 -I 
/home/charpent/Dev/apl/trunk/obj -MT 
sql/lib_gnu_apl_la-SqliteProvider.lo -MD -MP -MF 
sql/.deps/lib_gnu_apl_la-SqliteProvider.Tpo -c -o 
sql/lib_gnu_apl_la-SqliteProvider.lo `test -f 'sql/SqliteProvider.cc' 
|| echo '../../src/'`sql/SqliteProvider.cc ../../src/python_apl.cc: In 
function ‘PyObject* apl_exec(PyObject*, PyObject*)’: 
../../src/python_apl.cc:179:31: error: no matching function for call 
to ‘Command::process_line(UCS_string&)’ 179 | try { 
Command::process_line(line_ucs); } | ~^~ 
In file included from ../../src/python_apl.cc:5: 
../../src/Command.hh:46:16: note: candidate: ‘static void 
Command::process_line()’ 46 | static void process_line(); | 
^~~~ ../../src/Command.hh:46:16: note: candidate expects 0 
arguments, 1 provided ../../src/Command.hh:49:16: note: candidate: 
‘static void Command::process_line(UCS_string&, std::ostream*)’ 49 | 
static void process_line(UCS_string & line, ostream * out); | 
^~~~ ../../src/Command.hh:49:16: note: candidate expects 2 
arguments, 1 provided ../../src/python_apl.cc:200:50: error: 
incomplete type ‘StateIndicator’ used in nested name specifier 200 | 
const Error & err = StateIndicator::get_error(si); | ^ 
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../src -I.. -Wall 
-Wno-parentheses -I sql -I /home/charpent/Dev/apl/trunk/obj/.. 
-I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/harfbuzz -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-pthread -I/usr/include -I/usr/include/postgresql -DNDEBUG 
-D_FORTIFY_SOURCE=2 -fwrapv -fPIC -fstack-protector 
--param=ssp-buffer-size=4 -I/usr/include/python3.6m 
-I/usr/include/python3.8 -I /usr/include/python3.11 -I 
/home/charpent/Dev/apl/trunk/obj -MT 
sql/lib_gnu_apl_la-SqliteProvider.lo -MD -MP -MF 
sql/.deps/lib_gnu_apl_la-SqliteProvider.Tpo -c 
../../src/sql/SqliteProvider.cc -fPIC -DPIC -o 
sql/.libs/lib_gnu_apl_la-SqliteProvider.o make[3]: *** [Makefile:2779 
: lib_gnu_apl_la-python_apl.lo] Erreur 1 |


which seems of a different source...

Logs attached.

--
Emmanuel Charpentier

Re: Compilation problem

2023-05-25 Thread Dr . Jürgen Sauermann 

actually:

*CXXFLAGS="-I /usr/include/python3.10" ./configure --with-python*


On 5/25/23 11:31, Dr. Jürgen Sauermann wrote:

Hi Emmanuel,

could you please translate the french error message to English?

No idea yet what this is about.

In the meantime it may help to copy Python.h from:
|/usr/include/python3.11/Python.h|
to:
|/usr/include/Python.h|

Or configure GNU APL like this:

*CXXFLAGS="-I /usr/include/python3.10" ./configure*

Best Regards,
Jürgen


On 5/24/23 22:45, Emmanuel Charpentier wrote:


Dear Jürgen,

TL,DR : I tried to recompile |gnu-apl| with the Python library, but 
got a compilation error :


|../../src/python_apl.cc:3:10: fatal error: Python.h: Aucun fichier 
ou dossier de ce type 3 | #include  | ^~ 
compilation terminated. |


Some details :

In a fresh |VPATH directory| I did :

|../configure --with-sqlite3 --with-gtk3 --with-python |

which ended with :

|configure:  SUMMARY OF TESTS (please include in error reports) 
 DEVELOP_WANTED: no ASSERT_LEVEL_WANTED: 1 DYNAMIC_LOG_WANTED: no 
PERFORMANCE_COUNTERS_WANTED: no VALUE_CHECK_WANTED: no 
VALUE_HISTORY_WANTED: no apl_MAINTAINER_MODE: no apl_missing_headers: 
0 apl_missing_functions: 0 apl_FFT: yes (affects: ⎕FFT) apl_PCRE: yes 
(affects: ⎕RE) apl_PNG: yes (affects: ⎕PNG) apl_POSTGRES: yes (may 
affect: ⎕SQL) apl_SQLITE3: yes (may affect: ⎕SQL) apl_SQL yes 
(affects: ⎕SQL) apl_X11 (libxcb): yes (fallback for ⎕PLOT) apl_GTK3: 
yes (affects: ⎕PNG, ⎕GTK, maybe ⎕PLOT) apl_GUI: yes (affects: ⎕PNG, 
⎕GTK, ⎕PLOT) |


but a compilation, launched by

|time make -j8 2>&1 | tee compilation.log |

failed. The error seems to be :

|libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../src -I.. -Wall 
-Wno-parentheses -I sql -I /home/charpent/Dev/apl/trunk/obj/.. 
-I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/harfbuzz -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-pthread -I/usr/include -I/usr/include/postgresql -DNDEBUG 
-D_FORTIFY_SOURCE=2 -fwrapv -fPIC -fstack-protector 
--param=ssp-buffer-size=4 -I/usr/include/python3.6m 
-I/usr/include/python3.8 -g -O2 -I /home/charpent/Dev/apl/trunk/obj 
-MT lib_gnu_apl_la-python_apl.lo -MD -MP -MF 
.deps/lib_gnu_apl_la-python_apl.Tpo -c ../../src/python_apl.cc -fPIC 
-DPIC -o .libs/lib_gnu_apl_la-python_apl.o 
../../src/python_apl.cc:3:10: fatal error: Python.h: Aucun fichier ou 
dossier de ce type 3 | #include  | ^~ compilation 
terminated. make[3]: *** [Makefile:2779 : 
lib_gnu_apl_la-python_apl.lo] Erreur 1 make[3]: *** Attente des 
tâches non terminées |


The curious thing is that |Python.h| /is/ present on my system :

|charpent@zen-book-flip:~/Dev/apl/trunk/obj$ locate Python.h locate: 
warning: database ‘/var/cache/locate/locatedb’ is more than 8 jours 
old (actual age is 30,1 jours) /usr/include/python3.11/Python.h 
/usr/share/doc/Macaulay2/Python/html/_to__Python.html 
charpent@zen-book-flip:~/Dev/apl/trunk/obj$ ls -l 
/usr/include/python3.11/Python.h -rw-r--r-- 1 root root 2854 13 mars 
13:18 /usr/include/python3.11/Python.h |


I might have to specify some library in an option to |../configure|, 
but can't figure out which.


My setup is Debian testing, used fairly often for development (I'm 
more or less in the Sagemath development group), with as little 
non-Debian software I can manage (two notorious exceptions : Zotero, 
which is a /sine qua non/ of my work) and, of course, Sagemath (built 
from my local |git| clone). And an armfull of |R| packages, which are 
probably quite irrelevant.


Logs attached (I hope).

--
Emmanuel Charpentier

Re: Compilation problem

2023-05-25 Thread Dr . Jürgen Sauermann 

Hi Emmanuel,

could you please translate the french error message to English?

No idea yet what this is about.

In the meantime it may help to copy Python.h from:

|/usr/include/python3.11/Python.h|

to:

|/usr/include/Python.h|


Or configure GNU APL like this:

*CXXFLAGS="-I /usr/include/python3.10" ./configure*

Best Regards,
Jürgen


On 5/24/23 22:45, Emmanuel Charpentier wrote:


Dear Jürgen,

TL,DR : I tried to recompile |gnu-apl| with the Python library, but 
got a compilation error :


|../../src/python_apl.cc:3:10: fatal error: Python.h: Aucun fichier ou 
dossier de ce type 3 | #include  | ^~ compilation 
terminated. |


Some details :

In a fresh |VPATH directory| I did :

|../configure --with-sqlite3 --with-gtk3 --with-python |

which ended with :

|configure:  SUMMARY OF TESTS (please include in error reports) 
 DEVELOP_WANTED: no ASSERT_LEVEL_WANTED: 1 DYNAMIC_LOG_WANTED: no 
PERFORMANCE_COUNTERS_WANTED: no VALUE_CHECK_WANTED: no 
VALUE_HISTORY_WANTED: no apl_MAINTAINER_MODE: no apl_missing_headers: 
0 apl_missing_functions: 0 apl_FFT: yes (affects: ⎕FFT) apl_PCRE: yes 
(affects: ⎕RE) apl_PNG: yes (affects: ⎕PNG) apl_POSTGRES: yes (may 
affect: ⎕SQL) apl_SQLITE3: yes (may affect: ⎕SQL) apl_SQL yes 
(affects: ⎕SQL) apl_X11 (libxcb): yes (fallback for ⎕PLOT) apl_GTK3: 
yes (affects: ⎕PNG, ⎕GTK, maybe ⎕PLOT) apl_GUI: yes (affects: ⎕PNG, 
⎕GTK, ⎕PLOT) |


but a compilation, launched by

|time make -j8 2>&1 | tee compilation.log |

failed. The error seems to be :

|libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../src -I.. -Wall 
-Wno-parentheses -I sql -I /home/charpent/Dev/apl/trunk/obj/.. 
-I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/harfbuzz -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/fribidi -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-pthread -I/usr/include -I/usr/include/postgresql -DNDEBUG 
-D_FORTIFY_SOURCE=2 -fwrapv -fPIC -fstack-protector 
--param=ssp-buffer-size=4 -I/usr/include/python3.6m 
-I/usr/include/python3.8 -g -O2 -I /home/charpent/Dev/apl/trunk/obj 
-MT lib_gnu_apl_la-python_apl.lo -MD -MP -MF 
.deps/lib_gnu_apl_la-python_apl.Tpo -c ../../src/python_apl.cc -fPIC 
-DPIC -o .libs/lib_gnu_apl_la-python_apl.o 
../../src/python_apl.cc:3:10: fatal error: Python.h: Aucun fichier ou 
dossier de ce type 3 | #include  | ^~ compilation 
terminated. make[3]: *** [Makefile:2779 : 
lib_gnu_apl_la-python_apl.lo] Erreur 1 make[3]: *** Attente des tâches 
non terminées |


The curious thing is that |Python.h| /is/ present on my system :

|charpent@zen-book-flip:~/Dev/apl/trunk/obj$ locate Python.h locate: 
warning: database ‘/var/cache/locate/locatedb’ is more than 8 jours 
old (actual age is 30,1 jours) /usr/include/python3.11/Python.h 
/usr/share/doc/Macaulay2/Python/html/_to__Python.html 
charpent@zen-book-flip:~/Dev/apl/trunk/obj$ ls -l 
/usr/include/python3.11/Python.h -rw-r--r-- 1 root root 2854 13 mars 
13:18 /usr/include/python3.11/Python.h |


I might have to specify some library in an option to |../configure|, 
but can't figure out which.


My setup is Debian testing, used fairly often for development (I'm 
more or less in the Sagemath development group), with as little 
non-Debian software I can manage (two notorious exceptions : Zotero, 
which is a /sine qua non/ of my work) and, of course, Sagemath (built 
from my local |git| clone). And an armfull of |R| packages, which are 
probably quite irrelevant.


Logs attached (I hope).

--
Emmanuel Charpentier

Re: Compilation problem

2023-05-24 Thread Peter Teeson 
P.S to my previous post….

>
Apple has officially deprecated Python 2.7 in macOS Monterey 12.3. 
 The company is advising its developers to use an alternative programming 
language 
instead, such as Python 3, which, however, does not come preinstalled on 
macOS.Jan 28, 2022

>

Re: Compilation problem

2023-05-24 Thread Peter Teeson 
FWIW I also get the same error on macOS - been trying for days to hunt down 
problem but so far no answer. 

Looking at the ./configure code but am boggled by it and struggling to zone in 
on the correct area,
I work in Xcode so no idea what to use to dynamically debug/trace in Terminal

Gandalf:trunk pteeson$ ./configure --with-python
…..

configure: SUMMARY OF TESTS (please include in error reports) 

DEVELOP_WANTED:  no
ASSERT_LEVEL_WANTED: 1
DYNAMIC_LOG_WANTED:  no
PERFORMANCE_COUNTERS_WANTED: no
VALUE_CHECK_WANTED:  no
VALUE_HISTORY_WANTED:no

apl_MAINTAINER_MODE: no
apl_missing_headers: 3
apl_missing_functions:   0
apl_FFT: no (affects: ⎕FFT)
apl_PCRE:   (affects: ⎕RE)
apl_PNG: yes(affects: ⎕PNG)
apl_POSTGRES:no (may affect: ⎕SQL)
apl_SQLITE3: yes(may affect: ⎕SQL)
apl_SQL  yes(affects:⎕SQL)
apl_X11 (libxcb):no (fallback for   ⎕PLOT)
apl_GTK3:no (affects: ⎕PNG, ⎕GTK, maybe ⎕PLOT)
apl_GUI: no (affects: ⎕PNG, ⎕GTK,   ⎕PLOT)

=From the Make log===
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -Wall -I sql -I 
/Volumes/Data/GNUAPL-on-Mac-WS/GNUapl/trunk -I/usr/include -DNDEBUG 
-D_FORTIFY_SOURCE=2 -fwrapv -fPIC -fstack-protector --param=ssp-buffer-size=4 
-I/usr/include/python3.6m -I/usr/include/python3.8 -g -O2 -I 
/Volumes/Data/GNUAPL-on-Mac-WS/GNUapl/trunk -MT lib_gnu_apl_la-python_apl.lo 
-MD -MP -MF .deps/lib_gnu_apl_la-python_apl.Tpo -c python_apl.cc  -fno-common 
-DPIC -o .libs/lib_gnu_apl_la-python_apl.o
python_apl.cc:3:10: fatal error: 'Python.h' file not found
#include 
 ^~
1 error generated.
make[1]: *** [lib_gnu_apl_la-python_apl.lo] Error 1
make: *** [all-recursive] Error 1

 tracking down python3.8 -
../../Library/Frameworks/Python.framework/Versions/3.8/include/python3.8
../../Library/Frameworks/Python.framework/Headers 

> On May 24, 2023, at 4:45 PM, Emmanuel Charpentier  
> wrote:
> 
> Dear Jürgen,
> 
> TL,DR : I tried to recompile gnu-apl with the Python library, but got a 
> compilation error :
> 
> ../../src/python_apl.cc:3:10: fatal error: Python.h: Aucun fichier ou dossier 
> de ce type
> 3 | #include 
>   |  ^~
> compilation terminated.
> Some details :
> 
> In a fresh VPATH directory I did :
> 
> ../configure --with-sqlite3 --with-gtk3 --with-python
> which ended with :
> 
> configure: SUMMARY OF TESTS (please include in error reports) 
> 
> DEVELOP_WANTED:  no
> ASSERT_LEVEL_WANTED: 1
> DYNAMIC_LOG_WANTED:  no
> PERFORMANCE_COUNTERS_WANTED: no
> VALUE_CHECK_WANTED:  no
> VALUE_HISTORY_WANTED:no
> 
> apl_MAINTAINER_MODE: no
> apl_missing_headers: 0
> apl_missing_functions:   0
> apl_FFT: yes  (affects: ⎕FFT)
> apl_PCRE:yes  (affects: ⎕RE)
> apl_PNG: yes  (affects: ⎕PNG)
> apl_POSTGRES:yes  (may affect: ⎕SQL)
> apl_SQLITE3: yes  (may affect: ⎕SQL)
> apl_SQL  yes  (affects:⎕SQL)
> apl_X11 (libxcb):yes  (fallback for   ⎕PLOT)
> apl_GTK3:yes  (affects: ⎕PNG, ⎕GTK, maybe ⎕PLOT)
> apl_GUI: yes  (affects: ⎕PNG, ⎕GTK,   ⎕PLOT)
> but a compilation, launched by
> 
> time make -j8 2>&1 | tee compilation.log
> failed. The error seems to be :
> 
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../src -I.. -Wall 
> -Wno-parentheses -I sql -I /home/charpent/Dev/apl/trunk/obj/.. 
> -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount 
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/gio-unix-2.0 
> -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -pthread -I/usr/include 
> -I/usr/include/postgresql -DNDEBUG -D_FORTIFY_SOURCE=2 -fwrapv -fPIC 
> -fstack-protector --param=ssp-buffer-size=4 -I/usr/include/python3.6m 
> -I/usr/include/python3.8 -g -O2 -I /home/charpent/Dev/apl/trunk/obj -MT 
> lib_gnu_apl_la-python_apl.lo -MD -MP -MF .deps/lib_gnu_apl_la-python_apl.Tpo 
> -c ../../src/python_apl.cc  -fPIC -DPIC -o .libs/lib_gnu_apl_la-python_apl.o
> ../../src/python_apl.cc:3:10: fatal error: Python.h: Aucun fichier ou dossier 
> de ce type
>