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
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/
_
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 thankf
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> 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 g
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'
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.
>
> 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'
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 pre
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
-DCMAK
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
packe
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/oore
>
> 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 pa
>
> 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
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/homep
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 b
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
>
> 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
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_PREF
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
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
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
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
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_INST
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.
25 matches
Mail list logo
