date:20191128

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Antonio Juan

Thanks for your replies I'm using OSX Catalina 10.15.1,

Like I commented, I have gnu-apl installed with homebrew and it works well 
except for the Plot feature.

So it was a problem with X11 and GTK, for the X11 Lib I need Xquartz from 
https://www.xquartz.org/ 
This puts the X11 on /opt/X11, I also have this strange behavior, that I asked 
on stack overflow: 
https://stackoverflow.com/questions/59072106/do-not-understanig-mac-osx-x11 


Then I managed to Install Gtk with home-brew I installed gtk+ and gtk+3, like 
this:
https://stackoverflow.com/a/20114598/1900722

export PKG_CONFIG_PATH=/opt/X11/lib/pkgconfig
brew info gtk+3
gtk+3: stable 3.24.12 (bottled)

brew info gtk
gtk+: stable 2.24.32 (bottled), HEAD

https://stackoverflow.com/questions/20098862/how-to-install-gtk-on-osx-for-use-with-g-gcc-compiler

Anf during make I get this error:

g++ -DHAVE_CONFIG_H -I. -I..-Wall -I sql -Werror  -g -O2 -MT 
apl-Quad_PLOT.o -MD -MP -MF .deps/apl-Quad_PLOT.Tpo -c -o apl-Quad_PLOT.o `test 
-f 'Quad_PLOT.cc' || echo './'`Quad_PLOT.cc
Quad_PLOT.cc:79:1: error: control reaches end of non-void function
  [-Werror,-Wreturn-type]
}
^
1 error generated.
make[3]: *** [apl-Quad_PLOT.o] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

I hope that I could explain it.


> El 27 nov 2019, a las 16:48, Peter Teeson  escribió:
> 
> Hi:
> The Macintosh operating system used to be called OS X 
> Then it was renamed macOS. That was around the time Apple created a spin off 
> iOS for their mobile devices.
> 
> So these days people refer to the hardware as Macs (both desktop and laptop)
> And iPhone, iPad, iWatch for their mobile devices.
> 
> What make of Mac do you have? What version of macOS?
> 
> If you have questions I will try to help.
> 
> Peter
> 
>> On Nov 27, 2019, at 7:12 AM, Dr. Jürgen Sauermann 
>> http://jrgen-sauermann-zvb.de/>> wrote:
>> 
>> Hi,
>> 
>> there is a very nice description of how to install GNU APL on Macintosh 
>> written
>> by Peter Teeson. You can find in in the HOWTOs directory.
>> 
>> I don't know if Macintosh uses OSX, but Peters document is anyhow worthwhile 
>> reading.
>> 
>> BTW I have updated the ⎕PLOT error message to be more specific as to which 
>> library is missing.
>> 
>> Best Rgeards,
>> Jürgen Sauermann
>> 
>> 
>> On 11/27/19 12:32 PM, Antonio Juan wrote:
>>> Thanks; I need to completely read the GNU-APL DOC, sorry about that
>>> 
>>> You are right the problem is with the libxcb.
>>> 
>>> ⎕plot 1 2 3 4 5
>>> SYNTAX ERROR+
>>>   ⎕PLOT 1 2 3 4 5
>>>   ^
>>>   )MORE
>>> ⎕PLOT is not available because either no libxcb library was found on this
>>> system when GNU APL was compiled, or because it was disabled in ./configure.
>>> 
>>> Exist a tutorials for building gnu-apl in OSX
>>> 
>>> Thanks for your time
>>> 
>>> Toni 
>>> 
 El 26 nov 2019, a las 17:27, Dr. Jürgen Sauermann 
 mailto:m...@xn--jrgen-sauermann-zvb.de>> 
 escribió:
 
 Hi Toni,
 
 the + character after SYNTAX ERROR (or any other APL error) indicates that 
 there
 is more information available regarding that error. The additional 
 information
 can be displayed with command )MORE.
 
 I suspect that in this particular case libraries needed for plotting 
 (essentially libX11.so,
 libxcb.so, and libX11-xcb.so) were missing on the platform where GNU APL 
 was compiled
 (i.e. your own machine if you compiled from source or the build machine of 
 a package if
 you installed a binary package).
 
 For ⎕PLOT to work, you may need to compile the interpreter from source 
 with the required
 X libraries installed beforehand.
 
 Best Regards,
 Jürgen Sauermann
 
 
 On 11/26/19 2:27 PM, Antonio Juan wrote:
> Thanks for this awesome software. I have installed gnu plot 1.8 from brew 
> package. It works well, and good integration with emacs. So it is a good 
> environment for learning APL.
> 
> The only think is that when I try to plot I always get the following 
> error:
> 
>⎕PLOT 0 1 ¯1 2 ¯2 3 ¯3
> SYNTAX ERROR+
>   ⎕PLOT 0 1 ¯1 2 ¯2 3 ¯3
>   ^
> 
> I do not see anywhere, if is needed to load a workspace, or the needed 
> for some environment configuration during installation. So really I do 
> not know how to proceed.
> 
> Thanks for your time
> 
> Toni
> 
 
>>> 
>> 
>

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Dr . Jürgen Sauermann


  
  
Hi Antonio,
  
  I fixed the -Wreturn-type warning  in SVN 1206.
  
  Best Regards,
  Jürgen Sauermann


On 11/28/19 10:31 AM, Antonio Juan
  wrote:


  
  Thanks for your replies I'm using OSX Catalina 10.15.1,
  
  
  Like I commented, I have gnu-apl installed with
homebrew and it works well except for the Plot feature.
  
  
  So it was a problem with X11 and GTK, for the X11
Lib I need Xquartz from https://www.xquartz.org/
  This puts the X11 on /opt/X11, I also have this
strange behavior, that I asked on stack overflow: https://stackoverflow.com/questions/59072106/do-not-understanig-mac-osx-x11
  
  
  Then I managed to Install Gtk with home-brew I
installed gtk+ and gtk+3, like this:
  https://stackoverflow.com/a/20114598/1900722
  
  
  export PKG_CONFIG_PATH=/opt/X11/lib/pkgconfig
  
brew info gtk+3
gtk+3: stable 3.24.12 (bottled)
  
  
  
  
brew info gtk
gtk+: stable 2.24.32 (bottled), HEAD
  
  
  
  https://stackoverflow.com/questions/20098862/how-to-install-gtk-on-osx-for-use-with-g-gcc-compiler
  


Anf during make I get this error:



  g++ -DHAVE_CONFIG_H -I. -I..    -Wall -I sql -Werror    
 -g -O2 -MT apl-Quad_PLOT.o -MD -MP -MF
.deps/apl-Quad_PLOT.Tpo -c -o apl-Quad_PLOT.o `test -f 'Quad_PLOT.cc'
|| echo './'`Quad_PLOT.cc
  Quad_PLOT.cc:79:1: error:
control reaches end of non-void function
        [-Werror,-Wreturn-type]
  }
  ^
  1 error generated.
  make[3]: *** [apl-Quad_PLOT.o] Error 1
  make[2]: *** [all-recursive] Error 1
  make[1]: *** [all-recursive] Error 1
  make: *** [all] Error 2
  
  
  I hope that I could explain it.
  
  


  
