Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-07 Thread Michael Lueck

Greetings Team,


Michael Lueck wrote:

On to make install finally... maybe during lunch (shortly).


(uiserver):u40009095:~/build/oorexxbuild/release$ make install
[  3%] Built target class_files
[ 10%] Built target rexxapi
[ 82%] Built target rexx
[ 83%] Built target hostemu
[ 83%] Built target rexx_exe
[ 88%] Built target rxapi
[ 89%] Built target rexxutil
[ 89%] Built target rexximage
[ 90%] Built target rexx_img
[ 91%] Generating rexx.1.gz
[ 91%] Built target rexx_man
[ 91%] Built target rexxc
[ 92%] Generating rexxc.1.gz
[ 92%] Built target rexxc_man
[ 93%] Built target rxmath
[ 93%] Built target rxqueue
[ 93%] Generating rxqueue.1.gz
[ 93%] Built target rxqueue_man
[ 94%] Built target rxregexp
[ 95%] Built target rxsock
[ 95%] Built target rxsubcom
[ 96%] Generating rxsubcom.1.gz
[ 96%] Built target rxsubcom_man
[ 96%] Built target rxunixsys
[ 96%] Built target runRexxProgram
[ 96%] Built target stackOverflow
[ 96%] Built target callrexx1
[ 96%] Built target callrexx2
[ 97%] Built target wpipe1
[ 97%] Built target wpipe2
[ 98%] Built target wpipe3
[ 98%] Built target orxclassic
[ 98%] Built target orxclassic1
[ 99%] Built target orxexits
[ 99%] Built target orxfunction
[100%] Built target orxinvocation
[100%] Built target orxmethod
[100%] Built target rexxinstance
Install the project...
-- Install configuration: "RELEASE"
-- Installing: 
/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so.4
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so.5.0.0" 
to "$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so.4
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rexx
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rexx" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/rexx.img
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rxapi
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rxapi" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rexxc
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rexxc" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rxqueue
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rxqueue" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rxsubcom
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rxsubcom" to 
"$ORIGIN/../lib"
-- Installing: 
/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so.4
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so.4
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so.4
-- Installing: 
/homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so.4
-- Installing: 
/homepages/35/d157794216/htdocs/opt/oorexx/lib/libhostemu.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/libhostemu.so
-- Set runtime 

Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-06 Thread Michael Lueck

Greetings Team,

Rick McGuire wrote:

This change is in now.



Checked out revision 11724.

[100%] Built target rexxinstance


Phew!!!

On to make install finally... maybe during lunch (shortly).

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


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


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-06 Thread Rick McGuire
This change is in now.

Rick

On Tue, Feb 5, 2019 at 5:32 PM Michael Lueck 
wrote:

> Greetings Team,
>
> All right. Please let me know when I can do another svn pull to pick up
> that accommodation.
>
> Meanwhile I have contacted 1&1 support seeking the specified library
> package.
>
> I am thankful,
>
> --
> Michael Lueck
> Lueck Data Systems
> http://www.lueckdatasystems.com/
>
>
> Rick McGuire wrote:
> > Excellent idea.
> >
> > Rick
> >
> > On Tue, Feb 5, 2019 at 5:24 PM Enrico Sorichetti via Oorexx-devel <
> oorexx-devel@lists.sourceforge.net  oorexx-devel@lists.sourceforge.net>> wrote:
> >
> > Why not simply wrap the build of the ncurses stuff with , for example
> >
> > If( HAVE_NCURSES_H )
> >
> > the ncurses stuff
> >
> > endif()
> >
> > So that if the curses-devel gets installed there will be no need to
> revisit the cmakelists.txt
> >
> > E
> >
> >> On 5 Feb 2019, at 23:18, Michael Lueck  > wrote:
> >>
> >>>
> >>> If you really can't install ncurses, you could remove all
> references to curses/ncurses from CMakeLists.txt
> >>> You'd then build an interpreter without orxncurses and ncurses.cls
> >>
>
>
> ___
> 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] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Michael Lueck

Greetings Team,

All right. Please let me know when I can do another svn pull to pick up that 
accommodation.

Meanwhile I have contacted 1&1 support seeking the specified library package.

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


Rick McGuire wrote:

Excellent idea.

Rick

On Tue, Feb 5, 2019 at 5:24 PM Enrico Sorichetti via Oorexx-devel 
mailto:oorexx-devel@lists.sourceforge.net>> wrote:

Why not simply wrap the build of the ncurses stuff with , for example

If( HAVE_NCURSES_H )

the ncurses stuff

endif()

So that if the curses-devel gets installed there will be no need to revisit 
the cmakelists.txt

E


On 5 Feb 2019, at 23:18, Michael Lueck mailto:mlu...@lueckdatasystems.com>> wrote:



If you really can't install ncurses, you could remove all references to 
curses/ncurses from CMakeLists.txt
You'd then build an interpreter without orxncurses and ncurses.cls





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


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Rick McGuire
Excellent idea.

Rick

On Tue, Feb 5, 2019 at 5:24 PM Enrico Sorichetti via Oorexx-devel <
oorexx-devel@lists.sourceforge.net> wrote:

> Why not simply wrap the build of the ncurses stuff with , for example
>
> If( HAVE_NCURSES_H )
>
> the ncurses stuff
>
> endif()
>
> So that if the curses-devel gets installed there will be no need to
> revisit the cmakelists.txt
>
> E
>
> On 5 Feb 2019, at 23:18, Michael Lueck 
> wrote:
>
>
> If you really can't install ncurses, you could remove all references to
> curses/ncurses from CMakeLists.txt
> You'd then build an interpreter without orxncurses and ncurses.cls
>
>
>
> ___
> 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] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Enrico Sorichetti via Oorexx-devel
Why not simply wrap the build of the ncurses stuff with , for example 

If( HAVE_NCURSES_H )

the ncurses stuff

endif()

So that if the curses-devel gets installed there will be no need to revisit the 
cmakelists.txt

E

> On 5 Feb 2019, at 23:18, Michael Lueck  wrote:
> 
>> 
>> If you really can't install ncurses, you could remove all references to 
>> curses/ncurses from CMakeLists.txt
>> You'd then build an interpreter without orxncurses and ncurses.cls
> 

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


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Michael Lueck

Greetings Erich,

Erich Steinböck wrote:
Back to 1&1 to seek them to add ncurses to the box? 


Yes. Normally you'd just sudo apt install libncurses5-dev



Then I will request.



Did you also have to ask your provider to install gcc, cmake, and svn?



No, the rest was already on the server.



If you really can't install ncurses, you could remove all references to 
curses/ncurses from CMakeLists.txt
You'd then build an interpreter without orxncurses and ncurses.cls



Oh, so it is not needed for ooRexx core, only the nucurses extension?



Do you have write access to either $XDG_RUNTIME_DIR or /tmp ?
This is where rxapi stores it's service "file" and it's lock file.


YUCK! Yes user accounts have write access.

I create my own tmp directory within the user account, point webapps there for 
their temp directory.

We should also expose that to CMake (if not already done) so I can specify 
where I would like the tmp files created.

1&1 advises against writing to the common / shared /tmp directory, and for good 
reason!

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


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


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Erich Steinböck
>
> Back to 1&1 to seek them to add ncurses to the box?

Yes. Normally you'd just  sudo apt install libncurses5-dev
Did you also have to ask your provider to install gcc, cmake, and svn?

If you really can't install ncurses, you could remove all references
to curses/ncurses from CMakeLists.txt
You'd then build an interpreter without orxncurses and ncurses.cls

Do you have write access to either $XDG_RUNTIME_DIR or /tmp ?
This is where rxapi stores it's service "file" and it's lock file.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Michael Lueck

Michael Lueck wrote:

Brilliant suggestion! That does work. I am building now. Used CMake suntax:


cmake -DCMAKE_BUILD_TYPE=RELEASE 
-DCMAKE_INSTALL_PREFIX=/homepages/35/d157794216/htdocs/build/oorexxbuild/release/opt/oorexx
 ../../ooRexx-5.0.0/oorexx-code-0



Oops, copy/paste issue with the prefix! Doing so again...

cmake -DCMAKE_BUILD_TYPE=RELEASE 
-DCMAKE_INSTALL_PREFIX=/homepages/35/d157794216/htdocs/opt/oorexx 
../../ooRexx-5.0.0/oorexx-code-0

Looks better. I see now at the end of cmake:


-- Looking for ncurses.h
-- Looking for ncurses.h - not found
-- Configuring done
-- Generating done
-- Build files have been written to: 
/homepages/35/d157794216/htdocs/build/oorexxbuild/release


Back to 1&1 to seek them to add ncurses to the box?

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


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


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Michael Lueck

Greetings Erich,

Erich Steinböck wrote:

Or try if you can simple ignore kunden and use an absolute path starting with 
/homepages/35/d..
Just check if ls /homepages works



Brilliant suggestion! That does work. I am building now. Used CMake suntax:


cmake -DCMAKE_BUILD_TYPE=RELEASE 
-DCMAKE_INSTALL_PREFIX=/homepages/35/d157794216/htdocs/build/oorexxbuild/release/opt/oorexx
 ../../ooRexx-5.0.0/oorexx-code-0

I had to fullpath as ~ has the funky link /kunden/ in it.

Now the compile (make) blows up at...


[ 80%] Building CXX object 
CMakeFiles/rexx.dir/interpreter/streamLibrary/StreamNative.cpp.o
[ 80%] Building CXX object 
CMakeFiles/rexx.dir/interpreter/streamLibrary/FileNative.cpp.o
[ 81%] Building CXX object 
CMakeFiles/rexx.dir/interpreter/platform/unix/RexxMain.cpp.o
Linking CXX shared library lib/librexx.so
[ 81%] Built target rexx
Scanning dependencies of target hostemu
[ 81%] Building CXX object 
CMakeFiles/hostemu.dir/extensions/hostemu/platform/unix/hostemu.cpp.o
[ 82%] Building CXX object 
CMakeFiles/hostemu.dir/extensions/hostemu/cmdparse.cpp.o
..\..\cmdparse.cpp: In function ‘int yyparse()’:
..\..\cmdparse.cpp:1603:35: warning: deprecated conversion from string constant 
to ‘char*’ [-Wwrite-strings]
..\..\cmdparse.cpp:1746:35: warning: deprecated conversion from string constant 
to ‘char*’ [-Wwrite-strings]
Linking CXX shared library lib/libhostemu.so
[ 82%] Built target hostemu
Scanning dependencies of target ncurses_cls
[ 82%] Generating bin/ncurses.cls
[ 82%] Built target ncurses_cls
Scanning dependencies of target orxncurses
[ 83%] Building CXX object 
CMakeFiles/orxncurses.dir/extensions/orxncurses/orxncurses.cpp.o
/homepages/35/d157794216/htdocs/build/ooRexx-5.0.0/oorexx-code-0/extensions/orxncurses/orxncurses.cpp:50:20:
 fatal error: curses.h: No such file or directory
 #include 
^
compilation terminated.
CMakeFiles/orxncurses.dir/build.make:54: recipe for target 
'CMakeFiles/orxncurses.dir/extensions/orxncurses/orxncurses.cpp.o' failed
make[2]: *** [CMakeFiles/orxncurses.dir/extensions/orxncurses/orxncurses.cpp.o] 
Error 1
CMakeFiles/Makefile2:167: recipe for target 'CMakeFiles/orxncurses.dir/all' 
failed
make[1]: *** [CMakeFiles/orxncurses.dir/all] Error 2
Makefile:137: recipe for target 'all' failed
make: *** [all] Error 2


Again, this was built from source SVN pull:
Checked out revision 11717.

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


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


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Erich Steinböck
Michael, I've uploaded
ooRexx-5.0.0-11716.ubuntu1604.x86_64-opt-oorexx-mdlueck.tar to
https://sourceforge.net/projects/oorexx/files/oorexx/5.0.0beta/
It's the installed files of an interpreter built on Ubuntu 16.04 using
cmake -DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_INSTALL_PREFIX=~/opt/oorexx and
packed with tar -cvf
ooRexx-5.0.0-11716.ubuntu1604.x86_64-opt-oorexx-mdlueck.tar opt/oorexx/
You might want to try if it works for you.

On Tue, Feb 5, 2019 at 5:36 PM Erich Steinböck 
wrote:

> Or try if you can simple ignore kunden and use an absolute path starting
> with /homepages/35/d..
> Just check if ls /homepages works
>
> On Tue, Feb 5, 2019 at 5:29 PM Erich Steinböck 
> wrote:
>
>> cmake -DCMAKE_BUILD_TYPE=RELEASE
>>> -DCMAKE_INSTALL_PREFIX=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
>>> -CMAKE_INSTALL_PREFIX=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
>>> ../../ooRexx-5.0.0/oorexx-code-0
>>> Still blows up... see attached.
>>
>>
>> My suggestion was to specify a relative path.  The command you show uses
>> absolute paths.
>> Also -CMAKE_INSTALL_PREFIX won't work, this must start with -D
>>
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Erich Steinböck
Or try if you can simple ignore kunden and use an absolute path starting
with /homepages/35/d..
Just check if ls /homepages works

On Tue, Feb 5, 2019 at 5:29 PM Erich Steinböck 
wrote:

> cmake -DCMAKE_BUILD_TYPE=RELEASE
>> -DCMAKE_INSTALL_PREFIX=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
>> -CMAKE_INSTALL_PREFIX=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
>> ../../ooRexx-5.0.0/oorexx-code-0
>> Still blows up... see attached.
>
>
> My suggestion was to specify a relative path.  The command you show uses
> absolute paths.
> Also -CMAKE_INSTALL_PREFIX won't work, this must start with -D
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-05 Thread Erich Steinböck
>
> cmake -DCMAKE_BUILD_TYPE=RELEASE
> -DCMAKE_INSTALL_PREFIX=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
> -CMAKE_INSTALL_PREFIX=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
> ../../ooRexx-5.0.0/oorexx-code-0
> Still blows up... see attached.


My suggestion was to specify a relative path.  The command you show uses
absolute paths.
Also -CMAKE_INSTALL_PREFIX won't work, this must start with -D
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-04 Thread Erich Steinböck
>
> lrwxrwxrwx4 root root1 Jul 23  2015 kunden -> /
>
kunden links to / ?  Sounds strange to me.

You might try to specify CMAKE_INSTALL_PREFIX as a relative path to avoid
going via /kunden
Are you using the most recent cmake available for your platform? You didn't
provide the actual cmake output, did you?
If all else fails, build on a different system (with the required PREFIX),
generate a .deb install file and install it on this system




On Sun, Feb 3, 2019 at 11:37 PM Michael Lueck 
wrote:

> Greetings Erich,
>
> Erich Steinböck wrote:
> > Hi Michael, I didn't miss your reply, I just wouldn't know what could be
> wrong here.
> >
> > I recreated your setup as accurately as possible on my Ubuntu 16.04 VM
> and cmake runs successfully for me.
>
>
> I have no idea how exactly the hosting provider (1&1) is mounting file
> systems. They never have allowed output of mount to show up. They used to
> let customers see the /etc/fstab... not any longer.
>
>
>
> > Are there any links involved in your build path?
>
> Trying to investigate what I can...
>
> (uiserver):u40009095:/$ ls -al | grep kunden
> lrwxrwxrwx4 root root1 Jul 23  2015 kunden -> /
>
> There is a link already right there!
>
> (uiserver):u40009095:/kunden$ ls -al | grep homepages
> drwxr-xr-x   59 root root 4096 Feb  3 17:17 homepages
>
> (uiserver):u40009095:/kunden/homepages$ ls -al | grep 35
> drwxr-xr-x 32 root root  4096 Aug 11 20:37 35
>
> (uiserver):u40009095:/kunden/homepages/35$ ls -al | grep d157794216
> drwxr-xr-t  7 root root 4096 Feb  3 00:38 d157794216
>
> (uiserver):u40009095:/kunden/homepages/35/d157794216$ ls -al | grep htdocs
> drwx---r-t 23 u40009095 ftpusers 4096 Jan 21 16:22 htdocs
>
>
>
>
> > Can you rd CMakeCache.txt and rerun cmake?
>
>
> I cleared out all the files in ~/build/oorexxbuild/release
>
> Tried the command again full pathing the prefix:
> cmake -DCMAKE_BUILD_TYPE=RELEASE
> -DCMAKE_INSTALL_PREFIX=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
> ../../ooRexx-5.0.0/oorexx-code-0
>
> Still blows up the same way.
>
> So I stated looking through for instances of "/kunden/kunden/" in the .txt
> output files. Some interesting results are showing up:
>
> Compiler: /kunden/kunden/usr/bin/cc
>
> That is not correct!
> (uiserver):u40009095:~/build/oorexxbuild/release$ which cc
> /usr/bin/cc
>
> Compiler: /kunden/kunden/kunden/kunden/usr/bin/c++
>
> Also not correct!
> (uiserver):u40009095:~/build/oorexxbuild/release$ which c++
> /usr/bin/c++
>
> Run Build Command:"/kunden/kunden/usr/bin/make"
> "cmTryCompileExec3372896991/fast"
> /kunden/kunden/usr/bin/make -f
> CMakeFiles/cmTryCompileExec3372896991.dir/build.make
> CMakeFiles/cmTryCompileExec3372896991.dir/build
> make[1]: Entering directory
> '/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeTmp'
> /kunden/usr/bin/cmake -E cmake_progress_report
> /kunden/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeTmp/CMakeFiles
> 1
> Building C object
> CMakeFiles/cmTryCompileExec3372896991.dir/testCCompiler.c.o
> cd
> /kunden/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeTmp
> && /kunden/kunden/usr/bin/cc-o
> CMakeFiles/cmTryCompileExec3372896991.dir/testCCompiler.c.o   -c
>
> /kunden/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeTmp/testCCompiler.c
> Linking C executable
> /kunden/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeTmp/cmTryCompileExec3372896991
> cd
> /kunden/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeTmp
> && /kunden/usr/bin/cmake -E cmake_link_script
> /kunden/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeTmp/CMakeFiles/cmTryCompileExec3372896991.dir/link.txt
> --verbose=1
> /kunden/kunden/usr/bin/cc
>  CMakeFiles/cmTryCompileExec3372896991.dir/testCCompiler.c.o  -o
> /kunden/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeTmp/cmTryCompileExec3372896991
> -rdynamic
> make[1]: Leaving directory
> '/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeTmp'
>
>
>
> I suspect something about that first link /kunden/ is making CMake to blow
> up. Correct?
>
>
>
> > Can you remove and recreate the full build path and then rerun cmake?
>
> Did I do above what you are asking for here?
>
>
> > Can you supply the full CMake output? (this should include your CMake
> version as above)
> > Can you try building on a different path, e. g. on /home/michael or such?
>
>
> No, not that far up the directory levels.
>
> Our web hosting account is rooted at:
>
> /kunden/homepages/35/d157794216/htdocs/
>
>
> I am thankful,
>
> --
> Michael Lueck
> Lueck Data Systems
> http://www.lueckdatasystems.com/
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>

Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-02-03 Thread Erich Steinböck
Hi Michael, I didn't miss your reply, I just wouldn't know what could be
wrong here.

I recreated your setup as accurately as possible on my Ubuntu 16.04 VM and
cmake runs successfully for me.

~~~
erichst@erich-vm:/$ md -p /kunden/homepages/35/d157794216/htdocs
erichst@erich-vm:/$ cd /kunden/homepages/35/d157794216/htdocs
erichst@erich-vm:/kunden/homepages/35/d157794216/htdocs$ mkdir -p
build/ooRexx-5.0.0
erichst@erich-vm:/kunden/homepages/35/d157794216/htdocs$ cd
build/ooRexx-5.0.0
erichst@erich-vm:/kunden/homepages/35/d157794216/htdocs/build/ooRexx-5.0.0$
svn checkout svn://svn.code.sf.net/p/oorexx/code-0/main/trunk oorexx-code-0
erichst@erich-vm:/kunden/homepages/35/d157794216/htdocs/build/ooRexx-5.0.0$
cd ..
erichst@erich-vm:/kunden/homepages/35/d157794216/htdocs/build$ mkdir
oorexxbuild
erichst@erich-vm:/kunden/homepages/35/d157794216/htdocs/build$ cd
oorexxbuild
erichst@erich-vm:/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild$
mkdir release
erichst@erich-vm:/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild$
cd release
erichst@erich-vm:/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release$
cmake -DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_INSTALL_PREFIX=../../../opt/oorexx
../../ooRexx-5.0.0/oorexx-code-0
-- CMake version is 3.5.1
-- Building for a 64-bit architecture
-- OOREXX_SHEBANG_PROGRAM: "/usr/bin/env rexx" (default)
-- Found Subversion: /usr/bin/svn (found version "1.9.3")
-- SVN Revision Number is 11708
-- CMAKE_INSTALL_PREFIX is /kunden/homepages/35/d157794216/htdocs/opt/oorexx
-- INSTALL_LIB_DIR is /kunden/homepages/35/d157794216/htdocs/opt/oorexx/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 - 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 - found
-- Looking for filehdr.h
-- Looking for filehdr.h - not found
-- Looking for fstat
-- Looking for fstat - found
-- Looking for gcvt
-- Looking for gcvt - 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
-- 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 pwd.h
-- Looking for pwd.h - found
-- Looking for sched.h
-- Looking for sched.h - found
-- Looking for sighold
-- Looking for sighold - found
-- Looking for strdup
-- Looking for strdup - found
-- Looking for strings.h
-- Looking for strings.h - found
-- Looking for stropts.h
-- Looking for stropts.h - found
-- Looking for sys/filio.h
-- Looking for sys/filio.h - not found
-- Looking for sys/ldr.h
-- Looking for sys/ldr.h - not found
-- Looking for sys/resource.h
-- Looking for sys/resource.h - found
-- Looking for sys/select.h
-- Looking for sys/select.h - found
-- Looking for sys/sem.h
-- Looking for sys/sem.h - found
-- Looking for sys/signal.h
-- Looking for sys/signal.h - found
-- Looking for sys/socket.h
-- Looking for sys/socket.h - found
-- Looking for sys/stat.h
-- Looking for sys/stat.h - found
-- 

Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-30 Thread Michael Lueck

Greetings Erich,

Erich Steinböck wrote:

Michael,
OS_DIST provides a string that will become part of the package name generated 
with CPack.  If you don't generate a package, there's no need to use this 
option.  Same for BUILD_DEB.

for the DCMAKE_INSTALL_PREFIX arg, what is the difference between full path specifying and passing in the ~ symbol? 


You can use any form of path specification, including full path. "~" is just a 
shortcut for the user's home directory.



I decided to try the build again on this cold evening here in Michigan. Here is 
how far I got:

Version: v5.0.0 Beta

mkdir ~/build/ooRexx-5.0.0
cd ~/build/ooRexx-5.0.0

svn checkout svn://svn.code.sf.net/p/oorexx/code-0/main/trunk oorexx-code-0

Checked out revision 11692.

Code gets downloaded to directory: ~/build/ooRexx-5.0.0/oorexx-code-0/

cd ..
mkdir oorexxbuild
cd oorexxbuild
mkdir release
cd release

cmake -DCMAKE_BUILD_TYPE=RELEASE -DCMAKE_INSTALL_PREFIX=~/opt/oorexx 
../../ooRexx-5.0.0/oorexx-code-0

-- Looking for usersec.h
-- Looking for usersec.h - not found
-- Looking for ncurses.h
-- Looking for ncurses.h - not found
CMake Error at CMakeLists.txt:1831 (add_subdirectory):
  add_subdirectory not given a binary directory but the given source
  directory
  
"/kunden/kunden/kunden/homepages/35/d157794216/htdocs/build/ooRexx-5.0.0/oorexx-code-0/samples"
  is not a subdirectory of
  
"/kunden/kunden/homepages/35/d157794216/htdocs/build/ooRexx-5.0.0/oorexx-code-0".
  When specifying an out-of-tree source a binary directory must be explicitly
  specified.


CMake Error at CMakeLists.txt:1834 (add_subdirectory):
  add_subdirectory not given a binary directory but the given source
  directory
  
"/kunden/kunden/kunden/homepages/35/d157794216/htdocs/build/ooRexx-5.0.0/oorexx-code-0/testbinaries"
  is not a subdirectory of
  
"/kunden/kunden/homepages/35/d157794216/htdocs/build/ooRexx-5.0.0/oorexx-code-0".
  When specifying an out-of-tree source a binary directory must be explicitly
  specified.


-- Configuring incomplete, errors occurred!
See also 
"/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeOutput.log".
See also 
"/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release/CMakeFiles/CMakeError.log".
(uiserver):u40009095:~/build/oorexxbuild/release$



Looks to me like the error is in stacking up multiple /kunden/ directories in 
the path. There should only be one:

(uiserver):u40009095:~/build/oorexxbuild/release$ pwd
/kunden/homepages/35/d157794216/htdocs/build/oorexxbuild/release


Suggestions / assistance please.

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


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


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-27 Thread CV Bruce
Thanks.  I just thought I’d ask since you seem to be the guru for the -D 
option.  This was in no way an enhancement request.

Yours,

Bruce
> On Jan 27, 2019, at 10:36 AM, Erich Steinböck  
> wrote:
> 
> Is there a build option that would allow me to rename the rexx executable to, 
> perhaps orexx?
> Tthat's not a supported scenario.
> You'd have to rename the binary manually. On Unix at least you could build 
> with -DORX_SHEBANG=/-your-install-path-/bin/orexx so that built rexx programs 
> have their shebangs modified accordingly.
> On Windows, you'd have to modify the file type association with ftype 
> RexxScript="d:\-your-install-path-\ooRexx\orexx.exe" "%1" %*
> I never tested anything like this, so you might experience other issues.
> ___
> 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] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-27 Thread Erich Steinböck
>
> Is there a build option that would allow me to rename the rexx executable
> to, perhaps orexx?
>
Tthat's not a supported scenario.
You'd have to rename the binary manually. On Unix at least you could build
with -DORX_SHEBANG=/-your-install-path-/bin/orexx so that built rexx
programs have their shebangs modified accordingly.
On Windows, you'd have to modify the file type association with ftype
RexxScript="d:\-your-install-path-\ooRexx\orexx.exe" "%1" %*
I never tested anything like this, so you might experience other issues.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-27 Thread CV Bruce
Hi Eric,

Is there a build option that would allow me to rename the rexx executable to, 
perhaps orexx?

Thanks,

Bruce
> On Jan 22, 2019, at 8:53 AM, Erich Steinböck  
> wrote:
> 
> Hi Michael,
> if you do not want to build to the default ooRexx install location /usr/bin, 
> set CMAKE_INSTALL_PREFIX to the desired path on the cmake command. To build 
> for an install to your home directory, you would use
> 
> cmake -DBUILD_DEB=1 -DOS_DIST=ubuntu1604 -DCMAKE_BUILD_TYPE=RELEASE 
> -DCMAKE_INSTALL_PREFIX=~/oorexx ../../oorexxsvn/main/trunk
> 
> To install without building a package, use make install
> 
> No APIService.cpp patching, ./configure, mkdir ~/opt/oorexx/var should be 
> necessary for 5.0.  The latest 5.0 trunk will no longer require rxapi to run 
> as root.
> 
> 
> I have just updated our How-to-build-ooRexx wiki at 
> https://sourceforge.net/p/oorexx/wiki/how-to-build-oorexx/ 
> I'll also update 
> CMake-build-readme.txt 
> 
> Please let us know of any issues you encounter.
> ___
> 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] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-26 Thread Erich Steinböck
Michael,
OS_DIST provides a string that will become part of the package name
generated with CPack.  If you don't generate a package, there's no need to
use this option.  Same for BUILD_DEB.

for the DCMAKE_INSTALL_PREFIX arg, what is the difference between full path
> specifying and passing in the ~ symbol?
>
You can use any form of path specification, including full path. "~" is
just a shortcut for the user's home directory.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-26 Thread Michael Lueck

Greetings Erich,

Erich Steinböck wrote:
if you do not want to build to the default ooRexx install location /usr/bin, set CMAKE_INSTALL_PREFIX to the desired path on the cmake command. To build for an install to your home directory, you 
would use


cmake -DBUILD_DEB=1 -DOS_DIST=ubuntu1604 -DCMAKE_BUILD_TYPE=RELEASE 
-DCMAKE_INSTALL_PREFIX=~/oorexx ../../oorexxsvn/main/trunk

To install without building a package, use make install



So since I am not intending to package this deployment (since I am non-root, 
and cannot install packages on the shared server)... what then is the purpose 
of leaving args:

-DBUILD_DEB=1 -DOS_DIST=ubuntu1604

Also, what is the supported list of DOS_DIST constants? Or is that a literal 
pass-through string?

Recall, I stated the the shared web server is running Debian, not Ubuntu.


Oh, and our hosting provider serves us on:
cat /etc/debian_version
8.11

uname -a
Linux infong531 3.16.0-ui18276.29-uiabi1-infong-amd64 #1 SMP Debian 
3.16.59-1~ui80+1 (2018-10-03) x86_64 GNU/Linux



Lastly, for the DCMAKE_INSTALL_PREFIX arg, what is the difference between full path specifying and passing in the ~ symbol?  The successful compile of ooRexx 4.2 I did for shared web hosting, I full 
pathed the prefix value.


#ooRexx 4.2 syntax
 ./configure --disable-static 
--prefix=/kunden/homepages/35/d157794216/htdocs/opt/oorexx

Noted, after getting cmake syntax established, I will perform a make and make install. 
"Getting close."

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


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


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-22 Thread Erich Steinböck
DESTDIR works differently. It allows to prepend a different top-level
directory, but the base directory would still be .../usr/bin
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-22 Thread Rony G. Flatscher
On 22.01.2019 17:53, Erich Steinböck wrote:
> Hi Michael,
> if you do not want to build to the default ooRexx install location /usr/bin, 
> set
> CMAKE_INSTALL_PREFIX to the desired path on the cmake command. To build for 
> an install to your
> home directory, you would use
>
> cmake -DBUILD_DEB=1 -DOS_DIST=ubuntu1604 -DCMAKE_BUILD_TYPE=RELEASE
> -DCMAKE_INSTALL_PREFIX=~/oorexx ../../oorexxsvn/main/trunk
>
> To install without building a package, use make install
>
> No APIService.cpp patching, ./configure, mkdir ~/opt/oorexx/var should be 
> necessary for 5.0.  The
> latest 5.0 trunk will no longer require rxapi to run as root.
>
>
> I have just updated our How-to-build-ooRexx wiki at
> https://sourceforge.net/p/oorexx/wiki/how-to-build-oorexx/
> I'll also update CMake-build-readme.txt
>
> Please let us know of any issues you encounter.

maybe the following can be helpful after running "make":

make DESTDIR=~/oorexx5 install   

"DESTDIR=someDestinationDirectory" allows one to install ooRexx anywhere on 
one's system. Then
"~/oorexx5/bin/rexx -e 'say address()' " should work.

---rony

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


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-22 Thread Erich Steinböck
Hi Michael,
if you do not want to build to the default ooRexx install location /usr/bin,
set CMAKE_INSTALL_PREFIX to the desired path on the cmake command. To build
for an install to your home directory, you would use

cmake -DBUILD_DEB=1 -DOS_DIST=ubuntu1604 -DCMAKE_BUILD_TYPE=RELEASE
-DCMAKE_INSTALL_PREFIX=~/oorexx ../../oorexxsvn/main/trunk

To install without building a package, use make install

No APIService.cpp patching, ./configure, mkdir ~/opt/oorexx/var should be
necessary for 5.0.  The latest 5.0 trunk will no longer require rxapi to
run as root.


I have just updated our How-to-build-ooRexx wiki at
https://sourceforge.net/p/oorexx/wiki/how-to-build-oorexx/
I'll also update CMake-build-readme.txt

Please let us know of any issues you encounter.
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

2019-01-21 Thread Michael Lueck

Greetings ooRexx'ers,

René Jansen wrote:


try: svn checkout svn://svn.code.sf.net/p/oorexx/code-0/main/trunk oorexx-code-0



All right, I am substituting the above syntax to pull the latest ooRexx v5 
source.

The last time I was building, I was targeting Ubuntu where I have root capabilities. I suspect some things in these next steps also need to be adjusted to just build raw, and to support the correct 
prefix for the compile and install.


From my notes from before:
cmake -DBUILD_DEB=1 -DOS_DIST=ubuntu1604 -DCMAKE_BUILD_TYPE=RELEASE 
../../oorexxsvn/main/trunk
make


So, needs to change to:
cmake -DBUILD_DEB=1 -DOS_DIST=ubuntu1604 -DCMAKE_BUILD_TYPE=RELEASE 
../../ooRexx-5.0.0/oorexx-code-0
make

As that is where svn download the files to.


My steps to build ooRexx v4.2 on Shared Linux Web Hosting were:

Version: ooRexx-4.2.0-source.tar.gz

Patch file: rexxapi/server/platform/unix/linux/APIService.cpp to be able to 
deal with being installed in a home directory rooted environment

% ./configure --disable-static 
--prefix=/kunden/homepages/35/d157794216/htdocs/opt/oorexx
% make
% make install
mkdir ~/opt/oorexx/var
mkdir ~/opt/oorexx/var/run

Symlinks for ooRexx 4.2.0 as follows:

Add a symlink to support libraries compiled against the old ORexx 2.x from IBM
~/opt/oorexx/lib >ln -s librexxapi.so.4.0.6 librexxapi.so.2

Add rexxtry.rex support from the command line
~/opt/oorexx/bin > ln -s ../share/ooRexx/rexxtry.rex rexxtry.rex
And put the proper shebang in that target file



So, suggestions:
To filename ../../ooRexx-5.0.0/oorexx-code-0/CMake-build-readme.txt add notes 
for:
1) Building on Linux
2) Building with a custom prefix
3) Installing raw after the compile verses for packaging


Oh, and our hosting provider serves us on:
cat /etc/debian_version
8.11

uname -a
Linux infong531 3.16.0-ui18276.29-uiabi1-infong-amd64 #1 SMP Debian 
3.16.59-1~ui80+1 (2018-10-03) x86_64 GNU/Linux


So, based on real Debian, not Ubuntu.


I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


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


Re: [Oorexx-devel] Releasing ooRexx 5.0?

2019-01-15 Thread René Jansen
Hi Michael,

try: svn checkout svn://svn.code.sf.net/p/oorexx/code-0/main/trunk oorexx-code-0

best regards,

René.   

> On 15 Jan 2019, at 13:35, Michael Lueck  wrote:
> 
> Greetings ooRexx'ers,
> 
> Rick McGuire wrote:
>> Also, with changes for rxapi, this really needs a longer beta-test to make 
>> sure we've not overlooked any major issues.
> 
> 
> This tells me it is time to do a pull/build on the 1&1 Linux Shared Web 
> Hosting server.
> 
> How do I do the correct source code pull?
> 
> I am thankful,
> 
> -- 
> Michael Lueck
> Lueck Data Systems
> http://www.lueckdatasystems.com/
> 
> 
> ___
> 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] Releasing ooRexx 5.0?

2019-01-15 Thread Michael Lueck

Greetings ooRexx'ers,

Rick McGuire wrote:

Also, with changes for rxapi, this really needs a longer beta-test to make sure 
we've not overlooked any major issues.



This tells me it is time to do a pull/build on the 1&1 Linux Shared Web Hosting 
server.

How do I do the correct source code pull?

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


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


Re: [Oorexx-devel] Releasing ooRexx 5.0?

2019-01-15 Thread René Jansen
Then we will not freeze. Can you give us a heads up when it is a convenient 
time to freeze?

I was happy we did not freeze last time, because it gave us the rxapi and 
usb-install functionality, the gencat elimination and some more.

best regards,

René.


> On 15 Jan 2019, at 11:51, Rick McGuire  wrote:
> 
> I am against a freeze, as I've got some changes in the works that I'd really 
> like to get into the 5.0 release. 
> 
> Rick
> 
> On Tue, Jan 15, 2019 at 10:46 AM René Jansen  > wrote:
> I am for it, but I think it is up to Erich and Rick.
> 
> To be precise, I am for freezing, setting a date and prepare. I would like to 
> have the oorexx.org  website up to date before we 
> announce. I did some work last year, which is accessible through 
> oorexx.org/index2.html  , but I need to finish 
> that. Also - documentation. We must be able to build it in a repeatable 
> fashion and not when someone’s pc has the right configuration. We are working 
> towards that, albeit slowly.
> 
> I was planning for the symposium, but I can imagine it would be better if we 
> did it earlier.
> 
> My proposal: freeze now and release March 1st.
> 

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


Re: [Oorexx-devel] Releasing ooRexx 5.0?

2019-01-15 Thread René Jansen
I am for it, but I think it is up to Erich and Rick.

To be precise, I am for freezing, setting a date and prepare. I would like to 
have the oorexx.org  website up to date before we announce. 
I did some work last year, which is accessible through oorexx.org/index2.html 
 , but I need to finish that. Also - 
documentation. We must be able to build it in a repeatable fashion and not when 
someone’s pc has the right configuration. We are working towards that, albeit 
slowly.

I was planning for the symposium, but I can imagine it would be better if we 
did it earlier.

My proposal: freeze now and release March 1st.

best regards,

René.

> On 15 Jan 2019, at 10:15, Rony G. Flatscher  wrote:
> 
> What would be the thoughts about releasing the current trunk version of 
> ooRexx 5.0 as "general
> available"?
> (In order for organisations/companies to adopt 5.0 or to replace older 
> versions of Rexx/ooRexx with
> 5.0 it would be necessary that it becomes officially GA.)
> 
> It would be still possible to create some ooRexx 5.1, 5.2 and the like 
> shortly after a GA release,
> if new functionality would be added to it (e.g. applying sandbox development 
> results or implementing
> RFEs).
> 
> ---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] Releasing ooRexx 5.0?

2019-01-15 Thread Rick McGuire
There is still documentation work that needs to be done, including doing a
very thorough review of the docs. There are still tests that need to be
written, and I'm working on a restructuring of rexxutil that is cleaning up
a lot of potential problems in that code. Also, with changes for rxapi,
this really needs a longer beta-test to make sure we've not overlooked any
major issues. It will be released when it is ready, and not one second
before. The same answer you have been given every other time you have asked
this question, so please stop asking.

Rick

On Tue, Jan 15, 2019 at 9:16 AM Rony G. Flatscher 
wrote:

> What would be the thoughts about releasing the current trunk version of
> ooRexx 5.0 as "general
> available"?
> (In order for organisations/companies to adopt 5.0 or to replace older
> versions of Rexx/ooRexx with
> 5.0 it would be necessary that it becomes officially GA.)
>
> It would be still possible to create some ooRexx 5.1, 5.2 and the like
> shortly after a GA release,
> if new functionality would be added to it (e.g. applying sandbox
> development results or implementing
> RFEs).
>
> ---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] Releasing ooRexx 5.0?

2019-01-15 Thread Gil Barmwater
I believe there is some documentation still to be done for the newer 
features but I would support a Release once that is done. However, I 
have not looked at all the RFEs and bugs to see what else might need to 
be done before we do that.


Gil B.

On 1/15/2019 9:15 AM, Rony G. Flatscher wrote:

What would be the thoughts about releasing the current trunk version of ooRexx 5.0 
as "general
available"?
(In order for organisations/companies to adopt 5.0 or to replace older versions 
of Rexx/ooRexx with
5.0 it would be necessary that it becomes officially GA.)

It would be still possible to create some ooRexx 5.1, 5.2 and the like shortly 
after a GA release,
if new functionality would be added to it (e.g. applying sandbox development 
results or implementing
RFEs).

---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


[Oorexx-devel] Releasing ooRexx 5.0?

2019-01-15 Thread Rony G. Flatscher
What would be the thoughts about releasing the current trunk version of ooRexx 
5.0 as "general
available"?
(In order for organisations/companies to adopt 5.0 or to replace older versions 
of Rexx/ooRexx with
5.0 it would be necessary that it becomes officially GA.)

It would be still possible to create some ooRexx 5.1, 5.2 and the like shortly 
after a GA release,
if new functionality would be added to it (e.g. applying sandbox development 
results or implementing
RFEs).

---rony



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