[Bug-apl] GNU APL port for OpenBSD

Discussion:

Giuseppe Cocomazzi

2017-08-28 08:44:58 UTC

Hi list,
I have ported GNU APL to the OpenBSD operating system, and I kindly ask
you to consider the possibility of merging the following changes to the
source tree, in order to enable a better support for the OS. As you can
see, only few lines are needed.

Also, I recollected some info about the steps needed to configure
the environment (fonts, keyboard), not necessarily addressed
at users of this OS but of any Unix-like system in general:

http://sbudella.altervista.org/blog/20170821-apl-openbsd.html

And here are the two patches:

--- configure.orig Fri Mar 17 16:03:06 2017
+++ configure Mon Jul 17 17:11:15 2017
@@ -21413,7 +21413,7 @@ echo
#
echo "configure: creating $srcdir/src//buildtag.hh"
rm -f $srcdir/src/buildtag.hh
-cd $srcdir/src ; source ./buildtag ; cd ..
+cd $srcdir/src ; . ./buildtag ; cd ..

# create src/makefile.h
#

--- src/Common.cc.orig Fri Mar 17 15:46:53 2017
+++ src/Common.cc Mon Jul 17 16:37:56 2017
@@ -81,6 +81,11 @@ void
init_1(const char * argv0, bool log_startup)
{
rlimit rl;
+
+#ifndef RLIMIT_AS
+# define RLIMIT_AS RLIMIT_DATA
+#endif
+
getrlimit(RLIMIT_AS, &rl);
total_memory = rl.rlim_cur;

--
Giuseppe Cocomazzi
My self is steam

http://sbudella.altervista.org

Juergen Sauermann

2017-08-28 13:09:22 UTC

Permalink

<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Giuseppe, 
 
thanks for submitting the patches. I have included them into SVN
1001. 
 
The first patch is now in Makefile.am as opposed to configure.
That suggests that you 
are using an older version of the GNU APL sources. Maybe the one
from the GNU APL 
home page at gnu.org or a gnu mirror. The "official" GNU
APL releases happen quite 
rarely (like every one or two years) and therefore they quickly
become outdated. If you 
are porting GNU APL then it is better to check out the latest
version from SVN. 
 
Regarding your web link below, I wonder how persistent it is? If
the link is supposed to 
last for a longer period, then we could point to it from out community
web page 
<a href="http://www.gnu.org/software/apl/Community.html">http://www.gnu.org/software/apl/Community.html</a>
and/or mention it in our README-6-porting 
file. 
 
Best Regards, 
/// Jürgen Sauermann 
 
 
<div class="moz-cite-prefix">On 08/28/2017 10:44 AM, Giuseppe
Cocomazzi wrote: 
</div>
<blockquote
cite="mid:CA+ObNtY99xsSsVc0_e17YoH8qTeoV6W1n3B2AW_azU-***@mail.gmail.com"
type="cite">
<pre wrap="">Hi list,
I have ported GNU APL to the OpenBSD operating system, and I kindly ask
you to consider the possibility of merging the following changes to the
source tree, in order to enable a better support for the OS. As you can
see, only few lines are needed.

Also, I recollected some info about the steps needed to configure
the environment (fonts, keyboard), not necessarily addressed
at users of this OS but of any Unix-like system in general:

<a class="moz-txt-link-freetext" href="http://sbudella.altervista.org/blog/20170821-apl-openbsd.html">http://sbudella.altervista.org/blog/20170821-apl-openbsd.html</a>

And here are the two patches:

--- configure.orig Fri Mar 17 16:03:06 2017
+++ configure Mon Jul 17 17:11:15 2017
@@ -21413,7 +21413,7 @@ echo
#
echo "configure: creating $srcdir/src//buildtag.hh"
rm -f $srcdir/src/buildtag.hh
-cd $srcdir/src ; source ./buildtag ; cd ..
+cd $srcdir/src ; . ./buildtag ; cd ..

# create src/makefile.h
#

--- src/Common.cc.orig Fri Mar 17 15:46:53 2017
+++ src/Common.cc Mon Jul 17 16:37:56 2017
@@ -81,6 +81,11 @@ void
init_1(const char * argv0, bool log_startup)
{
rlimit rl;
+
+#ifndef RLIMIT_AS
+# define RLIMIT_AS RLIMIT_DATA
+#endif
+
getrlimit(RLIMIT_AS, &rl);
total_memory = rl.rlim_cur;

--
Giuseppe Cocomazzi
My self is steam

<a class="moz-txt-link-freetext" href="http://sbudella.altervista.org">http://sbudella.altervista.org</a>

</pre>
</blockquote>
 
</body>
</html>

Giuseppe Cocomazzi

2017-08-28 18:22:04 UTC

Permalink

Hi Jürgen,
thanks for your reply.
Ported software on OpenBSD is submitted for inclusion in the so-called
"port tree", basically a set of custom Makefiles by means of which
ports can be automatically downloaded, built, packaged and installed
with a single "make" command. The port tree is part of the operating
system, and importing rolling releases from SVN is not an option.
Therefore, the official releases on the GNU mirrors are perfectly fine
for the goal. Furthermore, I feel more comfortable in submitting
stable and mature releases, as another goal of the OS is stability,
security and cleanliness.

As I am also the maintainer of the port/package, I will update the
port's Makefile every time a major release is announced.

As for the link to my blog/notebook, I have been actively maintaining
my homepage for 8 years, my hosting service is quite stable and I have
intention to keep the page away from oblivion. I think then it is
reasonably safe to refer to it.

Thank you very much.

On Mon, Aug 28, 2017 at 3:09 PM, Juergen Sauermann

Post by Juergen Sauermann
Hi Giuseppe,
thanks for submitting the patches. I have included them into SVN 1001.
The first patch is now in Makefile.am as opposed to configure. That suggests
that you
are using an older version of the GNU APL sources. Maybe the one from the
GNU APL
home page at gnu.org or a gnu mirror. The "official" GNU APL releases happen
quite
rarely (like every one or two years) and therefore they quickly become
outdated. If you
are porting GNU APL then it is better to check out the latest version from
SVN.
Regarding your web link below, I wonder how persistent it is? If the link is
supposed to
last for a longer period, then we could point to it from out community web
page
http://www.gnu.org/software/apl/Community.html and/or mention it in our
README-6-porting
file.
Best Regards,
/// Jürgen Sauermann
Hi list,
I have ported GNU APL to the OpenBSD operating system, and I kindly ask
you to consider the possibility of merging the following changes to the
source tree, in order to enable a better support for the OS. As you can
see, only few lines are needed.
Also, I recollected some info about the steps needed to configure
the environment (fonts, keyboard), not necessarily addressed
http://sbudella.altervista.org/blog/20170821-apl-openbsd.html
--- configure.orig Fri Mar 17 16:03:06 2017
+++ configure Mon Jul 17 17:11:15 2017
@@ -21413,7 +21413,7 @@ echo
#
echo "configure: creating $srcdir/src//buildtag.hh"
rm -f $srcdir/src/buildtag.hh
-cd $srcdir/src ; source ./buildtag ; cd ..
+cd $srcdir/src ; . ./buildtag ; cd ..
# create src/makefile.h
#
--- src/Common.cc.orig Fri Mar 17 15:46:53 2017
+++ src/Common.cc Mon Jul 17 16:37:56 2017
@@ -81,6 +81,11 @@ void
init_1(const char * argv0, bool log_startup)
{
rlimit rl;
+
+#ifndef RLIMIT_AS
+# define RLIMIT_AS RLIMIT_DATA
+#endif
+
getrlimit(RLIMIT_AS, &rl);
total_memory = rl.rlim_cur;
--
Giuseppe Cocomazzi
My self is steam
http://sbudella.altervista.org

--
Giuseppe Cocomazzi
My self is steam.

http://sbudella.altervista.org

Elias Mårtenson

2017-08-29 00:33:11 UTC

Permalink

Perhaps it's time for a new release? Or should it be delayed until the
rational number support is stable enough to be default?

Hi JÃŒrgen,
thanks for your reply.
Ported software on OpenBSD is submitted for inclusion in the so-called
"port tree", basically a set of custom Makefiles by means of which
ports can be automatically downloaded, built, packaged and installed
with a single "make" command. The port tree is part of the operating
system, and importing rolling releases from SVN is not an option.
Therefore, the official releases on the GNU mirrors are perfectly fine
for the goal. Furthermore, I feel more comfortable in submitting
stable and mature releases, as another goal of the OS is stability,
security and cleanliness.
As I am also the maintainer of the port/package, I will update the
port's Makefile every time a major release is announced.
As for the link to my blog/notebook, I have been actively maintaining
my homepage for 8 years, my hosting service is quite stable and I have
intention to keep the page away from oblivion. I think then it is
reasonably safe to refer to it.
Thank you very much.
On Mon, Aug 28, 2017 at 3:09 PM, Juergen Sauermann

Post by Juergen Sauermann
Hi Giuseppe,
thanks for submitting the patches. I have included them into SVN 1001.
The first patch is now in Makefile.am as opposed to configure. That

suggests

Post by Juergen Sauermann
that you
are using an older version of the GNU APL sources. Maybe the one from the
GNU APL
home page at gnu.org or a gnu mirror. The "official" GNU APL releases

happen

Post by Juergen Sauermann
quite
rarely (like every one or two years) and therefore they quickly become
outdated. If you
are porting GNU APL then it is better to check out the latest version

from

Post by Juergen Sauermann
SVN.
Regarding your web link below, I wonder how persistent it is? If the

link is

Post by Juergen Sauermann
supposed to
last for a longer period, then we could point to it from out community

web

Post by Juergen Sauermann
page
http://www.gnu.org/software/apl/Community.html and/or mention it in our
README-6-porting
file.
Best Regards,
/// JÃŒrgen Sauermann
Hi list,
I have ported GNU APL to the OpenBSD operating system, and I kindly ask
you to consider the possibility of merging the following changes to the
source tree, in order to enable a better support for the OS. As you can
see, only few lines are needed.
Also, I recollected some info about the steps needed to configure
the environment (fonts, keyboard), not necessarily addressed
http://sbudella.altervista.org/blog/20170821-apl-openbsd.html
--- configure.orig Fri Mar 17 16:03:06 2017
+++ configure Mon Jul 17 17:11:15 2017
@@ -21413,7 +21413,7 @@ echo
#
echo "configure: creating $srcdir/src//buildtag.hh"
rm -f $srcdir/src/buildtag.hh
-cd $srcdir/src ; source ./buildtag ; cd ..
+cd $srcdir/src ; . ./buildtag ; cd ..
# create src/makefile.h
#
--- src/Common.cc.orig Fri Mar 17 15:46:53 2017
+++ src/Common.cc Mon Jul 17 16:37:56 2017
@@ -81,6 +81,11 @@ void
init_1(const char * argv0, bool log_startup)
{
rlimit rl;
+
+#ifndef RLIMIT_AS
+# define RLIMIT_AS RLIMIT_DATA
+#endif
+
getrlimit(RLIMIT_AS, &rl);
total_memory = rl.rlim_cur;
--
Giuseppe Cocomazzi
My self is steam
http://sbudella.altervista.org

--
Giuseppe Cocomazzi
My self is steam.
http://sbudella.altervista.org

Juergen Sauermann

2017-08-29 17:30:56 UTC

Permalink

<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, 
 
the rational numbers are still quite new, so I would like to wait
a little longer before 
making a new release. 
 
Rational numbers cannot become the default because some
computations with them 
take considerably more time than their floating point counterparts
- mainly due to GCD 
normalization. 
 
Giuseppe, I have added a link to your blog on our APL community
page. 
 
/// Jürgen 
 
 
<div class="moz-cite-prefix">On 08/29/2017 02:33 AM, Elias Mårtenson
wrote: 
</div>
<blockquote
cite="mid:CADtN0WJr+LE3-KaKDR04qLq+8uMiCVr7Kg_n+***@mail.gmail.com"
type="cite">
<div dir="auto">Perhaps it's time for a new release? Or should it
be delayed until the rational number support is stable enough to
be default? </div>
<div class="gmail_extra"> 
<div class="gmail_quote">On 29 Aug 2017 02:22, "Giuseppe
Cocomazzi" <<a moz-do-not-send="true"
href="mailto:***@gmail.com">***@gmail.com</a>>
wrote: 
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Jürgen, 
thanks for your reply. 
Ported software on OpenBSD is submitted for inclusion in the
so-called 
"port tree", basically a set of custom Makefiles by means of
which 
ports can be automatically downloaded, built, packaged and
installed 
with a single "make" command. The port tree is part of the
operating 
system, and importing rolling releases from SVN is not an
option. 
Therefore, the official releases on the GNU mirrors are
perfectly fine 
for the goal. Furthermore, I feel more comfortable in
submitting 
stable and mature releases, as another goal of the OS is
stability, 
security and cleanliness. 
 
As I am also the maintainer of the port/package, I will
update the 
port's Makefile every time a major release is announced. 
 
As for the link to my blog/notebook, I have been actively
maintaining 
my homepage for 8 years, my hosting service is quite stable
and I have 
intention to keep the page away from oblivion. I think then
it is 
reasonably safe to refer to it. 
 
Thank you very much. 
 
 
</blockquote>
</div>
</div>
</blockquote>
 
</body>
</html>

e***@gmx.com

2017-08-29 18:34:20 UTC

Permalink

apl on openbsd openbsd on rpi
nice to see openbsd shaking off the cobwebs

On Tue, 29 Aug 2017 19:30:56 +0200

Hi,
the rational numbers are still quite new, so I would like to wait a little longer before
making a new release.
Rational numbers cannot become the default because some computations with them
take considerably more time than their floating point counterparts - mainly due to GCD
normalization.
Giuseppe, I have added a link to your blog on our APL community page.
/// Jürgen
Perhaps it's time for a new release? Or should it be delayed until the rational number support is stable enough to be default?
Hi Jürgen,
thanks for your reply.
Ported software on OpenBSD is submitted for inclusion in the so-called
"port tree", basically a set of custom Makefiles by means of which
ports can be automatically downloaded, built, packaged and installed
with a single "make" command. The port tree is part of the operating
system, and importing rolling releases from SVN is not an option.
Therefore, the official releases on the GNU mirrors are perfectly fine
for the goal. Furthermore, I feel more comfortable in submitting
stable and mature releases, as another goal of the OS is stability,
security and cleanliness.
As I am also the maintainer of the port/package, I will update the
port's Makefile every time a major release is announced.
As for the link to my blog/notebook, I have been actively maintaining
my homepage for 8 years, my hosting service is quite stable and I have
intention to keep the page away from oblivion. I think then it is
reasonably safe to refer to it.
Thank you very much.