El 27 nov 2019, a las 16:48, Peter Teeson 
  escribió:


  
  Hi:
The Macintosh operating system used to be
  called OS X 
Then it was renamed macOS. That was around
  the time Apple created a spin off iOS for their mobile
  devices.


So these days people refer to the hardware
  as Macs (both desktop and laptop)
And iPhone, iPad, iWatch for their mobile
  devices.


What make of Mac do you have? What version
  of macOS?


If you have questions I will try to help.


Peter

  

  On Nov 27, 2019, at 7:12 AM, Dr.
Jürgen Sauermann jrgen-sauermann-zvb.de>
wrote:
  
  


  Hi,

there is a very nice description of how to
install GNU APL on Macintosh written
by Peter Teeson. You can find in in the
HOWTOs directory.

I don't know if Macintosh uses OSX, but
Peters document is anyhow worthwhile
reading.

BTW I have updated the ⎕PLOT
error message to be more specific as to
which library is missing.

Best Rgeards,
Jürgen Sauermann

  
  On 11/27/19 12:32
PM, Antonio Juan wrote:
  
  

Thanks; I need to completely read the
GNU-APL DOC, sorry about that


You are right the problem is
  with the libxcb.



  ⎕plot 1 2 3 4 5
  SYNTAX ERROR+
        ⎕PLOT 1 2 3 4 5
        ^
        )MORE
  ⎕PLOT is not available

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Antonio Juan

Hi thanks, I thinks that will be important to put the output of this things:

➜ svn co http://svn.savannah.gnu.org/svn/apl/trunk gnu-apl
...
...
Agnu-apl/install-sh
Checked out revision 1206.

➜ export
PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig

➜ ./configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/local/bin/ggrep
checking for egrep... /usr/local/bin/ggrep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for a BSD-compatible install... /usr/local/bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking whether make supports nested variables... yes
checking dependency style of gcc... gcc3
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-apple-darwin19.0.0
checking host system type... x86_64-apple-darwin19.0.0
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/local/bin/gsed
checking for fgrep... /usr/local/bin/ggrep -F
checking for ld used by gcc...
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
checking if the linker
(/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld)
is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 196608
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-apple-darwin19.0.0 file names to
x86_64-apple-darwin19.0.0 format... func_convert_file_noop
checking how to convert x86_64-apple-darwin19.0.0 file names to toolchain
format... func_convert_file_noop
checking for
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for ar... ar
checking for archiver @FILE support... no
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking for dsymutil... dsymutil
checking for nmedit... nmedit
checking for lipo... lipo
checking for otool... otool
checking for otool64... no
checking for -single_module linker flag... yes
checking for -exported_symbols_list linker flag... yes
checking for -force_load linker flag... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking for gcc option to produce PIC... -fno-common -DPIC
checking if gcc PIC flag -fno-common -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker
(/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld)
supports shared libraries... yes
checking dynamic linker characteristics... darwin19.0.0 dyld
checking how to hardcode library paths into programs... immediate
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... yes
checking whether stripping libraries is possible... yes
checking if libtool

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Dr . Jürgen Sauermann

Hi Antonio,

that seems to be an incompatibility between the commonly used libs
and the Apple libs.
Nothing that I could (or should) do anything about in GNU APL. As
far as I can see you could
probably remove the POLLRDHUP without much harm so that the offending line
reads:

pfd.events = POLLIN;

Best Regards,
Jürgen

On 11/28/19 11:58 AM, Antonio Juan
wrote:

Hi thanks, I thinks that will be important to put the output of
this things:

➜ svn co http://svn.savannah.gnu.org/svn/apl/trunk
gnu-apl
...
...

A gnu-apl/install-sh
Checked out revision 1206.

➜ export
PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Dr . Jürgen Sauermann

Hi again,

another thing that you may want to check is that your config.h
(which is
generated by ./configure) contains the following lines:

/* Enable GNU
extensions on systems that have them. */
#ifndef _GNU_SOURCE
# define _GNU_SOURCE 1
#endif

Best Regards,
Jürgen

On 11/28/19 12:11 PM, Dr. Jürgen
Sauermann wrote:

Hi Antonio,

that seems to be an incompatibility between the commonly used
libs and the Apple libs.
Nothing that I could (or should) do anything about in GNU APL.
As far as I can see you could
probably remove the POLLRDHUP without much harm so that the offending
line reads:

pfd.events = POLLIN;

Best Regards,
Jürgen

On 11/28/19 11:58 AM, Antonio Juan
wrote:

Hi thanks, I thinks that will be important to put the output of
this things:

➜ svn co http://svn.savannah.gnu.org/svn/apl/trunk
gnu-apl
...
...

A gnu-apl/install-sh
Checked out revision 1206.

➜ export
PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Antonio Juan

Maybe could be useful the makefile

Makefile
Description: Binary data
El 28 nov 2019, a las 10:31, Antonio Juan escribió:Thanks for your replies I'm using OSX Catalina 10.15.1,Like I commented, I have gnu-apl installed with homebrew and it works well except for the Plot feature.So it was a problem with X11 and GTK, for the X11 Lib I need Xquartz from https://www.xquartz.org/This puts the X11 on /opt/X11, I also have this strange behavior, that I asked on stack overflow: https://stackoverflow.com/questions/59072106/do-not-understanig-mac-osx-x11Then I managed to Install Gtk with home-brew I installed gtk+ and gtk+3, like this:https://stackoverflow.com/a/20114598/1900722export PKG_CONFIG_PATH=/opt/X11/lib/pkgconfigbrew info gtk+3gtk+3: stable 3.24.12 (bottled)brew info gtkgtk+: stable 2.24.32 (bottled), HEADhttps://stackoverflow.com/questions/20098862/how-to-install-gtk-on-osx-for-use-with-g-gcc-compilerAnf during make I get this error:g++ -DHAVE_CONFIG_H -I. -I.. -Wall -I sql -Werror -g -O2 -MT apl-Quad_PLOT.o -MD -MP -MF .deps/apl-Quad_PLOT.Tpo -c -o apl-Quad_PLOT.o `test -f 'Quad_PLOT.cc' || echo './'`Quad_PLOT.ccQuad_PLOT.cc:79:1: error: control reaches end of non-void function [-Werror,-Wreturn-type]}^1 error generated.make[3]: *** [apl-Quad_PLOT.o] Error 1make[2]: *** [all-recursive] Error 1make[1]: *** [all-recursive] Error 1make: *** [all] Error 2I hope that I could explain it.El 27 nov 2019, a las 16:48, Peter Teeson escribió:Hi:The Macintosh operating system used to be called OS X Then it was renamed macOS. That was around the time Apple created a spin off iOS for their mobile devices.So these days people refer to the hardware as Macs (both desktop and laptop)And iPhone, iPad, iWatch for their mobile devices.What make of Mac do you have? What version of macOS?If you have questions I will try to help.PeterOn Nov 27, 2019, at 7:12 AM, Dr. Jürgen Sauermann jrgen-sauermann-zvb.de> wrote:

Hi,

there is a very nice description of how to install GNU APL on
Macintosh written
by Peter Teeson. You can find in in the HOWTOs directory.

I don't know if Macintosh uses OSX, but Peters document is anyhow
worthwhile reading.

BTW I have updated the ⎕PLOT error message to be more
specific as to which library is missing.

Best Rgeards,
Jürgen Sauermann

On 11/27/19 12:32 PM, Antonio Juan
wrote:

Thanks; I need to completely read the GNU-APL DOC, sorry about
that

You are right the problem is with the libxcb.

⎕plot 1 2 3 4 5
SYNTAX ERROR+
⎕PLOT 1 2 3 4 5
^
)MORE
⎕PLOT is not available because either no libxcb
library was found on this
system when GNU APL was compiled, or because it
was disabled in ./configure.

Exist a tutorials for building gnu-apl in OSX

Thanks for your time

Toni

El 26 nov 2019, a las 17:27, Dr. Jürgen
Sauermann
escribió:

Hi Toni,

the + character after SYNTAX ERROR (or any other APL error)
indicates that there
is more information available regarding that error. The
additional information
can be displayed with command )MORE.

I suspect that in this particular case libraries needed
for plotting (essentially libX11.so,
libxcb.so, and libX11-xcb.so) were missing on the
platform where GNU APL was compiled
(i.e. your own machine if you compiled from source or
the build machine of a package if
you installed a binary package).

For ⎕PLOT to work, you may need to
compile the interpreter from source with the required
X libraries installed beforehand.

Best Regards,
Jürgen Sauermann

On 11/26/19 2:27 PM,
Antonio Juan wrote:

Thanks for this awesome software. I have installed gnu plot 1.8 from brew package. It works well, and good integration with emacs. So it is a good environment for learning APL.

The only think is that when I try to plot I always get the following error:

⎕PLOT 0 1 ¯1 2 ¯2 3 ¯3
SYNTAX ERROR+
⎕PLOT 0 1 ¯1 2 ¯2 3 ¯3
^

I do not see anywhere, if is needed to load a workspace, or the needed for some environment configuration during installation. So really I do not know how to proceed.

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Antonio Juan

I have this lines

/* Enable GNU extensions on systems that have them.  */
#ifndef _GNU_SOURCE
# define _GNU_SOURCE 1
#endif

> El 28 nov 2019, a las 12:22, Dr. Jürgen Sauermann 
>  escribió:
> 
> Hi again,
> 
> another thing that you may want to check is that your config.h (which is
> generated by ./configure) contains the following lines:
> 
> /* Enable GNU extensions on systems that have them.  */
> #ifndef _GNU_SOURCE
> # define _GNU_SOURCE 1
> #endif
> 
> Best Regards,
> Jürgen
> 
> 
> On 11/28/19 12:11 PM, Dr. Jürgen Sauermann wrote:
>> Hi Antonio,
>> 
>> that seems to be an incompatibility between the commonly used libs and the 
>> Apple libs.
>> Nothing that I could (or should) do anything about in GNU APL. As far as I 
>> can see you could
>> probably remove the  POLLRDHUP without much harm so that the offending line 
>> reads:
>> 
>> pfd.events = POLLIN;
>> 
>> Best Regards,
>> Jürgen
>> 
>> 
>> On 11/28/19 11:58 AM, Antonio Juan wrote:
>>> Hi thanks, I thinks that will be important to put the output of this things:
>>> 
>>> ➜ svn co http://svn.savannah.gnu.org/svn/apl/trunk 
>>>  gnu-apl
>>> ...
>>> ...
>>> Agnu-apl/install-sh
>>> Checked out revision 1206.
>>> 
>>> ➜ export 
>>> PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig
>>> 
>>> ➜ ./configure
>>> checking for gcc... gcc
>>> checking whether the C compiler works... yes
>>> checking for C compiler default output file name... a.out
>>> checking for suffix of executables...
>>> checking whether we are cross compiling... no
>>> checking for suffix of object files... o
>>> checking whether we are using the GNU C compiler... yes
>>> checking whether gcc accepts -g... yes
>>> checking for gcc option to accept ISO C89... none needed
>>> checking whether gcc understands -c and -o together... yes
>>> checking how to run the C preprocessor... gcc -E
>>> checking for grep that handles long lines and -e... /usr/local/bin/ggrep
>>> checking for egrep... /usr/local/bin/ggrep -E
>>> checking for ANSI C header files... yes
>>> checking for sys/types.h... yes
>>> checking for sys/stat.h... yes
>>> checking for stdlib.h... yes
>>> checking for string.h... yes
>>> checking for memory.h... yes
>>> checking for strings.h... yes
>>> checking for inttypes.h... yes
>>> checking for stdint.h... yes
>>> checking for unistd.h... yes
>>> checking minix/config.h usability... no
>>> checking minix/config.h presence... no
>>> checking for minix/config.h... no
>>> checking whether it is safe to define __EXTENSIONS__... yes
>>> checking for a BSD-compatible install... /usr/local/bin/ginstall -c
>>> checking whether build environment is sane... yes
>>> checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p
>>> checking for gawk... gawk
>>> checking whether make sets $(MAKE)... yes
>>> checking for style of include used by make... GNU
>>> checking whether make supports nested variables... yes
>>> checking dependency style of gcc... gcc3
>>> checking whether to enable maintainer-specific portions of Makefiles... no
>>> checking build system type... x86_64-apple-darwin19.0.0
>>> checking host system type... x86_64-apple-darwin19.0.0
>>> checking how to print strings... printf
>>> checking for a sed that does not truncate output... /usr/local/bin/gsed
>>> checking for fgrep... /usr/local/bin/ggrep -F
>>> checking for ld used by gcc... 
>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
>>> checking if the linker 
>>> (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld)
>>>  is GNU ld... no
>>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>>> checking the name lister (/usr/bin/nm -B) interface... BSD nm
>>> checking whether ln -s works... yes
>>> checking the maximum length of command line arguments... 196608
>>> checking whether the shell understands some XSI constructs... yes
>>> checking whether the shell understands "+="... yes
>>> checking how to convert x86_64-apple-darwin19.0.0 file names to 
>>> x86_64-apple-darwin19.0.0 format... func_convert_file_noop
>>> checking how to convert x86_64-apple-darwin19.0.0 file names to toolchain 
>>> format... func_convert_file_noop
>>> checking for 
>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
>>>  option to reload object files... -r
>>> checking for objdump... objdump
>>> checking how to recognize dependent libraries... pass_all
>>> checking for dlltool... no
>>> checking how to associate runtime and link libraries... printf %s\n
>>> checking for g++... g++
>>> checking whether we are using the GNU C++ compiler... yes
>>> checking whether g++ accepts -g... yes
>>> checking dependency style of g++... gcc3
>>> checking for ar... ar
>>> checking for archiver @FILE support... no
>>> checking for strip... strip
>>> checking for ranlib... ranlib
>>>

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Dr . Jürgen Sauermann

Hi Juan,

I see. I have changed the code so that it checks if POLLRDHUP is
#defined.
SVN 1207.

Best Regards,
Jürgen

On 11/28/19 12:34 PM, Antonio Juan
wrote:

I have this lines

/* Enable GNU extensions on systems that have
them. */
#ifndef _GNU_SOURCE
# define _GNU_SOURCE 1
#endif

El 28 nov 2019, a las 12:22, Dr. Jürgen
Sauermann
escribió:

Hi again,

another thing that you may want to check is that your
config.h (which is
generated by ./configure) contains the following
lines:

/* Enable GNU extensions on systems that
have them. */
#ifndef _GNU_SOURCE
# define _GNU_SOURCE 1
#endif

Best Regards,
Jürgen

On 11/28/19 12:11 PM, Dr.
Jürgen Sauermann wrote:

Hi
Antonio,

that seems to be an incompatibility between the
commonly used libs and the Apple libs.
Nothing that I could (or should) do anything about
in GNU APL. As far as I can see you could
probably remove the POLLRDHUP
without much harm so that the offending line reads:

pfd.events
= POLLIN;

Best Regards,
Jürgen

On 11/28/19 11:58 AM,
Antonio Juan wrote:

Hi thanks, I thinks that will be important to put
the output of this things:

➜ svn co http://svn.savannah.gnu.org/svn/apl/trunk
gnu-apl
...
...

A gnu-apl/install-sh
Checked out revision 1206.

➜ export
PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Antonio Juan

Hi i will check,

The compilation ended, and done sudo make install, but I still have the same 
problem 

  ⎕PLOT 1 2 3 4 5
SYNTAX ERROR+
∩  ⎕PLOT 1 2 3 4 5
  ^
  )MORE
⎕PLOT is not available because one or more of its build prerequisites (in
particular libX11.so) was missing, or because it was explicitly
 disabled in ./configure.

But different from the first one, it was no libxcb library was found, I suspect 
that at this point I also need to change something in the configure in order to 
compile with X11
Which I get:
checking xcb/xcb.h usability... no
checking xcb/xcb.h presence... no
checking for xcb/xcb.h... no
checking X11/Xlib.h usability... no
checking X11/Xlib.h presence... no
checking for X11/Xlib.h... no
checking X11/Xlib-xcb.h usability... no
checking X11/Xlib-xcb.h presence... no
checking for X11/Xlib-xcb.h... no
checking X11/Xutil.h usability... no
checking X11/Xutil.h presence... no
checking for X11/Xutil.h... no

Thanks for your help



> El 28 nov 2019, a las 12:22, Dr. Jürgen Sauermann 
>  escribió:
> 
> Hi again,
> 
> another thing that you may want to check is that your config.h (which is
> generated by ./configure) contains the following lines:
> 
> /* Enable GNU extensions on systems that have them.  */
> #ifndef _GNU_SOURCE
> # define _GNU_SOURCE 1
> #endif
> 
> Best Regards,
> Jürgen
> 
> 
> On 11/28/19 12:11 PM, Dr. Jürgen Sauermann wrote:
>> Hi Antonio,
>> 
>> that seems to be an incompatibility between the commonly used libs and the 
>> Apple libs.
>> Nothing that I could (or should) do anything about in GNU APL. As far as I 
>> can see you could
>> probably remove the  POLLRDHUP without much harm so that the offending line 
>> reads:
>> 
>> pfd.events = POLLIN;
>> 
>> Best Regards,
>> Jürgen
>> 
>> 
>> On 11/28/19 11:58 AM, Antonio Juan wrote:
>>> Hi thanks, I thinks that will be important to put the output of this things:
>>> 
>>> ➜ svn co http://svn.savannah.gnu.org/svn/apl/trunk 
>>>  gnu-apl
>>> ...
>>> ...
>>> Agnu-apl/install-sh
>>> Checked out revision 1206.
>>> 
>>> ➜ export 
>>> PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig
>>> 
>>> ➜ ./configure
>>> checking for gcc... gcc
>>> checking whether the C compiler works... yes
>>> checking for C compiler default output file name... a.out
>>> checking for suffix of executables...
>>> checking whether we are cross compiling... no
>>> checking for suffix of object files... o
>>> checking whether we are using the GNU C compiler... yes
>>> checking whether gcc accepts -g... yes
>>> checking for gcc option to accept ISO C89... none needed
>>> checking whether gcc understands -c and -o together... yes
>>> checking how to run the C preprocessor... gcc -E
>>> checking for grep that handles long lines and -e... /usr/local/bin/ggrep
>>> checking for egrep... /usr/local/bin/ggrep -E
>>> checking for ANSI C header files... yes
>>> checking for sys/types.h... yes
>>> checking for sys/stat.h... yes
>>> checking for stdlib.h... yes
>>> checking for string.h... yes
>>> checking for memory.h... yes
>>> checking for strings.h... yes
>>> checking for inttypes.h... yes
>>> checking for stdint.h... yes
>>> checking for unistd.h... yes
>>> checking minix/config.h usability... no
>>> checking minix/config.h presence... no
>>> checking for minix/config.h... no
>>> checking whether it is safe to define __EXTENSIONS__... yes
>>> checking for a BSD-compatible install... /usr/local/bin/ginstall -c
>>> checking whether build environment is sane... yes
>>> checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p
>>> checking for gawk... gawk
>>> checking whether make sets $(MAKE)... yes
>>> checking for style of include used by make... GNU
>>> checking whether make supports nested variables... yes
>>> checking dependency style of gcc... gcc3
>>> checking whether to enable maintainer-specific portions of Makefiles... no
>>> checking build system type... x86_64-apple-darwin19.0.0
>>> checking host system type... x86_64-apple-darwin19.0.0
>>> checking how to print strings... printf
>>> checking for a sed that does not truncate output... /usr/local/bin/gsed
>>> checking for fgrep... /usr/local/bin/ggrep -F
>>> checking for ld used by gcc... 
>>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
>>> checking if the linker 
>>> (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld)
>>>  is GNU ld... no
>>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>>> checking the name lister (/usr/bin/nm -B) interface... BSD nm
>>> checking whether ln -s works... yes
>>> checking the maximum length of command line arguments... 196608
>>> checking whether the shell understands some XSI constructs... yes
>>> checking whether the shell understands "+="... yes
>>> checking how to convert x86_64-apple-darwin19.0.0 file names

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Antonio Juan

So I need to change

CXXFLAGS="-I /opt/X11" ./configure

With this I not get anything

I'm not sure where to point I have the X11 in my /opt/X11

export 
PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig

Thanks for your time

