Re: [Oorexx-devel] Fwd: Failing build on FreeBSD12

[Jason Martin]

Same goes on OpenBSD.

Patching required in multiple places.



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] Fwd: Failing build on FreeBSD12

[P.O. Jonsson]

Dear all,

I have been trying to install ooRexx on FreeBSD 12. I have found the necessary 
tools (with the exception of PkgConfig) and the installation is as basic as I 
can get it.

I can only see one error in the CMake list  CMAKE_INSTALL_PREFIX is /usr 
(should be /usr/bin i think?) but the building stop early in the make step.

I have included my manual steps and the execution, what am I doing wrong? Did 
anyone build on FreeBSD before?

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se



> Anfang der weitergeleiteten Nachricht:
> 
> Von: FreeBSD Linux 
> Betreff: Failing build on FreeBSD12
> Datum: 20. März 2020 um 23:19:08 MEZ
> An: oor...@jonases.se
> 
> cd ~/workspace/oorexx-freebsd-build/oorexxSVN
> svn update
> cd ~/workspace/oorexx-freebsd-build/oorexxbuild
> cmake -G "Unix Makefiles" ../oorexxSVN
> make clean
> make
> make install
> cpack  ./
> 
> 
> $ bash buildooRexx.sh
> Updating '.':
> At revision 12002.
> -- CMake version is 3.15.5
> -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
> -- The C compiler identification is Clang 8.0.1
> -- The CXX compiler identification is Clang 8.0.1
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Building for a 64-bit architecture
> -- OOREXX_SHEBANG_PROGRAM: "/usr/bin/env rexx" (default)
> -- Found Subversion: /usr/local/bin/svn (found version "1.13.0")
> -- SVN Revision Number is 12002
> -- CMAKE_INSTALL_PREFIX is /usr
> -- INSTALL_LIB_DIR is /usr/lib
> -- Looking for ctype.h
> -- Looking for ctype.h - found
> -- Looking for float.h
> -- Looking for float.h - found
> -- Looking for limits.h
> -- Looking for limits.h - found
> -- Looking for locale.h
> -- Looking for locale.h - found
> -- Looking for malloc.h
> -- Looking for malloc.h - not found
> -- Looking for memory.h
> -- Looking for memory.h - found
> -- Looking for memset
> -- Looking for memset - found
> -- Looking for nsleep
> -- Looking for nsleep - not found
> -- Looking for setlocale
> -- Looking for setlocale - found
> -- Looking for signal.h
> -- Looking for signal.h - found
> -- Looking for stdarg.h
> -- Looking for stdarg.h - found
> -- Looking for stddef.h
> -- Looking for stddef.h - found
> -- Looking for stdio.h
> -- Looking for stdio.h - found
> -- Looking for stdlib.h
> -- Looking for stdlib.h - found
> -- Looking for string.h
> -- Looking for string.h - found
> -- Looking for time.h
> -- Looking for time.h - found
> -- Looking for vprintf
> -- Looking for vprintf - found
> -- Looking for fcntl.h
> -- Looking for fcntl.h - found
> -- Looking for nanosleep
> -- Looking for nanosleep - found
> -- Looking for inttypes.h
> -- Looking for inttypes.h - found
> -- Looking for stdint.h
> -- Looking for stdint.h - found
> -- Looking for attr/xattr.h
> -- Looking for attr/xattr.h - not found
> -- Looking for catopen
> -- Looking for catopen - found
> -- Looking for dlfcn.h
> -- Looking for dlfcn.h - found
> -- Looking for features.h
> -- Looking for features.h - not found
> -- Looking for filehdr.h
> -- Looking for filehdr.h - not found
> -- Looking for fstat
> -- Looking for fstat - found
> -- Looking for gcvt
> -- Looking for gcvt - not found
> -- Looking for geteuid
> -- Looking for geteuid - found
> -- Looking for getpgrp
> -- Looking for getpgrp - found
> -- Looking for getpwuid
> -- Looking for getpwuid - found
> -- Looking for gettimeofday
> -- Looking for gettimeofday - found
> -- Looking for IDtouser
> -- Looking for IDtouser - not found
> -- Looking for mesg.h
> -- Looking for mesg.h - not found
> -- Looking for netinet/in.h
> -- Looking for netinet/in.h - found
> -- Looking for nl_types.h
> -- Looking for nl_types.h - found
> -- Looking for pthread.h
> -- Looking for pthread.h - found
> -- Looking for pthread_mutexattr_settype
> -- Looking for pthread_mutexattr_settype - found
> -- Looking for pthread_mutex_timedlock
> -- Looking for pthread_mutex_timedlock - found
> -- Performing Test HAVE_PTHREAD_MUTEX_ERRORCHECK
> -- Performing Test HAVE_PTHREAD_MUTEX_ERRORCHECK - Success
> -- Performing Test HAVE_PTHREAD_MUTEX_RECURSIVE
> -- Performing Test HAVE_PTHREAD_MUTEX_RECURSIVE - Success
> -- Performing Test HAVE_DLADDR
> -- Performing Test HAVE_DLADDR - Success
> -- Looking for _PC_CASE_SENSITIVE
> -- Looking for _PC_CASE_SENSITIVE - not found
> -- Looking for FNM_CASEFOLD
> -- Looking for FNM_CASEFOLD - found
> -- Looking for KDMKTONE
> -- Looking for KDMKTONE - not found
> -- Looking for _NSGetExecutablePath
> -- Looking for _NSGetExecutablePath - not found
> -- Looking for getexecname
> -- 

