Dear Rony, I followed this „Howto“ Publican can run in Dockers as well I tried some time ago but ran into similar problems. The ooRexx documents to build from are for version 3 of Publican, I guess there is some adaptation needed. I summarized the exchange at the time, I have attached it. I did not try Pandoc. |
[osboxes@localhost oorexx]$ rm -r publish/oorexx
[osboxes@localhost oorexx]$ publican build --formats xml --langs en-US --publish
Setting up en-US
Processing file tmp/en-US/xml_tmp/CPLv1.0.xml ->
tmp/en-US/xml/CPLv1.0.xml
Processing file tmp/en-US/xml_tmp/Conventions.xml ->
tmp/en-US/xml/Conventions.xml
Processing file tmp/en-US/xml_tmp/Legal_Notice.xml ->
tmp/en-US/xml/Legal_Notice.xml
Processing file tmp/en-US/xml_tmp/Notices.xml ->
tmp/en-US/xml/Notices.xml
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Processing file tmp/en-US/xml_tmp/diagrams.xml ->
tmp/en-US/xml/diagrams.xml
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Processing file tmp/en-US/xml_tmp/help.xml -> tmp/en-US/xml/help.xml
Beginning work on en-US
Starting xml
Finished xml
[osboxes@localhost oorexx]$ publican build --formats pdf --langs en-US --publish
Setting up en-US
Processing file tmp/en-US/xml_tmp/CPLv1.0.xml ->
tmp/en-US/xml/CPLv1.0.xml
Processing file tmp/en-US/xml_tmp/Conventions.xml ->
tmp/en-US/xml/Conventions.xml
Processing file tmp/en-US/xml_tmp/Legal_Notice.xml ->
tmp/en-US/xml/Legal_Notice.xml
Processing file tmp/en-US/xml_tmp/Notices.xml ->
tmp/en-US/xml/Notices.xml
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Processing file tmp/en-US/xml_tmp/diagrams.xml ->
tmp/en-US/xml/diagrams.xml
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Use of uninitialized value in concatenation (.) or string at
/usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 739, <FH> line 12.
Processing file tmp/en-US/xml_tmp/help.xml -> tmp/en-US/xml/help.xml
Beginning work on en-US
Starting pdf
Can't call method "param" on an undefined value at
/usr/share/perl5/vendor_perl/Publican/Builder/DocBook.pm line 528, <FH> line 12.
[osboxes@localhost oorexx]$
Documentation-0.1-testbook-en-US.pdf
Description: Adobe PDF document
Complete Thread for Publican on ooRexx site
results of 319
Flat | Threaded
<< < 1 2 3 4 5 .. 13 > >> (Page 3 of 13)
Re: [Oorexx-devel] Building the docs
From: René Jansen <rvjansen@xs...> - 2018-12-25 17:55:44
Attachments: Message as HTML
Hi Erich,
Iâd like to build the docs on the build server also. Do you still have that
email somewhere in which you explained to me what you did?
René.
On 25 Dec 2018, at 13:51, Erich Steinböck <erich.steinboeck@...> wrote:
>> OK, snag #1) fedorahosted.org has gone away
> Well, as far as I understand this is where the Publican git was hosted. That
> could mean, Publican is dead.
>
>> Do you still have the installer file? Perhaps we should add that to the
>> buildutils directory on sourceforge.
> Yes, I still have it.
> I've packed it together with a bunch of my publican-related stuff into a ZIP
> and uploaded to
> https://sourceforge.net/projects/oorexx/files/windows-build-tools/PublicanWindows.zip
> (I just now see that there's also a oorexx-buildutils/ folder .. I haven't
> yet checked if we are keeping redundant files)
>
> The ZIP contains the Publican-Installer-3.0.exe and various helper scripts
> that I wrote
> e. g. a filter to get rid of thousands of fop warnings during build, or a fop
> front-end script, which runs fop-preprocess to remove unwanted whitespace.
> The PublicanBuildHere script will run a build with above mentioned extensions
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Building the docs
From: Erich Steinböck <erich.steinboeck@gm...> - 2018-12-25 17:51:32
Attachments: Message as HTML
>
> OK, snag #1) fedorahosted.org has gone away
>
Well, as far as I understand this is where the Publican git was hosted.
That could mean, Publican is dead.
Do you still have the installer file? Perhaps we should add that to the
> buildutils directory on sourceforge.
Yes, I still have it.
I've packed it together with a bunch of my publican-related stuff into a
ZIP and uploaded to
https://sourceforge.net/projects/oorexx/files/windows-build-tools/PublicanWindows.zip
(I just now see that there's also a oorexx-buildutils/ folder .. I haven't
yet checked if we are keeping redundant files)
The ZIP contains the Publican-Installer-3.0.exe and various helper scripts
that I wrote
e. g. a filter to get rid of thousands of fop warnings during build, or a
fop front-end script, which runs fop-preprocess to remove unwanted
whitespace.
The PublicanBuildHere script will run a build with above mentioned
extensions
[Oorexx-devel] Problem to load oosqlite.dll in Rexx Version 5.0.0 r11639
From: H?kan Erixon <hakan.hex.erixon@ou...> - 2018-12-25 17:10:16
Attachments: Message as HTML
Problem to load oosqlite.dll in Rexx Version 5.0.0 r11639
Works to load oosqlite.dll with Rexx Version 5.0.0 r11580
I believe it has something to do with how the loading mechanism have changed,
but as a non C programmer I have no clue, what changes has to be done in the
oosqlite src regarding rexx extension library loading.
Hopefully someone with knowledge can have a look.
57 *-* ::attribute null get class external "LIBRARY oosqlite
oosql_getNull_atr_cls"
47 *-* ::requires 'ooSQLite.cls'
4 *-* call sqlA.rex dbname
Error 90 running C:\Program Files\ooRexx\ooSQLite.cls line 57: External name
not found.
Error 90.998: Unable to find external method "OOSQLRESET_RTN".
Re: [Oorexx-devel] Building the docs
From: Rick McGuire <object.rexx@gm...> - 2018-12-25 16:56:10
Attachments: Message as HTML
I thought I'd give the ubuntu build a try. I was able to build and install
the brand successfully. Attempting to build the docs got the the phase
"Starting pdf" and it has been sitting there for a long time. I don't know
it it is hung, or just taking a really long time. This is using the latest
publican and wkhtmltopdf. Since you are using FOP on windows, I wonder if
it might be better to delete wkhtmltopdf and allow it to use FOP instead.
Rick
On Tue, Dec 25, 2018 at 11:39 AM Rick McGuire <object.rexx@...> wrote:
> OK, snag #1) fedorahosted.org has gone away and I haven't been able to
> find another source for publican 3.0. Do you still have the installer file?
> Perhaps we should add that to the buildutils directory on sourceforge.
>
> Rick
>
> On Tue, Dec 25, 2018 at 10:18 AM Erich Steinböck <
> erich.steinboeck@...> wrote:
>
>> I'm building on Windows only, using an ancient, unsupported version of
>> publican plus fop for Windows
>> I changed some settings, like single-page formatting and added a crude
>> manual cleaning-step which removes a lot of annoying whitespace around
>> examples. Windows was (and still seems) the only way to get a decent PDF.
>> PDFs built on Ubuntu had several major issues (reported at
>> https://www.redhat.com/archives/publican-list/2016-August/msg00004.html)
>> which I didn't understand well enough to be able to fix.
>> Also the build would take some ten times longer than on Windows and I'm
>> doing all the editing on Windows, so a build capability on Windows is
>> really a must for me.
>>
>> My old installation notes for publican on Windows are here, but I'm not
>> sure how complete these are
>>
>> ~~~
>> Install Publican
>> https://fedorahosted.org/releases/p/u/publican/
>> Tars and SRPMs: https://fedorahosted.org/releases/p/u/publican/
>> Publican-Installer-3.0.exe
>>
>> Install FOP
>> https://xmlgraphics.apache.org/fop/download.html
>> http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop
>>
>> http://mirror.cc.columbia.edu/pub/software/apache/xmlgraphics/fop/binaries/fop-1.1-bin.zip
>>
>> add "version: 5.0" to docs/trunk/rexxref/publican.cfg
>> either
>> add Publican path to PATH: set path="\Program Files
>> (x86)\Publican;"%PATH%, or
>> use "\Program Files (x86)\Publican;publican.exe" instead of "publican"
>> either
>> add FOP path to PATH: set path=\FOP\fop-1.1;%PATH%, or
>> create a BAT file (within your PATH) that redirects
>> publican build --formats=pdf --langs=en-US --common_content=".."
>> ~~~
>>
>> On Tue, Dec 25, 2018 at 3:38 PM Rick McGuire <object.rexx@...>
>> wrote:
>>
>>> I'll give it a go...how are you building the docs now if not this way?
>>>
>>> Rick
>>>
>>> On Tue, Dec 25, 2018 at 9:30 AM Erich Steinböck <
>>> erich.steinboeck@...> wrote:
>>>
>>>> I tried this some two or three years ago, and it was a miserable
>>>> experience.
>>>> I've attached below my notes from back then.
>>>>
>>>> If you want to give it a try, please note down each step as accurately
>>>> as possible. If we get somewhere, I'll add the steps required to our Wiki.
>>>>
>>>> I tried getting help for a few things by posting to the publican-list
>>>> publican-list@...
>>>>
>>>> The publican-list archives are to be found at
>>>> https://www.redhat.com/archives/publican-list/
>>>>
>>>> ~~~
>>>> sudo apt install publican
>>>> # this will install fop, but fop is deprecated by publican, it wants
>>>> wkhtmltopdf
>>>> # installing wkhtmltopdf doesn't seem to work, as publican requires a
>>>> 'patched' version
>>>> # see
>>>> https://www.redhat.com/archives/publican-list/2014-April/msg00003.html
>>>>
>>>> # in case we've already tried to install wkhtmltopdf:
>>>> #
>>>> http://stackoverflow.com/questions/18758589/wkhtmltopdf-installation-error-on-ubuntu
>>>> sudo apt-get remove --purge wkhtmltopdf
>>>>
>>>> # now let's install 'patched' wkhtmltopdf:
>>>> sudo apt-get install openssl build-essential xorg libssl-dev
>>>> # http://wkhtmltopdf.org/downloads.html
>>>> wget
>>>> http://download.gna.org/wkhtmltopdf/0.12/0.12.3/wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
>>>> tar xf wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
>>>> cd wkhtmltox/bin
>>>> sudo chown root:root wkhtmltopdf
>>>> sudo cp wkhtmltopdf /usr/local/bin/wkhtmltopdf
>>>> wkhtmltopdf --version # wkhtmltopdf 0.12.3 (with patched qt)
>>>>
>>>> # to avoid "failed loading image" errors and unexplained "wkhtmltopdf
>>>> died" errors
>>>> #
>>>> https://www.redhat.com/archives/publican-list/2013-August/msg00005.html
>>>> ulimit -n 8192
>>>> ~~~
>>>>
>>>>
>>>>
>>>> On Tue, Dec 25, 2018 at 1:28 PM Rick McGuire <object.rexx@...>
>>>> wrote:
>>>>
>>>>> I have a working Ubuntu 18.10 now running in VirtualBox. It would be
>>>>> nice to be able to build the docs on VM as well. Is there a guide for what
>>>>> needs to be installed for this?
>>>>>
>>>>> Rick
>>>>> _______________________________________________
>>>>> Oorexx-devel mailing list
>>>>> Oorexx-devel@...
>>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>>>
>>>> _______________________________________________
>>>> Oorexx-devel mailing list
>>>> Oorexx-devel@...
>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>>
>>> _______________________________________________
>>> Oorexx-devel mailing list
>>> Oorexx-devel@...
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>
Re: [Oorexx-devel] Building the docs
From: Rick McGuire <object.rexx@gm...> - 2018-12-25 16:39:51
Attachments: Message as HTML
OK, snag #1) fedorahosted.org has gone away and I haven't been able to find
another source for publican 3.0. Do you still have the installer file?
Perhaps we should add that to the buildutils directory on sourceforge.
Rick
On Tue, Dec 25, 2018 at 10:18 AM Erich Steinböck <erich.steinboeck@...>
wrote:
> I'm building on Windows only, using an ancient, unsupported version of
> publican plus fop for Windows
> I changed some settings, like single-page formatting and added a crude
> manual cleaning-step which removes a lot of annoying whitespace around
> examples. Windows was (and still seems) the only way to get a decent PDF.
> PDFs built on Ubuntu had several major issues (reported at
> https://www.redhat.com/archives/publican-list/2016-August/msg00004.html)
> which I didn't understand well enough to be able to fix.
> Also the build would take some ten times longer than on Windows and I'm
> doing all the editing on Windows, so a build capability on Windows is
> really a must for me.
>
> My old installation notes for publican on Windows are here, but I'm not
> sure how complete these are
>
> ~~~
> Install Publican
> https://fedorahosted.org/releases/p/u/publican/
> Tars and SRPMs: https://fedorahosted.org/releases/p/u/publican/
> Publican-Installer-3.0.exe
>
> Install FOP
> https://xmlgraphics.apache.org/fop/download.html
> http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop
>
> http://mirror.cc.columbia.edu/pub/software/apache/xmlgraphics/fop/binaries/fop-1.1-bin.zip
>
> add "version: 5.0" to docs/trunk/rexxref/publican.cfg
> either
> add Publican path to PATH: set path="\Program Files
> (x86)\Publican;"%PATH%, or
> use "\Program Files (x86)\Publican;publican.exe" instead of "publican"
> either
> add FOP path to PATH: set path=\FOP\fop-1.1;%PATH%, or
> create a BAT file (within your PATH) that redirects
> publican build --formats=pdf --langs=en-US --common_content=".."
> ~~~
>
> On Tue, Dec 25, 2018 at 3:38 PM Rick McGuire <object.rexx@...>
> wrote:
>
>> I'll give it a go...how are you building the docs now if not this way?
>>
>> Rick
>>
>> On Tue, Dec 25, 2018 at 9:30 AM Erich Steinböck <
>> erich.steinboeck@...> wrote:
>>
>>> I tried this some two or three years ago, and it was a miserable
>>> experience.
>>> I've attached below my notes from back then.
>>>
>>> If you want to give it a try, please note down each step as accurately
>>> as possible. If we get somewhere, I'll add the steps required to our Wiki.
>>>
>>> I tried getting help for a few things by posting to the publican-list
>>> publican-list@...
>>>
>>> The publican-list archives are to be found at
>>> https://www.redhat.com/archives/publican-list/
>>>
>>> ~~~
>>> sudo apt install publican
>>> # this will install fop, but fop is deprecated by publican, it wants
>>> wkhtmltopdf
>>> # installing wkhtmltopdf doesn't seem to work, as publican requires a
>>> 'patched' version
>>> # see
>>> https://www.redhat.com/archives/publican-list/2014-April/msg00003.html
>>>
>>> # in case we've already tried to install wkhtmltopdf:
>>> #
>>> http://stackoverflow.com/questions/18758589/wkhtmltopdf-installation-error-on-ubuntu
>>> sudo apt-get remove --purge wkhtmltopdf
>>>
>>> # now let's install 'patched' wkhtmltopdf:
>>> sudo apt-get install openssl build-essential xorg libssl-dev
>>> # http://wkhtmltopdf.org/downloads.html
>>> wget
>>> http://download.gna.org/wkhtmltopdf/0.12/0.12.3/wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
>>> tar xf wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
>>> cd wkhtmltox/bin
>>> sudo chown root:root wkhtmltopdf
>>> sudo cp wkhtmltopdf /usr/local/bin/wkhtmltopdf
>>> wkhtmltopdf --version # wkhtmltopdf 0.12.3 (with patched qt)
>>>
>>> # to avoid "failed loading image" errors and unexplained "wkhtmltopdf
>>> died" errors
>>> #
>>> https://www.redhat.com/archives/publican-list/2013-August/msg00005.html
>>> ulimit -n 8192
>>> ~~~
>>>
>>>
>>>
>>> On Tue, Dec 25, 2018 at 1:28 PM Rick McGuire <object.rexx@...>
>>> wrote:
>>>
>>>> I have a working Ubuntu 18.10 now running in VirtualBox. It would be
>>>> nice to be able to build the docs on VM as well. Is there a guide for what
>>>> needs to be installed for this?
>>>>
>>>> Rick
>>>> _______________________________________________
>>>> Oorexx-devel mailing list
>>>> Oorexx-devel@...
>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>>
>>> _______________________________________________
>>> Oorexx-devel mailing list
>>> Oorexx-devel@...
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
Re: [Oorexx-devel] Building the docs
From: Gil Barmwater <gbarmwater@al...> - 2018-12-25 16:20:58
Attachments: Message as HTML
I, too, was under the impression that the docs were built on *ix, not
Windows! Once we have a tested "recipe" for doing it, I'll attempt to
get it working on my system as well. That way, when I find typos, etc.,
I can edit/build and supply a "tested" patch that a committer can
confidently apply.
Gil B.
On 12/25/2018 10:39 AM, Rick McGuire wrote:
> I didn't realize you were doing this on Windows...I'd actually prefer
> that. Years ago David stated Windows would not be possible, so I
> didn't realize that had changed. I'll give that a shot.
>
> I ran into an immediate road block with your ubuntu instructions. The
> patched version doesn't appear available any more. I just finished
> installing the latest wkhtmltopdf, but haven't had a chance to see if
> it works or not. I think I'll focus on the Windows build first, since
> if I do any editting, it will be on Windows also.
>
> Rick
>
> On Tue, Dec 25, 2018 at 10:18 AM Erich Steinböck
> <erich.steinboeck@... <mailto:erich.steinboeck@...>> wrote:
>
> I'm building on Windows only, using an ancient, unsupported
> version of publican plus fop for Windows
> I changed some settings, like single-page formatting and added a
> crude manual cleaning-step which removes a lot of annoying
> whitespace around examples. Windows was (and still seems) the
> only way to get a decent PDF.
> PDFs built on Ubuntu had several major issues (reported at
> https://www.redhat.com/archives/publican-list/2016-August/msg00004.html)
> which I didn't understand well enough to be able to fix.
> Also the build would take some ten times longer than on Windows
> and I'm doing all the editing on Windows, so a build capability on
> Windows is really a must for me.
>
> My old installation notes for publican on Windows are here, but
> I'm not sure how complete these are
>
> ~~~
> Install Publican
> https://fedorahosted.org/releases/p/u/publican/
> Tars and SRPMs: https://fedorahosted.org/releases/p/u/publican/
> Publican-Installer-3.0.exe
>
> Install FOP
> https://xmlgraphics.apache.org/fop/download.html
> http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop
>
> http://mirror.cc.columbia.edu/pub/software/apache/xmlgraphics/fop/binaries/fop-1.1-bin.zip
>
> add "version: 5.0" to docs/trunk/rexxref/publican.cfg
> either
> add Publican path to PATH: set path="\Program Files
> (x86)\Publican;"%PATH%, or
> use "\Program Files (x86)\Publican;publican.exe" instead of
> "publican"
> either
> add FOP path to PATH: set path=\FOP\fop-1.1;%PATH%, or
> create a BAT file (within your PATH) that redirects
> publican build --formats=pdf --langs=en-US --common_content=".."
> ~~~
>
> On Tue, Dec 25, 2018 at 3:38 PM Rick McGuire
> <object.rexx@... <mailto:object.rexx@...>> wrote:
>
> I'll give it a go...how are you building the docs now if not
> this way?
>
> Rick
>
> On Tue, Dec 25, 2018 at 9:30 AM Erich Steinböck
> <erich.steinboeck@...
> <mailto:erich.steinboeck@...>> wrote:
>
> I tried this some two or three years ago, and it was a
> miserable experience.
> I've attached below my notes from back then.
>
> If you want to give it a try, please note down each step
> as accurately as possible. If we get somewhere, I'll add
> the steps required to our Wiki.
>
> I tried getting help for a few things by posting to the
> publican-list
> publican-list@... <mailto:publican-list@...>
>
> The publican-list archives are to be found at
> https://www.redhat.com/archives/publican-list/
>
> ~~~
> sudo apt install publican
> # this will install fop, but fop is deprecated by
> publican, it wants wkhtmltopdf
> # installing wkhtmltopdf doesn't seem to work, as publican
> requires a 'patched' version
> # see
>
> https://www.redhat.com/archives/publican-list/2014-April/msg00003.html
>
> # in case we've already tried to install wkhtmltopdf:
> #
>
> http://stackoverflow.com/questions/18758589/wkhtmltopdf-installation-error-on-ubuntu
> sudo apt-get remove --purge wkhtmltopdf
>
> # now let's install 'patched' wkhtmltopdf:
> sudo apt-get install openssl build-essential xorg libssl-dev
> # http://wkhtmltopdf.org/downloads.html
> wget
>
> http://download.gna.org/wkhtmltopdf/0.12/0.12.3/wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
> tar xf wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
> cd wkhtmltox/bin
> sudo chown root:root wkhtmltopdf
> sudo cp wkhtmltopdf /usr/local/bin/wkhtmltopdf
> wkhtmltopdf --version # wkhtmltopdf 0.12.3 (with patched qt)
>
> # to avoid "failed loading image" errors and unexplained
> "wkhtmltopdf died" errors
> #
>
> https://www.redhat.com/archives/publican-list/2013-August/msg00005.html
> ulimit -n 8192
> ~~~
>
>
>
> On Tue, Dec 25, 2018 at 1:28 PM Rick McGuire
> <object.rexx@... <mailto:object.rexx@...>> wrote:
>
> I have a working Ubuntu 18.10 now running in
> VirtualBox. It would be nice to be able to build the
> docs on VM as well. Is there a guide for what needs to
> be installed for this?
>
> Rick
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> <mailto:Oorexx-devel@...>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> <mailto:Oorexx-devel@...>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> <mailto:Oorexx-devel@...>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> <mailto:Oorexx-devel@...>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
Re: [Oorexx-devel] Building the docs
From: Rick McGuire <object.rexx@gm...> - 2018-12-25 15:39:23
Attachments: Message as HTML
I didn't realize you were doing this on Windows...I'd actually prefer that.
Years ago David stated Windows would not be possible, so I didn't realize
that had changed. I'll give that a shot.
I ran into an immediate road block with your ubuntu instructions. The
patched version doesn't appear available any more. I just finished
installing the latest wkhtmltopdf, but haven't had a chance to see if it
works or not. I think I'll focus on the Windows build first, since if I do
any editting, it will be on Windows also.
Rick
On Tue, Dec 25, 2018 at 10:18 AM Erich Steinböck <erich.steinboeck@...>
wrote:
> I'm building on Windows only, using an ancient, unsupported version of
> publican plus fop for Windows
> I changed some settings, like single-page formatting and added a crude
> manual cleaning-step which removes a lot of annoying whitespace around
> examples. Windows was (and still seems) the only way to get a decent PDF.
> PDFs built on Ubuntu had several major issues (reported at
> https://www.redhat.com/archives/publican-list/2016-August/msg00004.html)
> which I didn't understand well enough to be able to fix.
> Also the build would take some ten times longer than on Windows and I'm
> doing all the editing on Windows, so a build capability on Windows is
> really a must for me.
>
> My old installation notes for publican on Windows are here, but I'm not
> sure how complete these are
>
> ~~~
> Install Publican
> https://fedorahosted.org/releases/p/u/publican/
> Tars and SRPMs: https://fedorahosted.org/releases/p/u/publican/
> Publican-Installer-3.0.exe
>
> Install FOP
> https://xmlgraphics.apache.org/fop/download.html
> http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop
>
> http://mirror.cc.columbia.edu/pub/software/apache/xmlgraphics/fop/binaries/fop-1.1-bin.zip
>
> add "version: 5.0" to docs/trunk/rexxref/publican.cfg
> either
> add Publican path to PATH: set path="\Program Files
> (x86)\Publican;"%PATH%, or
> use "\Program Files (x86)\Publican;publican.exe" instead of "publican"
> either
> add FOP path to PATH: set path=\FOP\fop-1.1;%PATH%, or
> create a BAT file (within your PATH) that redirects
> publican build --formats=pdf --langs=en-US --common_content=".."
> ~~~
>
> On Tue, Dec 25, 2018 at 3:38 PM Rick McGuire <object.rexx@...>
> wrote:
>
>> I'll give it a go...how are you building the docs now if not this way?
>>
>> Rick
>>
>> On Tue, Dec 25, 2018 at 9:30 AM Erich Steinböck <
>> erich.steinboeck@...> wrote:
>>
>>> I tried this some two or three years ago, and it was a miserable
>>> experience.
>>> I've attached below my notes from back then.
>>>
>>> If you want to give it a try, please note down each step as accurately
>>> as possible. If we get somewhere, I'll add the steps required to our Wiki.
>>>
>>> I tried getting help for a few things by posting to the publican-list
>>> publican-list@...
>>>
>>> The publican-list archives are to be found at
>>> https://www.redhat.com/archives/publican-list/
>>>
>>> ~~~
>>> sudo apt install publican
>>> # this will install fop, but fop is deprecated by publican, it wants
>>> wkhtmltopdf
>>> # installing wkhtmltopdf doesn't seem to work, as publican requires a
>>> 'patched' version
>>> # see
>>> https://www.redhat.com/archives/publican-list/2014-April/msg00003.html
>>>
>>> # in case we've already tried to install wkhtmltopdf:
>>> #
>>> http://stackoverflow.com/questions/18758589/wkhtmltopdf-installation-error-on-ubuntu
>>> sudo apt-get remove --purge wkhtmltopdf
>>>
>>> # now let's install 'patched' wkhtmltopdf:
>>> sudo apt-get install openssl build-essential xorg libssl-dev
>>> # http://wkhtmltopdf.org/downloads.html
>>> wget
>>> http://download.gna.org/wkhtmltopdf/0.12/0.12.3/wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
>>> tar xf wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
>>> cd wkhtmltox/bin
>>> sudo chown root:root wkhtmltopdf
>>> sudo cp wkhtmltopdf /usr/local/bin/wkhtmltopdf
>>> wkhtmltopdf --version # wkhtmltopdf 0.12.3 (with patched qt)
>>>
>>> # to avoid "failed loading image" errors and unexplained "wkhtmltopdf
>>> died" errors
>>> #
>>> https://www.redhat.com/archives/publican-list/2013-August/msg00005.html
>>> ulimit -n 8192
>>> ~~~
>>>
>>>
>>>
>>> On Tue, Dec 25, 2018 at 1:28 PM Rick McGuire <object.rexx@...>
>>> wrote:
>>>
>>>> I have a working Ubuntu 18.10 now running in VirtualBox. It would be
>>>> nice to be able to build the docs on VM as well. Is there a guide for what
>>>> needs to be installed for this?
>>>>
>>>> Rick
>>>> _______________________________________________
>>>> Oorexx-devel mailing list
>>>> Oorexx-devel@...
>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>>
>>> _______________________________________________
>>> Oorexx-devel mailing list
>>> Oorexx-devel@...
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
Re: [Oorexx-devel] Building the docs
From: Erich Steinböck <erich.steinboeck@gm...> - 2018-12-25 15:17:34
Attachments: Message as HTML
I'm building on Windows only, using an ancient, unsupported version of
publican plus fop for Windows
I changed some settings, like single-page formatting and added a crude
manual cleaning-step which removes a lot of annoying whitespace around
examples. Windows was (and still seems) the only way to get a decent PDF.
PDFs built on Ubuntu had several major issues (reported at
https://www.redhat.com/archives/publican-list/2016-August/msg00004.html)
which I didn't understand well enough to be able to fix.
Also the build would take some ten times longer than on Windows and I'm
doing all the editing on Windows, so a build capability on Windows is
really a must for me.
My old installation notes for publican on Windows are here, but I'm not
sure how complete these are
~~~
Install Publican
https://fedorahosted.org/releases/p/u/publican/
Tars and SRPMs: https://fedorahosted.org/releases/p/u/publican/
Publican-Installer-3.0.exe
Install FOP
https://xmlgraphics.apache.org/fop/download.html
http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop
http://mirror.cc.columbia.edu/pub/software/apache/xmlgraphics/fop/binaries/fop-1.1-bin.zip
add "version: 5.0" to docs/trunk/rexxref/publican.cfg
either
add Publican path to PATH: set path="\Program Files
(x86)\Publican;"%PATH%, or
use "\Program Files (x86)\Publican;publican.exe" instead of "publican"
either
add FOP path to PATH: set path=\FOP\fop-1.1;%PATH%, or
create a BAT file (within your PATH) that redirects
publican build --formats=pdf --langs=en-US --common_content=".."
~~~
On Tue, Dec 25, 2018 at 3:38 PM Rick McGuire <object.rexx@...> wrote:
> I'll give it a go...how are you building the docs now if not this way?
>
> Rick
>
> On Tue, Dec 25, 2018 at 9:30 AM Erich Steinböck <
> erich.steinboeck@...> wrote:
>
>> I tried this some two or three years ago, and it was a miserable
>> experience.
>> I've attached below my notes from back then.
>>
>> If you want to give it a try, please note down each step as accurately as
>> possible. If we get somewhere, I'll add the steps required to our Wiki.
>>
>> I tried getting help for a few things by posting to the publican-list
>> publican-list@...
>>
>> The publican-list archives are to be found at
>> https://www.redhat.com/archives/publican-list/
>>
>> ~~~
>> sudo apt install publican
>> # this will install fop, but fop is deprecated by publican, it wants
>> wkhtmltopdf
>> # installing wkhtmltopdf doesn't seem to work, as publican requires a
>> 'patched' version
>> # see
>> https://www.redhat.com/archives/publican-list/2014-April/msg00003.html
>>
>> # in case we've already tried to install wkhtmltopdf:
>> #
>> http://stackoverflow.com/questions/18758589/wkhtmltopdf-installation-error-on-ubuntu
>> sudo apt-get remove --purge wkhtmltopdf
>>
>> # now let's install 'patched' wkhtmltopdf:
>> sudo apt-get install openssl build-essential xorg libssl-dev
>> # http://wkhtmltopdf.org/downloads.html
>> wget
>> http://download.gna.org/wkhtmltopdf/0.12/0.12.3/wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
>> tar xf wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
>> cd wkhtmltox/bin
>> sudo chown root:root wkhtmltopdf
>> sudo cp wkhtmltopdf /usr/local/bin/wkhtmltopdf
>> wkhtmltopdf --version # wkhtmltopdf 0.12.3 (with patched qt)
>>
>> # to avoid "failed loading image" errors and unexplained "wkhtmltopdf
>> died" errors
>> # https://www.redhat.com/archives/publican-list/2013-August/msg00005.html
>> ulimit -n 8192
>> ~~~
>>
>>
>>
>> On Tue, Dec 25, 2018 at 1:28 PM Rick McGuire <object.rexx@...>
>> wrote:
>>
>>> I have a working Ubuntu 18.10 now running in VirtualBox. It would be
>>> nice to be able to build the docs on VM as well. Is there a guide for what
>>> needs to be installed for this?
>>>
>>> Rick
>>> _______________________________________________
>>> Oorexx-devel mailing list
>>> Oorexx-devel@...
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
Re: [Oorexx-devel] Building the docs
From: Rick McGuire <object.rexx@gm...> - 2018-12-25 14:37:49
Attachments: Message as HTML
I'll give it a go...how are you building the docs now if not this way?
Rick
On Tue, Dec 25, 2018 at 9:30 AM Erich Steinböck <erich.steinboeck@...>
wrote:
> I tried this some two or three years ago, and it was a miserable
> experience.
> I've attached below my notes from back then.
>
> If you want to give it a try, please note down each step as accurately as
> possible. If we get somewhere, I'll add the steps required to our Wiki.
>
> I tried getting help for a few things by posting to the publican-list
> publican-list@...
>
> The publican-list archives are to be found at
> https://www.redhat.com/archives/publican-list/
>
> ~~~
> sudo apt install publican
> # this will install fop, but fop is deprecated by publican, it wants
> wkhtmltopdf
> # installing wkhtmltopdf doesn't seem to work, as publican requires a
> 'patched' version
> # see
> https://www.redhat.com/archives/publican-list/2014-April/msg00003.html
>
> # in case we've already tried to install wkhtmltopdf:
> #
> http://stackoverflow.com/questions/18758589/wkhtmltopdf-installation-error-on-ubuntu
> sudo apt-get remove --purge wkhtmltopdf
>
> # now let's install 'patched' wkhtmltopdf:
> sudo apt-get install openssl build-essential xorg libssl-dev
> # http://wkhtmltopdf.org/downloads.html
> wget
> http://download.gna.org/wkhtmltopdf/0.12/0.12.3/wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
> tar xf wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
> cd wkhtmltox/bin
> sudo chown root:root wkhtmltopdf
> sudo cp wkhtmltopdf /usr/local/bin/wkhtmltopdf
> wkhtmltopdf --version # wkhtmltopdf 0.12.3 (with patched qt)
>
> # to avoid "failed loading image" errors and unexplained "wkhtmltopdf
> died" errors
> # https://www.redhat.com/archives/publican-list/2013-August/msg00005.html
> ulimit -n 8192
> ~~~
>
>
>
> On Tue, Dec 25, 2018 at 1:28 PM Rick McGuire <object.rexx@...>
> wrote:
>
>> I have a working Ubuntu 18.10 now running in VirtualBox. It would be nice
>> to be able to build the docs on VM as well. Is there a guide for what needs
>> to be installed for this?
>>
>> Rick
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
Re: [Oorexx-devel] Building the docs
From: Erich Steinböck <erich.steinboeck@gm...> - 2018-12-25 14:30:14
Attachments: Message as HTML
I tried this some two or three years ago, and it was a miserable experience.
I've attached below my notes from back then.
If you want to give it a try, please note down each step as accurately as
possible. If we get somewhere, I'll add the steps required to our Wiki.
I tried getting help for a few things by posting to the publican-list
publican-list@...
The publican-list archives are to be found at
https://www.redhat.com/archives/publican-list/
~~~
sudo apt install publican
# this will install fop, but fop is deprecated by publican, it wants
wkhtmltopdf
# installing wkhtmltopdf doesn't seem to work, as publican requires a
'patched' version
# see https://www.redhat.com/archives/publican-list/2014-April/msg00003.html
# in case we've already tried to install wkhtmltopdf:
#
http://stackoverflow.com/questions/18758589/wkhtmltopdf-installation-error-on-ubuntu
sudo apt-get remove --purge wkhtmltopdf
# now let's install 'patched' wkhtmltopdf:
sudo apt-get install openssl build-essential xorg libssl-dev
# http://wkhtmltopdf.org/downloads.html
wget
http://download.gna.org/wkhtmltopdf/0.12/0.12.3/wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
tar xf wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
cd wkhtmltox/bin
sudo chown root:root wkhtmltopdf
sudo cp wkhtmltopdf /usr/local/bin/wkhtmltopdf
wkhtmltopdf --version # wkhtmltopdf 0.12.3 (with patched qt)
# to avoid "failed loading image" errors and unexplained "wkhtmltopdf died"
errors
# https://www.redhat.com/archives/publican-list/2013-August/msg00005.html
ulimit -n 8192
~~~
On Tue, Dec 25, 2018 at 1:28 PM Rick McGuire <object.rexx@...> wrote:
> I have a working Ubuntu 18.10 now running in VirtualBox. It would be nice
> to be able to build the docs on VM as well. Is there a guide for what needs
> to be installed for this?
>
> Rick
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
[Oorexx-devel] Building the docs
From: Rick McGuire <object.rexx@gm...> - 2018-12-25 12:28:21
Attachments: Message as HTML
I have a working Ubuntu 18.10 now running in VirtualBox. It would be nice
to be able to build the docs on VM as well. Is there a guide for what needs
to be installed for this?
Rick
Re: [Oorexx-devel] Time for the *ix users to pitch in.
From: P.O. Jonsson <oorexx@jo...> - 2018-12-25 12:19:32
Attachments: Message as HTML
This is what is a bit weird: I deleted the old ooRexx installation (from /opt
or /uer/local) on the 4th of december, at 22:00 sometime (I checked the garbage
bin), hence there was no ooRexx installation available on the user âpoâ on
that machine at the 8.12. entering ârexxâ on the command line give
âcommand not found"
I have deleted both files, If they resurface I will let you know.
Von meinen Macbook gesendet
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oorexx@...
> Am 25.12.2018 um 12:35 schrieb Rick McGuire <object.rexx@...>:
>
> You probably ran ooRexx back on December 8th, which is when they were
> created. You can delete them, but the files will get recreated the next time
> you run ooRexx.
>
> Rick
>
> On Tue, Dec 25, 2018 at 6:25 AM P.O. Jonsson <oorexx@... <mailto:oorexx@...>>
> wrote:
> I have no recollection of having made a build on that userID for quite some
> time, hence the question,, it is Erich that uses the âJenkinsâ account on
> the same machine to make the automated builds, hence the question.
>
> Here are the further details of these files
>
> -rw-rw-rw- 1 po staff 0 Dec 8 16:19 .ooRexx-5.0.0-64.lock
> srwxrwxrwx 1 po staff 0 Dec 8 16:19 .ooRexx-5.0.0-64.service
>
> I assume I can safely delete them?
>
> Von meinen Macbook gesendet
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oorexx@... <mailto:oorexx@...>
>
>
>
>> Am 25.12.2018 um 11:42 schrieb Rick McGuire <object.rexx@...
>> <mailto:object.rexx@...>>:
>>
>> If the build was running under your userid, that file got created when rxapi
>> was launched during the build process. That's the file that is used to
>> ensure that only one copy of rxapi runs per user.
>>
>> Rick
>>
>> On Tue, Dec 25, 2018 at 5:09 AM P.O. Jonsson <oorexx@...
>> <mailto:oorexx@...>> wrote:
>> Dear Erich,
>>
>> I was going into my user account on the Mac Mini Jenkins slave today and
>> noticed a hidden file ".ooRexx-5.0.0-64.lockâ in my home directory
>> (Users/po) Is this something that is coming out of the Jenkins build? How
>> can the lock file be in my account? I have no ooRexx installation in that
>> account and the machine wide installation has been removed. some time ago.
>>
>> Can you please explain the latest development with the locking and how it is
>> intended to work? No criticism, just trying to understand.
>>
>> Von meinen Macbook gesendet
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oorexx@... <mailto:oorexx@...>
>>
>>> Am 25.12.2018 um 00:39 schrieb Erich Steinböck <erich.steinboeck@...
>>> <mailto:erich.steinboeck@...>>:
>>>
>>> With a few typos fixed, this seems to work as expected, also in the
>>> discussed sudo scenario.
>>>
>>> also includes the login name in the file names
>>> getuid() returns the id, not the name, so I had changed the %s to %d in the
>>> snprintf's
>>> I assume getting the name will require getpwuid() - if we want the name
>>> instead
>>>
>>> If no XDG_RUNTIME_DIR is set, this will be something like:
>>> ls -lda /tmp/.ooR*
>>> -rw-rw-rw- 1 jenkins jenkins 0 Dec 24 23:19
>>> /tmp/.ooRexx-5.0.0-64-1002.lock
>>> srwxrwxrwx 1 jenkins jenkins 0 Dec 24 23:49
>>> /tmp/.ooRexx-5.0.0-64-1002.service
>>> -rw-rw-rw- 1 www-data www-data 0 Dec 24 23:52 /tmp/.ooRexx-5.0.0-64-33.lock
>>> srwxrwxrwx 1 www-data www-data 0 Dec 24 23:49
>>> /tmp/.ooRexx-5.0.0-64-33.service
>>> I'm a bit concerned about the file permissions global RW bits, but to my
>>> surprise rm nevertheless refuses to remove both the lock and the service
>>> "file" (rm: cannot remove '/tmp/.ooRexx-5.0.0-64-1002.lock': Operation not
>>> permitted .. I don't understand why)
>>>
>>> There is one situation that will make rxapi fail to start: if a malicious
>>> user creates a simple file with the same name as the lock/service file of a
>>> user. It might still be a good idea to check whether rxapi can create
>>> those files (XDG or /tmp) and if not, somehow (but how?) give an error
>>> indication "cannot create path/.ooRexx...service"
>>>
>>> On Mon, Dec 24, 2018 at 2:19 PM Rick McGuire <object.rexx@...
>>> <mailto:object.rexx@...>> wrote:
>>> Ok, from what Bob Martin posted, it sounds like the www-data login does not
>>> have XDG variables set and also does not have write access to the home
>>> directory. As others have said, using the home directory is probably a bad
>>> idea because it could be network-mounted and using it would lock out users
>>> on other machines. Here is a totally uncompiled and untested patch that
>>> uses either the XDG_RUNTIME_DIR or /tmp for creating the files and also
>>> includes the login name in the file names.
>>>
>>> Rick
>>> <www-data-b.patch>_______________________________________________
>>> Oorexx-devel mailing list
>>> Oorexx-devel@... <mailto:Oorexx-devel@...>
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>;
>>
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@... <mailto:Oorexx-devel@...>
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>;
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@... <mailto:Oorexx-devel@...>
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>;
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@... <mailto:Oorexx-devel@...>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>;
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Time for the *ix users to pitch in.
From: Rick McGuire <object.rexx@gm...> - 2018-12-25 11:35:56
Attachments: Message as HTML
You probably ran ooRexx back on December 8th, which is when they were
created. You can delete them, but the files will get recreated the next
time you run ooRexx.
Rick
On Tue, Dec 25, 2018 at 6:25 AM P.O. Jonsson <oorexx@...> wrote:
> I have no recollection of having made a build on that userID for quite
> some time, hence the question,, it is Erich that uses the âJenkinsâ
> account
> on the same machine to make the automated builds, hence the question.
>
> Here are the further details of these files
>
> -rw-rw-rw- 1 po staff 0 Dec 8 16:19 .ooRexx-5.0.0-64.lock
> srwxrwxrwx 1 po staff 0 Dec 8 16:19 .ooRexx-5.0.0-64.service
>
> I assume I can safely delete them?
>
> Von meinen Macbook gesendet
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oorexx@...
>
>
>
> Am 25.12.2018 um 11:42 schrieb Rick McGuire <object.rexx@...>:
>
> If the build was running under your userid, that file got created when
> rxapi was launched during the build process. That's the file that is used
> to ensure that only one copy of rxapi runs per user.
>
> Rick
>
> On Tue, Dec 25, 2018 at 5:09 AM P.O. Jonsson <oorexx@...> wrote:
>
>> Dear Erich,
>>
>> I was going into my user account on the Mac Mini Jenkins slave today and
>> noticed a hidden file "*.ooRexx-5.0.0-64.lock*â in my home directory
>> (Users/po) Is this something that is coming out of the Jenkins build? How
>> can the lock file be in my account? I have no ooRexx installation in that
>> account and the machine wide installation has been removed. some time ago.
>>
>> Can you please explain the latest development with the locking and how it
>> is intended to work? No criticism, just trying to understand.
>>
>> Von meinen Macbook gesendet
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oorexx@...
>>
>>
>> Am 25.12.2018 um 00:39 schrieb Erich Steinböck <
>> erich.steinboeck@...>:
>>
>> With a few typos fixed, this seems to work as expected, also in the
>> discussed sudo scenario.
>>
>> also includes the login name in the file names
>>>
>> getuid() returns the id, not the name, so I had changed the %s to %d in
>> the snprintf's
>> I assume getting the name will require getpwuid() - if we want the name
>> instead
>>
>> If no XDG_RUNTIME_DIR is set, this will be something like:
>> ls -lda /tmp/.ooR*
>> -rw-rw-rw- 1 jenkins jenkins 0 Dec 24 23:19
>> /tmp/.ooRexx-5.0.0-64-1002.lock
>> srwxrwxrwx 1 jenkins jenkins 0 Dec 24 23:49
>> /tmp/.ooRexx-5.0.0-64-1002.service
>> -rw-rw-rw- 1 www-data www-data 0 Dec 24 23:52
>> /tmp/.ooRexx-5.0.0-64-33.lock
>> srwxrwxrwx 1 www-data www-data 0 Dec 24 23:49
>> /tmp/.ooRexx-5.0.0-64-33.service
>> I'm a bit concerned about the file permissions global RW bits, but to my
>> surprise rm nevertheless refuses to remove both the lock and the service
>> "file" (rm: cannot remove '/tmp/.ooRexx-5.0.0-64-1002.lock': Operation not
>> permitted .. I don't understand why)
>>
>> There is one situation that will make rxapi fail to start: if a malicious
>> user creates a simple file with the same name as the lock/service file of a
>> user. It might still be a good idea to check whether rxapi can create
>> those files (XDG or /tmp) and if not, somehow (but how?) give an error
>> indication "cannot create path/.ooRexx...service"
>>
>> On Mon, Dec 24, 2018 at 2:19 PM Rick McGuire <object.rexx@...>
>> wrote:
>>
>>> Ok, from what Bob Martin posted, it sounds like the www-data login does
>>> not have XDG variables set and also does not have write access to the home
>>> directory. As others have said, using the home directory is probably a bad
>>> idea because it could be network-mounted and using it would lock out users
>>> on other machines. Here is a totally uncompiled and untested patch that
>>> uses either the XDG_RUNTIME_DIR or /tmp for creating the files and also
>>> includes the login name in the file names.
>>>
>>> Rick
>>>
>> <www-data-b.patch>_______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
Re: [Oorexx-devel] Time for the *ix users to pitch in.
From: P.O. Jonsson <oorexx@jo...> - 2018-12-25 11:24:39
Attachments: Message as HTML
I have no recollection of having made a build on that userID for quite some
time, hence the question,, it is Erich that uses the âJenkinsâ account on
the same machine to make the automated builds, hence the question.
Here are the further details of these files
-rw-rw-rw- 1 po staff 0 Dec 8 16:19 .ooRexx-5.0.0-64.lock
srwxrwxrwx 1 po staff 0 Dec 8 16:19 .ooRexx-5.0.0-64.service
I assume I can safely delete them?
Von meinen Macbook gesendet
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oorexx@...
> Am 25.12.2018 um 11:42 schrieb Rick McGuire <object.rexx@...>:
>
> If the build was running under your userid, that file got created when rxapi
> was launched during the build process. That's the file that is used to ensure
> that only one copy of rxapi runs per user.
>
> Rick
>
> On Tue, Dec 25, 2018 at 5:09 AM P.O. Jonsson <oorexx@... <mailto:oorexx@...>>
> wrote:
> Dear Erich,
>
> I was going into my user account on the Mac Mini Jenkins slave today and
> noticed a hidden file ".ooRexx-5.0.0-64.lockâ in my home directory
> (Users/po) Is this something that is coming out of the Jenkins build? How can
> the lock file be in my account? I have no ooRexx installation in that account
> and the machine wide installation has been removed. some time ago.
>
> Can you please explain the latest development with the locking and how it is
> intended to work? No criticism, just trying to understand.
>
> Von meinen Macbook gesendet
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oorexx@... <mailto:oorexx@...>
>
>> Am 25.12.2018 um 00:39 schrieb Erich Steinböck <erich.steinboeck@...
>> <mailto:erich.steinboeck@...>>:
>>
>> With a few typos fixed, this seems to work as expected, also in the
>> discussed sudo scenario.
>>
>> also includes the login name in the file names
>> getuid() returns the id, not the name, so I had changed the %s to %d in the
>> snprintf's
>> I assume getting the name will require getpwuid() - if we want the name
>> instead
>>
>> If no XDG_RUNTIME_DIR is set, this will be something like:
>> ls -lda /tmp/.ooR*
>> -rw-rw-rw- 1 jenkins jenkins 0 Dec 24 23:19 /tmp/.ooRexx-5.0.0-64-1002.lock
>> srwxrwxrwx 1 jenkins jenkins 0 Dec 24 23:49
>> /tmp/.ooRexx-5.0.0-64-1002.service
>> -rw-rw-rw- 1 www-data www-data 0 Dec 24 23:52 /tmp/.ooRexx-5.0.0-64-33.lock
>> srwxrwxrwx 1 www-data www-data 0 Dec 24 23:49
>> /tmp/.ooRexx-5.0.0-64-33.service
>> I'm a bit concerned about the file permissions global RW bits, but to my
>> surprise rm nevertheless refuses to remove both the lock and the service
>> "file" (rm: cannot remove '/tmp/.ooRexx-5.0.0-64-1002.lock': Operation not
>> permitted .. I don't understand why)
>>
>> There is one situation that will make rxapi fail to start: if a malicious
>> user creates a simple file with the same name as the lock/service file of a
>> user. It might still be a good idea to check whether rxapi can create those
>> files (XDG or /tmp) and if not, somehow (but how?) give an error indication
>> "cannot create path/.ooRexx...service"
>>
>> On Mon, Dec 24, 2018 at 2:19 PM Rick McGuire <object.rexx@...
>> <mailto:object.rexx@...>> wrote:
>> Ok, from what Bob Martin posted, it sounds like the www-data login does not
>> have XDG variables set and also does not have write access to the home
>> directory. As others have said, using the home directory is probably a bad
>> idea because it could be network-mounted and using it would lock out users
>> on other machines. Here is a totally uncompiled and untested patch that uses
>> either the XDG_RUNTIME_DIR or /tmp for creating the files and also includes
>> the login name in the file names.
>>
>> Rick
>> <www-data-b.patch>_______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@... <mailto:Oorexx-devel@...>
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>;
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@... <mailto:Oorexx-devel@...>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>;
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Time for the *ix users to pitch in.
From: Rick McGuire <object.rexx@gm...> - 2018-12-25 10:42:44
Attachments: Message as HTML
If the build was running under your userid, that file got created when
rxapi was launched during the build process. That's the file that is used
to ensure that only one copy of rxapi runs per user.
Rick
On Tue, Dec 25, 2018 at 5:09 AM P.O. Jonsson <oorexx@...> wrote:
> Dear Erich,
>
> I was going into my user account on the Mac Mini Jenkins slave today and
> noticed a hidden file "*.ooRexx-5.0.0-64.lock*â in my home directory
> (Users/po) Is this something that is coming out of the Jenkins build? How
> can the lock file be in my account? I have no ooRexx installation in that
> account and the machine wide installation has been removed. some time ago.
>
> Can you please explain the latest development with the locking and how it
> is intended to work? No criticism, just trying to understand.
>
> Von meinen Macbook gesendet
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oorexx@...
>
>
> Am 25.12.2018 um 00:39 schrieb Erich Steinböck <erich.steinboeck@...
> >:
>
> With a few typos fixed, this seems to work as expected, also in the
> discussed sudo scenario.
>
> also includes the login name in the file names
>>
> getuid() returns the id, not the name, so I had changed the %s to %d in
> the snprintf's
> I assume getting the name will require getpwuid() - if we want the name
> instead
>
> If no XDG_RUNTIME_DIR is set, this will be something like:
> ls -lda /tmp/.ooR*
> -rw-rw-rw- 1 jenkins jenkins 0 Dec 24 23:19
> /tmp/.ooRexx-5.0.0-64-1002.lock
> srwxrwxrwx 1 jenkins jenkins 0 Dec 24 23:49
> /tmp/.ooRexx-5.0.0-64-1002.service
> -rw-rw-rw- 1 www-data www-data 0 Dec 24 23:52 /tmp/.ooRexx-5.0.0-64-33.lock
> srwxrwxrwx 1 www-data www-data 0 Dec 24 23:49
> /tmp/.ooRexx-5.0.0-64-33.service
> I'm a bit concerned about the file permissions global RW bits, but to my
> surprise rm nevertheless refuses to remove both the lock and the service
> "file" (rm: cannot remove '/tmp/.ooRexx-5.0.0-64-1002.lock': Operation not
> permitted .. I don't understand why)
>
> There is one situation that will make rxapi fail to start: if a malicious
> user creates a simple file with the same name as the lock/service file of a
> user. It might still be a good idea to check whether rxapi can create
> those files (XDG or /tmp) and if not, somehow (but how?) give an error
> indication "cannot create path/.ooRexx...service"
>
> On Mon, Dec 24, 2018 at 2:19 PM Rick McGuire <object.rexx@...>
> wrote:
>
>> Ok, from what Bob Martin posted, it sounds like the www-data login does
>> not have XDG variables set and also does not have write access to the home
>> directory. As others have said, using the home directory is probably a bad
>> idea because it could be network-mounted and using it would lock out users
>> on other machines. Here is a totally uncompiled and untested patch that
>> uses either the XDG_RUNTIME_DIR or /tmp for creating the files and also
>> includes the login name in the file names.
>>
>> Rick
>>
> <www-data-b.patch>_______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
Re: [Oorexx-devel] Time for the *ix users to pitch in.
From: P.O. Jonsson <oorexx@jo...> - 2018-12-25 10:08:23
Attachments: Message as HTML
Dear Erich,
I was going into my user account on the Mac Mini Jenkins slave today and
noticed a hidden file ".ooRexx-5.0.0-64.lockâ in my home directory (Users/po)
Is this something that is coming out of the Jenkins build? How can the lock
file be in my account? I have no ooRexx installation in that account and the
machine wide installation has been removed. some time ago.
Can you please explain the latest development with the locking and how it is
intended to work? No criticism, just trying to understand.
Von meinen Macbook gesendet
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oorexx@...
> Am 25.12.2018 um 00:39 schrieb Erich Steinböck <erich.steinboeck@...>:
>
> With a few typos fixed, this seems to work as expected, also in the discussed
> sudo scenario.
>
> also includes the login name in the file names
> getuid() returns the id, not the name, so I had changed the %s to %d in the
> snprintf's
> I assume getting the name will require getpwuid() - if we want the name
> instead
>
> If no XDG_RUNTIME_DIR is set, this will be something like:
> ls -lda /tmp/.ooR*
> -rw-rw-rw- 1 jenkins jenkins 0 Dec 24 23:19 /tmp/.ooRexx-5.0.0-64-1002.lock
> srwxrwxrwx 1 jenkins jenkins 0 Dec 24 23:49
> /tmp/.ooRexx-5.0.0-64-1002.service
> -rw-rw-rw- 1 www-data www-data 0 Dec 24 23:52 /tmp/.ooRexx-5.0.0-64-33.lock
> srwxrwxrwx 1 www-data www-data 0 Dec 24 23:49 /tmp/.ooRexx-5.0.0-64-33.service
> I'm a bit concerned about the file permissions global RW bits, but to my
> surprise rm nevertheless refuses to remove both the lock and the service
> "file" (rm: cannot remove '/tmp/.ooRexx-5.0.0-64-1002.lock': Operation not
> permitted .. I don't understand why)
>
> There is one situation that will make rxapi fail to start: if a malicious
> user creates a simple file with the same name as the lock/service file of a
> user. It might still be a good idea to check whether rxapi can create those
> files (XDG or /tmp) and if not, somehow (but how?) give an error indication
> "cannot create path/.ooRexx...service"
>
> On Mon, Dec 24, 2018 at 2:19 PM Rick McGuire <object.rexx@...
> <mailto:object.rexx@...>> wrote:
> Ok, from what Bob Martin posted, it sounds like the www-data login does not
> have XDG variables set and also does not have write access to the home
> directory. As others have said, using the home directory is probably a bad
> idea because it could be network-mounted and using it would lock out users on
> other machines. Here is a totally uncompiled and untested patch that uses
> either the XDG_RUNTIME_DIR or /tmp for creating the files and also includes
> the login name in the file names.
>
> Rick
> <www-data-b.patch>_______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Time for the *ix users to pitch in.
From: Rick McGuire <object.rexx@gm...> - 2018-12-25 01:41:58
Attachments: Message as HTML
Using getpwuid() would be better. Based on the code that was there before,
I was assuming getuid() actually returned the username...guess I should
have looked it up first.
Rick
On Mon, Dec 24, 2018 at 6:40 PM Erich Steinböck <erich.steinboeck@...>
wrote:
> With a few typos fixed, this seems to work as expected, also in the
> discussed sudo scenario.
>
> also includes the login name in the file names
>>
> getuid() returns the id, not the name, so I had changed the %s to %d in
> the snprintf's
> I assume getting the name will require getpwuid() - if we want the name
> instead
>
> If no XDG_RUNTIME_DIR is set, this will be something like:
> ls -lda /tmp/.ooR*
> -rw-rw-rw- 1 jenkins jenkins 0 Dec 24 23:19
> /tmp/.ooRexx-5.0.0-64-1002.lock
> srwxrwxrwx 1 jenkins jenkins 0 Dec 24 23:49
> /tmp/.ooRexx-5.0.0-64-1002.service
> -rw-rw-rw- 1 www-data www-data 0 Dec 24 23:52 /tmp/.ooRexx-5.0.0-64-33.lock
> srwxrwxrwx 1 www-data www-data 0 Dec 24 23:49
> /tmp/.ooRexx-5.0.0-64-33.service
> I'm a bit concerned about the file permissions global RW bits, but to my
> surprise rm nevertheless refuses to remove both the lock and the service
> "file" (rm: cannot remove '/tmp/.ooRexx-5.0.0-64-1002.lock': Operation not
> permitted .. I don't understand why)
>
> There is one situation that will make rxapi fail to start: if a malicious
> user creates a simple file with the same name as the lock/service file of a
> user. It might still be a good idea to check whether rxapi can create
> those files (XDG or /tmp) and if not, somehow (but how?) give an error
> indication "cannot create path/.ooRexx...service"
>
> On Mon, Dec 24, 2018 at 2:19 PM Rick McGuire <object.rexx@...>
> wrote:
>
>> Ok, from what Bob Martin posted, it sounds like the www-data login does
>> not have XDG variables set and also does not have write access to the home
>> directory. As others have said, using the home directory is probably a bad
>> idea because it could be network-mounted and using it would lock out users
>> on other machines. Here is a totally uncompiled and untested patch that
>> uses either the XDG_RUNTIME_DIR or /tmp for creating the files and also
>> includes the login name in the file names.
>>
>> Rick
>>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
Re: [Oorexx-devel] Time for the *ix users to pitch in.
From: Erich Steinböck <erich.steinboeck@gm...> - 2018-12-24 23:39:33
Attachments: www-data-b.patch Message as HTML
With a few typos fixed, this seems to work as expected, also in the
discussed sudo scenario.
also includes the login name in the file names
>
getuid() returns the id, not the name, so I had changed the %s to %d in the
snprintf's
I assume getting the name will require getpwuid() - if we want the name
instead
If no XDG_RUNTIME_DIR is set, this will be something like:
ls -lda /tmp/.ooR*
-rw-rw-rw- 1 jenkins jenkins 0 Dec 24 23:19
/tmp/.ooRexx-5.0.0-64-1002.lock
srwxrwxrwx 1 jenkins jenkins 0 Dec 24 23:49
/tmp/.ooRexx-5.0.0-64-1002.service
-rw-rw-rw- 1 www-data www-data 0 Dec 24 23:52 /tmp/.ooRexx-5.0.0-64-33.lock
srwxrwxrwx 1 www-data www-data 0 Dec 24 23:49
/tmp/.ooRexx-5.0.0-64-33.service
I'm a bit concerned about the file permissions global RW bits, but to my
surprise rm nevertheless refuses to remove both the lock and the service
"file" (rm: cannot remove '/tmp/.ooRexx-5.0.0-64-1002.lock': Operation not
permitted .. I don't understand why)
There is one situation that will make rxapi fail to start: if a malicious
user creates a simple file with the same name as the lock/service file of a
user. It might still be a good idea to check whether rxapi can create
those files (XDG or /tmp) and if not, somehow (but how?) give an error
indication "cannot create path/.ooRexx...service"
On Mon, Dec 24, 2018 at 2:19 PM Rick McGuire <object.rexx@...> wrote:
> Ok, from what Bob Martin posted, it sounds like the www-data login does
> not have XDG variables set and also does not have write access to the home
> directory. As others have said, using the home directory is probably a bad
> idea because it could be network-mounted and using it would lock out users
> on other machines. Here is a totally uncompiled and untested patch that
> uses either the XDG_RUNTIME_DIR or /tmp for creating the files and also
> includes the login name in the file names.
>
> Rick
>
Re: [Oorexx-devel] Setting up VirtualBox
From: Enrico Sorichetti <enricosorichetti@ma...> - 2018-12-24 21:00:35
Attachments: Message as HTML
Probably because nobody ever tried
At my first attempt I got som errors for missing DEFINES
I will look into it
E
> On 24 Dec 2018, at 20:49, Gil Barmwater <gbarmwater@...> wrote:
>
> Can someone help me remember why FreeBSD is not an ooRexx-supported
> configuration? Thanks!
>
Re: [Oorexx-devel] Setting up VirtualBox
From: Jack Woehr <jwoehr@ab...> - 2018-12-24 20:18:47
Attachments: Message as HTML
On Mon, Dec 24, 2018 at 12:49 PM Gil Barmwater <gbarmwater@...>
wrote:
> Can someone help me remember why FreeBSD is not an ooRexx-supported
> configuration? Thanks!
>
>
Wasn't it pthreads?
--
Jack Woehr
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
Re: [Oorexx-devel] Setting up VirtualBox
From: Gil Barmwater <gbarmwater@al...> - 2018-12-24 19:49:23
Attachments: Message as HTML
Can someone help me remember why FreeBSD is not an ooRexx-supported
configuration? Thanks!
On 12/24/2018 10:45 AM, Enrico Sorichetti via Oorexx-devel wrote:
>
>> So far, all I've gotten is suggestions for additional stuff to install.
>
> So far you have got suggestion from people with much more experience
> than you on the subject
> Who are trying to make things easier for you
>
> Before suggesting the use of vagrant I wanted to make an experiment
> Starting from scratch
>
> Installed Virtual Box
> Installed Vagrant
> Researched the best FreeBSD image
> Initialised the vagrant configuration
> Downloaded and Installed the local image
>
> Customised the system to my taste
> Bash
> cmake
> Subversion
>
> Cloned the repo
>
> Attempted the build
>
> To see that ooRexx on freeBSD is not supported yet
>
> And
> How long did it take me
> Just 30 minutes
> And 5 minutes to compose the email
>
> So just be a bit more flexible please
>
> E
>
> Seasonâ s greeting to everybody
>
>
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
Re: [Oorexx-devel] Setting up VirtualBox
From: Michael Lueck <mlueck@lu...> - 2018-12-24 16:46:59
Greetings Rick,
Rick McGuire wrote:
> Yep, I'm already regretting this. So far, all I've gotten is suggestions for
> additional stuff to install. I'm already putting this effort on the shelf.
>
>
> VirtualBox PUEL is really nice. Be sure to install the corresponding
> extension pack. That is a separate download at each VirtualBox release.
The VirtualBox extension pack is where the device drivers for the VirtualBox
virtual hardware come from.
If you like putting up with plain VGA, then sure, go ahead and skip installing
the extension pack. (sheesh at getting scared off that easily!)
I guess we live in separate worlds... I cringe at dealing with anything to do
with compilers, and you seem to be in the camp of "if I have to install
anything separate, RUN!!!"
Direct URL I found the Xubuntu ISO's at:
http://cdimage.ubuntu.com/xubuntu/releases/18.04/release/
There are separate files for the 18.04 and 10.04.1 release all in the one
folder.
I am thankful,
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/
Re: [Oorexx-devel] Setting up VirtualBox
From: Rick McGuire <object.rexx@gm...> - 2018-12-24 15:59:08
Attachments: Message as HTML
I have already installed Virtual Box. I am NOT going to play this game of
"just install this one more thing" or "you should have installed X instead
of Y" just so I can do a compile of ooRexx. I grew tired of it years ago,
I'm not going to start it again.
Rick
On Mon, Dec 24, 2018 at 10:41 AM René Jansen <rvjansen@...> wrote:
> With Docker you will not need Virtual Box.
>
> René.
>
> On 24 Dec 2018, at 10:46, Rick McGuire <object.rexx@...> wrote:
>
> Yep, I'm already regretting this. So far, all I've gotten is suggestions
> for additional stuff to install. I'm already putting this effort on the
> shelf.
>
> Rick
>
> On Mon, Dec 24, 2018 at 9:38 AM Michael Lueck <mlueck@...>
> wrote:
>
>> Greetings Rick,
>>
>> Rick McGuire wrote:
>> > I'll probably end up regretting this, but I finally broke down and
>> installed VirtualBox on my new laptop. Any suggestions on which distro I
>> should use for ooRexx development? (duck and run!).
>>
>>
>> 1) LTS release of Ubuntu / Xubuntu. 18.04 is the newest LTS release. I
>> personally prefer the Xfce desktop environment, so Xubuntu to get that. A
>> clean, less complex UI. For example, to get a random
>> wallpaper set on Ubuntu I had to build a XML file. With Xubuntu, just
>> takes a text file with a list of fully pathed graphic files. Xfce is KISS
>> to me... Keep It Super Simple.
>>
>> Oh, and when you download the ISO, grab the base release of the LTS ISO,
>> not the .1, .2 etc... updated. Sometimes Ubuntu slips updated kernels into
>> the higher .x releases for hardware support reasons,
>> which if you build on that then you become dependent on the updated
>> kernel, not the base LTS kernel.
>>
>> One tweak suggestion for Xubuntu... add a second panel at the bottom of
>> the screen, set to autohide, and place the workplace switcher component on
>> that panel. I run with 18 workspaces, aka Object
>> Desktop Virtual Desktops. To add it, right click the top panel, go into
>> panel preferences, and click to add a second panel.
>>
>> 2) Since IBM has snuggled up to RedHat, I suppose give a nod to that. Is
>> Fedoria still a current free RedHat?
>>
>>
>> VirtualBox PUEL is really nice. Be sure to install the corresponding
>> extension pack. That is a separate download at each VirtualBox release.
>>
>> I am thankful,
>>
>> --
>> Michael Lueck
>> Lueck Data Systems
>> http://www.lueckdatasystems.com/
>>
>>
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@...
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
Re: [Oorexx-devel] Setting up VirtualBox
From: Enrico Sorichetti <enricosorichetti@ma...> - 2018-12-24 15:45:39
Attachments: Message as HTML
> So far, all I've gotten is suggestions for additional stuff to install.
So far you have got suggestion from people with much more experience than you
on the subject
Who are trying to make things easier for you
Before suggesting the use of vagrant I wanted to make an experiment
Starting from scratch
Installed Virtual Box
Installed Vagrant
Researched the best FreeBSD image
Initialised the vagrant configuration
Downloaded and Installed the local image
Customised the system to my taste
Bash
cmake
Subversion
Cloned the repo
Attempted the build
To see that ooRexx on freeBSD is not supported yet
And
How long did it take me
Just 30 minutes
And 5 minutes to compose the email
So just be a bit more flexible please
E
Seasonâ s greeting to everybody
Re: [Oorexx-devel] Setting up VirtualBox
From: René Jansen <rvjansen@xs...> - 2018-12-24 15:41:20
Attachments: Message as HTML
With Docker you will not need Virtual Box.
René.
> On 24 Dec 2018, at 10:46, Rick McGuire <object.rexx@...> wrote:
>
> Yep, I'm already regretting this. So far, all I've gotten is suggestions for
> additional stuff to install. I'm already putting this effort on the shelf.
>
> Rick
>
> On Mon, Dec 24, 2018 at 9:38 AM Michael Lueck <mlueck@...
> <mailto:mlueck@...>> wrote:
> Greetings Rick,
>
> Rick McGuire wrote:
> > I'll probably end up regretting this, but I finally broke down and
> > installed VirtualBox on my new laptop. Any suggestions on which distro I
> > should use for ooRexx development? (duck and run!).
>
>
> 1) LTS release of Ubuntu / Xubuntu. 18.04 is the newest LTS release. I
> personally prefer the Xfce desktop environment, so Xubuntu to get that. A
> clean, less complex UI. For example, to get a random
> wallpaper set on Ubuntu I had to build a XML file. With Xubuntu, just takes a
> text file with a list of fully pathed graphic files. Xfce is KISS to me...
> Keep It Super Simple.
>
> Oh, and when you download the ISO, grab the base release of the LTS ISO, not
> the .1, .2 etc... updated. Sometimes Ubuntu slips updated kernels into the
> higher .x releases for hardware support reasons,
> which if you build on that then you become dependent on the updated kernel,
> not the base LTS kernel.
>
> One tweak suggestion for Xubuntu... add a second panel at the bottom of the
> screen, set to autohide, and place the workplace switcher component on that
> panel. I run with 18 workspaces, aka Object
> Desktop Virtual Desktops. To add it, right click the top panel, go into panel
> preferences, and click to add a second panel.
>
> 2) Since IBM has snuggled up to RedHat, I suppose give a nod to that. Is
> Fedoria still a current free RedHat?
>
>
> VirtualBox PUEL is really nice. Be sure to install the corresponding
> extension pack. That is a separate download at each VirtualBox release.
>
> I am thankful,
>
> --
> Michael Lueck
> Lueck Data Systems
> http://www.lueckdatasystems.com/ <http://www.lueckdatasystems.com/>;
>
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@... <mailto:Oorexx-devel@...>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>;
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Showing
results of 319
Flat | Threaded
<< < 1 2 3 4 5 .. 13 > >> (Page 3 of 13)
About
Site Status
@sfnet_ops
Create a Project
Open Source Software
Business Software
Commercial Games
Top Downloaded Projects
Blog
@sourceforge
Resources
Articles
Site Documentation
Support Request
|
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