> El 28 nov 2019, a las 12:54, Dr. Jürgen Sauermann 
>  escribió:
> 
> Hi Antonio,
> 
> For X11 and friend to work you need two different things:
> 
> 1. header files, e.g. xcb.h, Xlib.h, etc.
> 2. library files, e.g. libxcb.so.1, libX11.so.6, etc.
> 
> These days libraries are often shipped in two different packages: one that
> contains only the (shared) libraries and the other package contains the
> corresponding header files. That second packages normally ends with "-dev".
> 
> For example (output from aptitude search libx11):
> 
> i   libx11-6- X11 client-side library
> i   libx11-dev  - X11 client-side library (development 
> headers)
> 
> In your case the ./configure script cannot find the header files which means 
> that either the  the -dev package
> was not installed, or they were installed in an unusual place. In the latter 
> case you can
> tell ./configure where else to look, for example:
> 
> CXXFLAGS = -I /usr/somewhere_else ./configure [other configure options...]
> 
> Best Regards,
> Jürgen Sauermann
> 
> 
> On 11/28/19 12:33 PM, Antonio Juan wrote:
>> Hi i will check,
>> 
>> The compilation ended, and done sudo make install, but I still have the same 
>> problem 
>> 
>>   ⎕PLOT 1 2 3 4 5
>> SYNTAX ERROR+
>> ∩  ⎕PLOT 1 2 3 4 5
>>   ^
>>   )MORE
>> ⎕PLOT is not available because one or more of its build prerequisites (in
>> particular libX11.so) was missing, or because it was explicitly
>>  disabled in ./configure.
>> 
>> But different from the first one, it was no libxcb library was found, I 
>> suspect that at this point I also need to change something in the configure 
>> in order to compile with X11
>> Which I get:
>> checking xcb/xcb.h usability... no
>> checking xcb/xcb.h presence... no
>> checking for xcb/xcb.h... no
>> checking X11/Xlib.h usability... no
>> checking X11/Xlib.h presence... no
>> checking for X11/Xlib.h... no
>> checking X11/Xlib-xcb.h usability... no
>> checking X11/Xlib-xcb.h presence... no
>> checking for X11/Xlib-xcb.h... no
>> checking X11/Xutil.h usability... no
>> checking X11/Xutil.h presence... no
>> checking for X11/Xutil.h... no
>> 
>> Thanks for your help
>> 
>> 
>> 
>>> El 28 nov 2019, a las 12:22, Dr. Jürgen Sauermann 
>>> mailto:m...@xn--jrgen-sauermann-zvb.de>> 
>>> escribió:
>>> 
>>> Hi again,
>>> 
>>> another thing that you may want to check is that your config.h (which is
>>> generated by ./configure) contains the following lines:
>>> 
>>> /* Enable GNU extensions on systems that have them.  */
>>> #ifndef _GNU_SOURCE
>>> # define _GNU_SOURCE 1
>>> #endif
>>> 
>>> Best Regards,
>>> Jürgen
>>> 
>>> 
>>> On 11/28/19 12:11 PM, Dr. Jürgen Sauermann wrote:
 Hi Antonio,
 
 that seems to be an incompatibility between the commonly used libs and the 
 Apple libs.
 Nothing that I could (or should) do anything about in GNU APL. As far as I 
 can see you could
 probably remove the  POLLRDHUP without much harm so that the offending 
 line reads:
 
 pfd.events = POLLIN;
 
 Best Regards,
 Jürgen
 
 
 On 11/28/19 11:58 AM, Antonio Juan wrote:
> Hi thanks, I thinks that will be important to put the output of this 
> things:
> 
> ➜ svn co http://svn.savannah.gnu.org/svn/apl/trunk 
>  gnu-apl
> ...
> ...
> Agnu-apl/install-sh
> Checked out revision 1206.
> 
> ➜ export 
> PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig
> 
> ➜ ./configure
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /usr/local/bin/ggrep
> checking for egrep... /usr/local/bin/ggrep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Dr . Jürgen Sauermann

Hi,

I would at least expect something like

CXXFLAGS="-I /opt/X11/include" ./configure

(if that is the directory where your header files live).

Best Regards,
Jürgen

On 11/28/19 1:05 PM, Antonio Juan
wrote:

So I need to change

CXXFLAGS="-I /opt/X11" ./configure

With this I not get anything

I'm not sure where to point I have the X11 in my
/opt/X11

export
PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig

Thanks for your time

El 28 nov 2019, a las 12:54, Dr. Jürgen
Sauermann
escribió:

Hi
Antonio,

For X11 and friend to work you need two different
things:

1. header files, e.g. xcb.h, Xlib.h,
etc.
2. library files, e.g. libxcb.so.1, libX11.so.6, etc.

These days libraries are often shipped in two
different packages: one that
contains only the (shared) libraries and the other
package contains the
corresponding header files. That second packages
normally ends with "-dev".

For example (output from aptitude search
libx11):

i libx11-6 -
X11 client-side library
i libx11-dev - X11
client-side library (development headers)

In your case the ./configure script
cannot find the header files which means that either
the the -dev package
was not installed, or they were installed in an
unusual place. In the latter case you can
tell ./configure where else to look,
for example:

CXXFLAGS = -I /usr/somewhere_else
./configure [other configure options...]

Best Regards,
Jürgen Sauermann

On 11/28/19 12:33 PM,
Antonio Juan wrote:

Hi i will check,

The compilation ended, and done sudo
make install, but I still have the same problem

⎕PLOT 1 2 3 4 5
SYNTAX ERROR+
∩ ⎕PLOT 1 2 3 4 5
^
)MORE
⎕PLOT is not available because one or
more of its build prerequisites (in
particular libX11.so) was missing, or
because it was explicitly
disabled in ./configure.

But different from the first one, it
was no libxcb library was found, I suspect that at
this point I also need to change something in the
configure in order to compile with X11
Which I get:
checking xcb/xcb.h usability... no
checking xcb/xcb.h presence... no
checking for xcb/xcb.h... no
checking X11/Xlib.h usability... no
checking X11/Xlib.h presence... no
checking for X11/Xlib.h... no
checking X11/Xlib-xcb.h usability...
no
checking X11/Xlib-xcb.h presence... no
checking for X11/Xlib-xcb.h... no
checking X11/Xutil.h usability... no
checking X11/Xutil.h presence... no
checking for X11/Xutil.h... no

Thanks for your help

El 28 nov 2019, a las 12:22, Dr.
Jürgen Sauermann
escribió:

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Dr . Jürgen Sauermann

Hi Antonio,

For X11 and friend to work you need two different things:

1. header files, e.g. xcb.h, Xlib.h, etc.
2. library files, e.g. libxcb.so.1, libX11.so.6, etc.

These days libraries are often shipped in two different packages:
one that
contains only the (shared) libraries and the other package
contains the
corresponding header files. That second packages normally ends
with "-dev".

For example (output from aptitude search libx11):

i
libx11-6 - X11 client-side library
i libx11-dev - X11 client-side library
(development headers)

In your case the ./configure script cannot find the
header files which means that either the the -dev package
was not installed, or they were installed in an unusual place. In
the latter case you can
tell ./configure where else to look, for example:

CXXFLAGS = -I
/usr/somewhere_else ./configure [other configure options...]

Best Regards,
Jürgen Sauermann

On 11/28/19 12:33 PM, Antonio Juan
wrote:

Hi i will check,

The compilation ended, and done sudo make install,
but I still have the same problem

⎕PLOT 1 2 3 4 5
SYNTAX ERROR+
∩ ⎕PLOT 1 2 3 4 5
^
)MORE
⎕PLOT is not available because one or more of its
build prerequisites (in
particular libX11.so) was missing, or because it
was explicitly
disabled in ./configure.

But different from the first one, it was no libxcb
library was found, I suspect that at this point I also need to
change something in the configure in order to compile with X11
Which I get:
checking xcb/xcb.h usability... no
checking xcb/xcb.h presence... no
checking for xcb/xcb.h... no
checking X11/Xlib.h usability... no
checking X11/Xlib.h presence... no
checking for X11/Xlib.h... no
checking X11/Xlib-xcb.h usability... no
checking X11/Xlib-xcb.h presence... no
checking for X11/Xlib-xcb.h... no
checking X11/Xutil.h usability... no
checking X11/Xutil.h presence... no
checking for X11/Xutil.h... no

Thanks for your help

El 28 nov 2019, a las 12:22, Dr. Jürgen
Sauermann
escribió:

Hi again,

another thing that you may want to check is that your
config.h (which is
generated by ./configure) contains the following
lines:

/* Enable GNU extensions on systems that
have them. */
#ifndef _GNU_SOURCE
# define _GNU_SOURCE 1
#endif

Best Regards,
Jürgen

On 11/28/19 12:11 PM, Dr.
Jürgen Sauermann wrote:

Hi
Antonio,

that seems to be an incompatibility between the
commonly used libs and the Apple libs.
Nothing that I could (or should) do anything about
in GNU APL. As far as I can see you could
probably remove the POLLRDHUP
without much harm so that the offending line reads:

pfd.events
= POLLIN;

Best Regards,
Jürgen

On 11/28/19 11:58 AM,
Antonio Juan wrote:

Hi thanks, I thinks that will be important to put
the output of this things:

➜ svn co http://svn.savannah.gnu.org/svn/apl/trunk
gnu-apl
...
...

A gnu-apl/install-sh
Checked out revision 1206.

➜ export
PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Antonio Juan

Compiled well again same error, on apl interpreter

This is the new configure output

checking xcb/xcb.h usability... yes
checking xcb/xcb.h presence... no
configure: WARNING: xcb/xcb.h: accepted by the compiler, rejected by the 
preprocessor!
configure: WARNING: xcb/xcb.h: proceeding with the compiler's result
checking for xcb/xcb.h... yes
checking X11/Xlib.h usability... yes
checking X11/Xlib.h presence... no
configure: WARNING: X11/Xlib.h: accepted by the compiler, rejected by the 
preprocessor!
configure: WARNING: X11/Xlib.h: proceeding with the compiler's result
checking for X11/Xlib.h... yes
checking X11/Xlib-xcb.h usability... yes
checking X11/Xlib-xcb.h presence... no
configure: WARNING: X11/Xlib-xcb.h: accepted by the compiler, rejected by the 
preprocessor!
configure: WARNING: X11/Xlib-xcb.h: proceeding with the compiler's result
checking for X11/Xlib-xcb.h... yes
checking X11/Xutil.h usability... yes
checking X11/Xutil.h presence... no
configure: WARNING: X11/Xutil.h: accepted by the compiler, rejected by the 
preprocessor!
configure: WARNING: X11/Xutil.h: proceeding with the compiler's result
checking for X11/Xutil.h... yes

> El 28 nov 2019, a las 13:21, Dr. Jürgen Sauermann 
>  escribió:
> 
> Hi,
> 
> I would at least expect something like
> 
>  CXXFLAGS="-I /opt/X11/include" ./configure
> 
> (if that is the directory where your header files live).
> 
> Best Regards,
> Jürgen
> 
> 
> On 11/28/19 1:05 PM, Antonio Juan wrote:
>> So I need to change
>> 
>> CXXFLAGS="-I /opt/X11" ./configure
>> 
>> With this I not get anything
>> 
>> I'm not sure where to point I have the X11 in my /opt/X11
>> 
>> export 
>> PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig
>> 
>> Thanks for your time
>> 
>>> El 28 nov 2019, a las 12:54, Dr. Jürgen Sauermann 
>>> mailto:m...@xn--jrgen-sauermann-zvb.de>> 
>>> escribió:
>>> 
>>> Hi Antonio,
>>> 
>>> For X11 and friend to work you need two different things:
>>> 
>>> 1. header files, e.g. xcb.h, Xlib.h, etc.
>>> 2. library files, e.g. libxcb.so.1, libX11.so.6, etc.
>>> 
>>> These days libraries are often shipped in two different packages: one that
>>> contains only the (shared) libraries and the other package contains the
>>> corresponding header files. That second packages normally ends with "-dev".
>>> 
>>> For example (output from aptitude search libx11):
>>> 
>>> i   libx11-6- X11 client-side library
>>> i   libx11-dev  - X11 client-side library (development 
>>> headers)
>>> 
>>> In your case the ./configure script cannot find the header files which 
>>> means that either the  the -dev package
>>> was not installed, or they were installed in an unusual place. In the 
>>> latter case you can
>>> tell ./configure where else to look, for example:
>>> 
>>> CXXFLAGS = -I /usr/somewhere_else ./configure [other configure options...]
>>> 
>>> Best Regards,
>>> Jürgen Sauermann
>>> 
>>> 
>>> On 11/28/19 12:33 PM, Antonio Juan wrote:
 Hi i will check,

 The compilation ended, and done sudo make install, but I still have the 
 same problem 

   ⎕PLOT 1 2 3 4 5
 SYNTAX ERROR+
 ∩  ⎕PLOT 1 2 3 4 5
   ^
   )MORE
 ⎕PLOT is not available because one or more of its build prerequisites (in
 particular libX11.so) was missing, or because it was explicitly
  disabled in ./configure.

 But different from the first one, it was no libxcb library was found, I 
 suspect that at this point I also need to change something in the 
 configure in order to compile with X11
 Which I get:
 checking xcb/xcb.h usability... no
 checking xcb/xcb.h presence... no
 checking for xcb/xcb.h... no
 checking X11/Xlib.h usability... no
 checking X11/Xlib.h presence... no
 checking for X11/Xlib.h... no
 checking X11/Xlib-xcb.h usability... no
 checking X11/Xlib-xcb.h presence... no
 checking for X11/Xlib-xcb.h... no
 checking X11/Xutil.h usability... no
 checking X11/Xutil.h presence... no
 checking for X11/Xutil.h... no

 Thanks for your help

> El 28 nov 2019, a las 12:22, Dr. Jürgen Sauermann 
>  > escribió:
> 
> Hi again,
> 
> another thing that you may want to check is that your config.h (which is
> generated by ./configure) contains the following lines:
> 
> /* Enable GNU extensions on systems that have them.  */
> #ifndef _GNU_SOURCE
> # define _GNU_SOURCE 1
> #endif
> 
> Best Regards,
> Jürgen
> 
> 
> On 11/28/19 12:11 PM, Dr. Jürgen Sauermann wrote:
>> Hi Antonio,
>> 
>> that seems to be an incompatibility between the commonly used libs and 
>> the Apple libs.
>> Nothing that I could (or should) do anything about in GNU APL. As far as 
>> I can see you could
>> probably

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Dr . Jürgen Sauermann

Hi,

so the headers are usable even though they don't exist.
Interesting platform
that you have there. In that situation I would (recursively) copy
the header files from
/opt/X11/include to /usr/include to make sure that they are found
by both the
preprocessor and the compiler. If I remember correctly then apple
does not
use the real g++ but a kind of emulation of it which might cause
this kind of
problems.

Also have a look at config.log after ./configure; it tells you how
the tests were compiled.

Best Regards,
Jürgen

On 11/28/19 1:42 PM, Antonio Juan
wrote:

Compiled well again same error, on apl interpreter

This is the new configure output

checking xcb/xcb.h usability... yes
checking xcb/xcb.h presence... no
configure: WARNING: xcb/xcb.h: accepted by the
compiler, rejected by the preprocessor!
configure: WARNING: xcb/xcb.h: proceeding with the
compiler's result
checking for xcb/xcb.h... yes
checking X11/Xlib.h usability... yes
checking X11/Xlib.h presence... no
configure: WARNING: X11/Xlib.h: accepted by the
compiler, rejected by the preprocessor!
configure: WARNING: X11/Xlib.h: proceeding with
the compiler's result
checking for X11/Xlib.h... yes
checking X11/Xlib-xcb.h usability... yes
checking X11/Xlib-xcb.h presence... no
configure: WARNING: X11/Xlib-xcb.h: accepted by
the compiler, rejected by the preprocessor!
configure: WARNING: X11/Xlib-xcb.h: proceeding
with the compiler's result
checking for X11/Xlib-xcb.h... yes
checking X11/Xutil.h usability... yes
checking X11/Xutil.h presence... no
configure: WARNING: X11/Xutil.h: accepted by the
compiler, rejected by the preprocessor!
configure: WARNING: X11/Xutil.h: proceeding with
the compiler's result
checking for X11/Xutil.h... yes

El 28 nov 2019, a las 13:21, Dr. Jürgen
Sauermann
escribió:

Hi,

I would at least expect something like

CXXFLAGS="-I /opt/X11/include" ./configure

(if that is the directory where your header files live).

Best Regards,
Jürgen

On 11/28/19 1:05 PM,
Antonio Juan wrote:

So I need to change

CXXFLAGS="-I /opt/X11" ./configure

With this I not get anything

I'm not sure where to point I have the
X11 in my /opt/X11

export
PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig

Thanks for your time

El 28 nov 2019, a las 12:54, Dr.
Jürgen Sauermann
escribió:

Hi Antonio,

For X11 and friend to work you need two
different things:

1. header files, e.g. xcb.h, Xlib.h, etc.
2. library files, e.g. libxcb.so.1,
libX11.so.6, etc.

These days libraries are often shipped in
two different packages: one that
contains only the (shared) libraries and
the other package contains the
corresponding header files. That second
packages normally ends with "-dev".

For example (output from aptitude
search libx11):

i
libx11-6

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Elias Mårtenson

There should be no need for that.

I haven't used OSX in some time, but the way it works is that you use the -
framework flag which points to the library you want to use. The framework
files contain both the libraries and the header files, and the compiler
will automatically find them.

On Thu, 28 Nov 2019, 23:03 Antonio Juan,  wrote:

> Sorry for another inconvenience but since catalina I cannot write to
> /usr/include
>
>
> /usr 
> ➜ sudo mkdir include
> mkdir: include: Read-only file system
>
> El 28 nov 2019, a las 14:06, Dr. Jürgen Sauermann <
> m...@xn--jrgen-sauermann-zvb.de> escribió:
>
> Hi,
>
> so the headers are usable even though they don't exist. Interesting
> platform
> that you have there. In that situation I would (recursively) copy the
> header files from
> /opt/X11/include to /usr/include to make sure that they are found by both
> the
> preprocessor and the compiler. If I remember correctly then apple does not
> use the real g++ but a kind of emulation of it which might cause this kind
> of
> problems.
>
> Also have a look at config.log after ./configure; it tells you how the
> tests were compiled.
>
> Best Regards,
> Jürgen
>
>
> On 11/28/19 1:42 PM, Antonio Juan wrote:
>
> Compiled well again same error, on apl interpreter
>
> This is the new configure output
>
> checking xcb/xcb.h usability... yes
> checking xcb/xcb.h presence... no
> configure: WARNING: xcb/xcb.h: accepted by the compiler, rejected by the
> preprocessor!
> configure: WARNING: xcb/xcb.h: proceeding with the compiler's result
> checking for xcb/xcb.h... yes
> checking X11/Xlib.h usability... yes
> checking X11/Xlib.h presence... no
> configure: WARNING: X11/Xlib.h: accepted by the compiler, rejected by the
> preprocessor!
> configure: WARNING: X11/Xlib.h: proceeding with the compiler's result
> checking for X11/Xlib.h... yes
> checking X11/Xlib-xcb.h usability... yes
> checking X11/Xlib-xcb.h presence... no
> configure: WARNING: X11/Xlib-xcb.h: accepted by the compiler, rejected by
> the preprocessor!
> configure: WARNING: X11/Xlib-xcb.h: proceeding with the compiler's result
> checking for X11/Xlib-xcb.h... yes
> checking X11/Xutil.h usability... yes
> checking X11/Xutil.h presence... no
> configure: WARNING: X11/Xutil.h: accepted by the compiler, rejected by the
> preprocessor!
> configure: WARNING: X11/Xutil.h: proceeding with the compiler's result
> checking for X11/Xutil.h... yes
>
>
>
> El 28 nov 2019, a las 13:21, Dr. Jürgen Sauermann <
> m...@xn--jrgen-sauermann-zvb.de> escribió:
>
> Hi,
>
> I would at least expect something like
>
>  CXXFLAGS="-I /opt/X11/include" ./configure
>
> (if that is the directory where your header files live).
>
> Best Regards,
> Jürgen
>
>
> On 11/28/19 1:05 PM, Antonio Juan wrote:
>
> So I need to change
>
> CXXFLAGS="-I /opt/X11" ./configure
>
> With this I not get anything
>
> I'm not sure where to point I have the X11 in my /opt/X11
>
> export
> PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig
>
> Thanks for your time
>
> El 28 nov 2019, a las 12:54, Dr. Jürgen Sauermann <
> m...@xn--jrgen-sauermann-zvb.de> escribió:
>
> Hi Antonio,
>
> For X11 and friend to work you need two different things:
>
> 1. header files, e.g. xcb.h, Xlib.h, etc.
> 2. library files, e.g. libxcb.so.1, libX11.so.6, etc.
>
> These days libraries are often shipped in two different packages: one that
> contains only the (shared) libraries and the other package contains the
> corresponding header files. That second packages normally ends with "-dev".
>
> For example (output from *aptitude search libx11*):
>
>
>
> *i   libx11-6- X11 client-side library i
> libx11-dev  - X11 client-side library (development
> headers) *
> In your case the *./configure *script cannot find the header files which
> means that either the  the -dev package
> was not installed, or they were installed in an unusual place. In the
> latter case you can
> tell *./configure* where else to look, for example:
>
> *CXXFLAGS = -I /usr/somewhere_else ./configure [other configure
> options...]*
>
> Best Regards,
> Jürgen Sauermann
>
>
> On 11/28/19 12:33 PM, Antonio Juan wrote:
>
> Hi i will check,
>
> The compilation ended, and done sudo make install, but I still have the
> same problem
>
>   ⎕PLOT 1 2 3 4 5
> SYNTAX ERROR+
> ∩  ⎕PLOT 1 2 3 4 5
>   ^
>   )MORE
> ⎕PLOT is not available because one or more of its build prerequisites (in
> particular libX11.so) was missing, or because it was explicitly
>  disabled in ./configure.
>
> But different from the first one, it was no libxcb library was found, I
> suspect that at this point I also need to change something in the configure
> in order to compile with X11
> Which I get:
> checking xcb/xcb.h usability... no
> checking xcb/xcb.h presence... no
> checking for xcb/xcb.h... no
> checking X11/Xlib.h usability... no
> checking X11/Xlib.h presence... no
> ch