Re: [Oorexx-devel] Documentation: using less bold font for some elements ?

[Gil Barmwater]

Hi Rony,

I finally have had an opportunity to look into this issue. I downloaded 
your version of rexxpg and opened it next to the one that comes with the 
ooRexx build which is "pre-split" so it has none of the changes that you 
have made. One thing I noticed was that you have added tags "inside" the 
examples which I had not seen before. My understanding of the 
 tag was that it was supposed to show code examples or 
snippets "as-is" with the possible exception of syntax highlighting, a 
separate issue. Now, as you have demonstrated, you CAN "tag" parts of a 
 or  section but I don't see the benefit of doing 
so. Similarly, tagging words in the section titles causes the TOC (which 
is automatically generated) to display them accordingly. So, if it were 
me doing the work, I would only use the tags in the paragraphs where 
they draw the distinction between the prose and the "names" of important 
things. Again, just my opinion. Our documents have always only used the 
three types of typographic conventions described in the the Preface of 
each book. Deviating from that "standard" needs a whole lot more 
discussion and consideration IMHO.


Gil

On 3/20/2020 9:15 AM, Rony G. Flatscher wrote:

On 19.03.2020 14:31, Gil Barmwater wrote:

Having spent some time looking at the documentation while developing the system 
to build the
books, I found that we actually have a set of conventions on how things are 
displayed. This is
part of every document, under the title "Typographic Conventions", right near 
the beginning of the
book. So this proposal seems rather extreme to me as it could have a major 
impact on all our
documents. Just my opinion.


Gil, of course there is no intention to have any negative impact on the 
documentation!

The current boldness is quite strong and looking at the rexxpg book (also in 
the TOC!) the bolded,
monotype text stands out prominently. Hence wondering whether removing the 
boldness (but leaving it)
to semi-bold would be possible at all. And if it was possible it still needs to 
be assessed whether
it negatively impacts the overall look-and feel of the books.

---rony




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


--
Gil Barmwater



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Documentation: using less bold font for some elements ?

[Rony G. Flatscher]

On 20.03.2020 14:23, René Jansen wrote:
> just want to correct one terminology issue: a monotype font is a font from a 
> specific foundry, a monospaced (or non-proportional) font is what you mean.

Ah, yes, thank you René, also: 
.

---rony

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Documentation: using less bold font for some elements ?

[René Jansen]

just want to correct one terminology issue: a monotype font is a font from a 
specific foundry, a monospaced (or non-proportional) font is what you mean.