Re: Doubt about plotting on MAC OS X Catalina

2019-11-28 Thread Elias Mårtenson

There is no ldf on OSX if I'm not mistaken. I think you have to use otool.

Do note that OSX doesn't behave much like a Unix, and newer version are
even more limited.

You probably need to add the correct compiler flags manually since its
possible autotools doesn't handle it right.

On Thu, 28 Nov 2019, 23:45 Dr. Jürgen Sauermann, 
wrote:

> Hi,
>
> try:
>
> *ldd apl*
>
> in the src directory to see if the apl binary find all its libraries. If
> not then you
> need to configure and run ldconfig to tell the dynamic linker the place
> where
> the shared libraries can be found. This is fairly platform dependant. It
> has no
> relation to the header files (they are no longer needed after successful
> compilation).
>
> Best Regards,
> Jürgen Sauermann
>
>
> On 11/28/19 4:00 PM, Antonio Juan wrote:
>
> I will try that
> I Have tried this.
> LIBRARY_PATH=/opt/X11/lib:$LIBRARY_PATH CPPFLAGS="-I/opt/X11/include"
> LDFLAGS="-L/opt/X11/lib" ./configure
>
> Compiled and it worked finally de interpreter can find the X11 but now
> giving a segmentation fault:
>
>   ⎕PLOT 1 2 3 4
> 123145462255616
>
>
> ===
> SEGMENTATION FAULT
>
> 
> -- Stack trace at main.cc:88
> 
> 0x0 
> 0xA  
> 0x0   
> 0x0
> 0xA 
> 
> 
>
> Goodbye.
> Session duration: 7.84882 seconds
>
> Process apl<1> exited abnormally with code 3
>
> Do you thing that adding the include files will help?
>
> El 28 nov 2019, a las 15:56, Dr. Jürgen Sauermann <
> m...@xn--jrgen-sauermann-zvb.de> escribió:
>
> Hi,
>
> too bad. How about /usr/local/include (and a bit olf luck that g++ knows
> it) ?
>
> Best Regards,
> Jürgen
>
>
> On 11/28/19 3:08 PM, Antonio Juan wrote:
>
> Sorry for another inconvenience but since catalina I cannot write to
> /usr/include
>
>
> /usr 
> ➜ sudo mkdir include
> mkdir: include: Read-only file system
>
> El 28 nov 2019, a las 14:06, Dr. Jürgen Sauermann <
> m...@xn--jrgen-sauermann-zvb.de> escribió:
>
> Hi,
>
> so the headers are usable even though they don't exist. Interesting
> platform
> that you have there. In that situation I would (recursively) copy the
> header files from
> /opt/X11/include to /usr/include to make sure that they are found by both
> the
> preprocessor and the compiler. If I remember correctly then apple does not
> use the real g++ but a kind of emulation of it which might cause this kind
> of
> problems.
>
> Also have a look at config.log after ./configure; it tells you how the
> tests were compiled.
>
> Best Regards,
> Jürgen
>
>
> On 11/28/19 1:42 PM, Antonio Juan wrote:
>
> Compiled well again same error, on apl interpreter
>
> This is the new configure output
>
> checking xcb/xcb.h usability... yes
> checking xcb/xcb.h presence... no
> configure: WARNING: xcb/xcb.h: accepted by the compiler, rejected by the
> preprocessor!
> configure: WARNING: xcb/xcb.h: proceeding with the compiler's result
> checking for xcb/xcb.h... yes
> checking X11/Xlib.h usability... yes
> checking X11/Xlib.h presence... no
> configure: WARNING: X11/Xlib.h: accepted by the compiler, rejected by the
> preprocessor!
> configure: WARNING: X11/Xlib.h: proceeding with the compiler's result
> checking for X11/Xlib.h... yes
> checking X11/Xlib-xcb.h usability... yes
> checking X11/Xlib-xcb.h presence... no
> configure: WARNING: X11/Xlib-xcb.h: accepted by the compiler, rejected by
> the preprocessor!
> configure: WARNING: X11/Xlib-xcb.h: proceeding with the compiler's result
> checking for X11/Xlib-xcb.h... yes
> checking X11/Xutil.h usability... yes
> checking X11/Xutil.h presence... no
> configure: WARNING: X11/Xutil.h: accepted by the compiler, rejected by the
> preprocessor!
> configure: WARNING: X11/Xutil.h: proceeding with the compiler's result
> checking for X11/Xutil.h... yes
>
>
>
> El 28 nov 2019, a las 13:21, Dr. Jürgen Sauermann <
> m...@xn--jrgen-sauermann-zvb.de> escribió:
>
> Hi,
>
> I would at least expect something like
>
>  CXXFLAGS="-I /opt/X11/include" ./configure
>
> (if that is the directory where your header files live).
>
> Best Regards,
> Jürgen
>
>
> On 11/28/19 1:05 PM, Antonio Juan wrote:
>
> So I need to change
>
> CXXFLAGS="-I /opt/X11" ./configure
>
> With this I not get anything
>
> I'm not sure where to point I have the X11 in my /opt/X11
>
> export
> PKG_CONFIG_PATH=/usr/local/Cellar/gtk+/2.24.32_3/lib/pkgconfig:/opt/X11/lib/pkgconfig:/usr/local/Cellar/cairo/1.16.0_2/lib/pkgconfig
>
> Thanks for your time
>
> El 28 nov 2019, a las 12:54, Dr. Jürgen Sauermann <
> m...@xn--jrgen-sauermann-zvb.de> escribió:
>
> Hi Antonio,
>
> For X11 and friend to work you need two different things:
>
> 1. header files, e.g. xcb.h, Xlib.h, etc.
> 2. library files, e.g. libxcb.so.1, libX11.so.6, etc.
>
> These days libraries are often shipped in two different packages: one that
> c

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

Re: Doubt about plotting on MAC OS X Catalina

16 matches

Site Navigation

Mail list logo

Footer information