> On 20 Mar 2020, at 14:15, Rony G. Flatscher  wrote:
> 
> On 19.03.2020 14:31, Gil Barmwater wrote:
>> 
>> Having spent some time looking at the documentation while developing the 
>> system to build the
>> books, I found that we actually have a set of conventions on how things are 
>> displayed. This is
>> part of every document, under the title "Typographic Conventions", right 
>> near the beginning of the
>> book. So this proposal seems rather extreme to me as it could have a major 
>> impact on all our
>> documents. Just my opinion.
>> 
> Gil, of course there is no intention to have any negative impact on the 
> documentation!
> 
> The current boldness is quite strong and looking at the rexxpg book (also in 
> the TOC!) the bolded,
> monotype text stands out prominently. Hence wondering whether removing the 
> boldness (but leaving it)
> to semi-bold would be possible at all. And if it was possible it still needs 
> to be assessed whether
> it negatively impacts the overall look-and feel of the books.
> 
> ---rony
> 
> 
> 
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Ad semcls.cls in rexxref (Re: Samples take 3

[Rony G. Flatscher]

On 20.03.2020 14:14, Rick McGuire wrote:
>
> On Fri, Mar 20, 2020 at 9:13 AM Rony G. Flatscher  > wrote:
>
> On 19.03.2020 12:21, Rick McGuire wrote:
> > the sem.cls example is not intended to show how to use semaphores, but 
> rather an example for how
> > to use guard. I think the example needs to be kept, but have no 
> objections to including a
> link to
> > the new classes.
>
> Thanks, have added the links locally.
>
> One more question (cannot find the thread): shall I remove the 
> documentation for EventSemaphore's
> and MutexSemaphore's close method?
>
> Not until they have been removed from the code and the tests.

Thanks, committed the rexxref documentation change.

Temporarily the resulting rexxref.pdf can be viewed from
, 
cf. the end of chpater
"12.4.4.1. Semaphores".

---rony

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Documentation: using less bold font for some elements ?

[Rony G. Flatscher]

On 19.03.2020 14:31, Gil Barmwater wrote:
>
> Having spent some time looking at the documentation while developing the 
> system to build the
> books, I found that we actually have a set of conventions on how things are 
> displayed. This is
> part of every document, under the title "Typographic Conventions", right near 
> the beginning of the
> book. So this proposal seems rather extreme to me as it could have a major 
> impact on all our
> documents. Just my opinion.
>
Gil, of course there is no intention to have any negative impact on the 
documentation!

The current boldness is quite strong and looking at the rexxpg book (also in 
the TOC!) the bolded,
monotype text stands out prominently. Hence wondering whether removing the 
boldness (but leaving it)
to semi-bold would be possible at all. And if it was possible it still needs to 
be assessed whether
it negatively impacts the overall look-and feel of the books.

---rony




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Ad semcls.cls in rexxref (Re: Samples take 3

[Rick McGuire]

On Fri, Mar 20, 2020 at 9:13 AM Rony G. Flatscher 
wrote:

> On 19.03.2020 12:21, Rick McGuire wrote:
> > the sem.cls example is not intended to show how to use semaphores, but
> rather an example for how
> > to use guard. I think the example needs to be kept, but have no
> objections to including a link to
> > the new classes.
>
> Thanks, have added the links locally.
>
> One more question (cannot find the thread): shall I remove the
> documentation for EventSemaphore's
> and MutexSemaphore's close method?
>
> Not until they have been removed from the code and the tests.


> ---rony
>
>
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Ad semcls.cls in rexxref (Re: Samples take 3

[Rony G. Flatscher]

On 19.03.2020 12:21, Rick McGuire wrote:
> the sem.cls example is not intended to show how to use semaphores, but rather 
> an example for how
> to use guard. I think the example needs to be kept, but have no objections to 
> including a link to
> the new classes.

Thanks, have added the links locally.

One more question (cannot find the thread): shall I remove the documentation 
for EventSemaphore's
and MutexSemaphore's close method?

---rony




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Samples, take 1, changes to the readme in /samples

[Rony G. Flatscher]

n 19.03.2020 11:47, P.O. Jonsson wrote:
> I have provided the patch and will wait with the next step until that is in 
> the system.

applied your patch with r12001, thank you!

---rony



___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel