On Mon, Dec 24, 2018 at 12:49 PM Gil Barmwater
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-
he compilation and linking than I am by Cmake. How do
I add an LDFLAG?
--
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
confide
On Wed, Dec 5, 2018 at 11:01 AM Jack Woehr
wrote:
> Okay, we get pretty far, and then:
>
>
>
> ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more
> information.
> ld: 0711-781 ERROR: TOC overflow. TOC size: 85080 Maximum size: 65536
> collect
s/rexx.dir/build.make:5556: bin/librexx.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:659: CMakeFiles/rexx.dir/all] Error 2
make: *** [Makefile:150: all] Error 2
On Wed, Dec 5, 2018 at 8:33 AM Jack Woehr
wrote:
>
> I'll check out and try again later this morning. Thank ou.
>
>
Well, that was fast :)
I'll check out and try again later this morning. Thank ou.
On Wed, Dec 5, 2018 at 8:31 AM Rick McGuire wrote:
> I already committed the fix.
>
>
--
Jack Woehr
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE
Should I file a bug report?
On Wed, Dec 5, 2018 at 7:51 AM Rick McGuire wrote:
> And this is exactly the reason to use 5.0.0, to give us a chance to fix
> these sort of issues before we go gold.
>
> On Wed, Dec 5, 2018 at 9:47 AM Jack Woehr
> wrote:
>
>> Rick, Erich:
L
AIX just doesn't define the latter
why? AIX is the first maliciously POSIX compliant system
On Wed, Dec 5, 2018 at 4:13 AM Rick McGuire wrote:
It looks like the ARGUMENT_TYPE issue is also fixed in the 4.2 branch that
> Erich pointed out too, but I still recommend you switch to 5.0.0.
>
--
der(_Tp, _Up)':
./api/oorexxapi.h:3697:21: error: 'ARGUMENT_TYPE___x' was not declared in
this scope
#define __type(t) ARGUMENT_TYPE_##t
^
./api/oorexxapi.h:3697:21: error: 'ARGUMENT_TYPE___y' was not declared in
this scope
#define __type(t) ARGUMENT_
'_RexxPackageObject*
GetRoutinePackage(RexxThreadContext*, RexxRoutineObject)':
./interpreter/api/ThreadContextStubs.cpp:579:12: error: cannot convert
'bool' to 'RexxPackageObject {aka _RexxPackageObject*}' in return
return false;
^
--
Jack Woehr
Absol
/svn.code.sf.net/p/oorexx/code-0/main/releases/4.2.0/trunk
> trunk
>
>
--
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
/trunk
> Please try checking out source from this location
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
--
Jack Woehr
Absolute Performance, Inc.
1230
27;:
./interpreter/api/ThreadContextStubs.cpp:594:12: error: cannot convert
'bool' to 'RexxPackageObject {aka _RexxPackageObject*}' in return
return false;
^
make: *** [Makefile:2566: librexx_la-ThreadContextStubs.lo] Error 1
--
Jack Woehr
Absolute Performance, Inc.
12
ith OORexx/BSF4ooRexx that I have
tested works properly
* everything that I have tried so far from your menu application works properly
Thanks for this very useful tool which you created and have been maintaining
for .. what ... 9 years now? Longer?
--
Jack Woehr # "Democracy is the
g the menu! Had no idea it was
there :)
--
Jack Woehr # "Democracy is the theory that the common people
Box 51, Golden CO 80402 # know what they want, and deserve to get it
http://www.softwoehr.com #
Jack Woehr wrote:
> Rony G. Flatscher wrote:
>>
>> One thing everyone can do to test the installation and the information
Oops, I found the jar ... forgot that Sierra moves everything to /Library
instead of /System/Library
--
Jack Woehr # "Democracy is the th
-
After install,
1. I don't find BSF4ooRexx on any Mac menu.
2. I can't find (haven't done a whole disk search) the BSF4ooRexx jar file
anywhere it's ever been before.
I do find the rexxj* shell files in /usr/local/bin but they complain about not
being able to find the clas
Rony G. Flatscher wrote:
>
> From now on that package will carry the correct name after unzipping. Sorry
> for the inconvenience!
Thanks for clarifying, I'll give it a try!
--
Jack Woehr # "Democracy is the theory that the common people
Box 51, Golden CO 80402
g a zipped Apple installation package (so
you can get your hands on the ooRexx 5.0.0beta on MacOSX as well with b4r_600_500_65Bit_macosx.zip
<https://sourceforge.net/projects/bsf4oorexx/files/beta/20161026/b4r_600_500_65Bit_macosx.zip/download>).
--
Jack Woehr # "Democracy is
Dave Jones wrote:
>> ln: '/usr/lib/librexx.so' and '/usr/lib/librexx.so.4.0.6' are the same
maybe the args you wrote to ln are in the wrong order:
ln -s reallib symlink
is the correct order
and it should be a soft link (-s)
>>
--
Jack Woehr
ln: '/usr/lib/librexx.so' and '/usr/lib/librexx.so.4.0.6' are the same
file
Looks like the archiving process copied both the file and the link into the
archive in some fashion.
Make sure the link is not added to the archive and create the link in the
post-processi
Michael Lueck wrote:
> However for legacy support, I do end up touching Windows frequently. ;-)
> Valid question still stands. I am thankful,
Last I checked OORexx runs in Cygwin xterms. Are those broken in Windows 10?
--
Jack Woehr # "Democracy is the theory that
Michael Lueck wrote:
> I would think ooRexx would need some sort of replacement of cmd.exe to send
> shell commands to.
The replacement is readily available. It's called "Linux" :)
--
Jack Woehr # "Democracy is the theory that the common people
Box 51
obably ObjectRexx and BSF4ooRexx can support one rev back to Java 7 safely.
--
Jack Woehr # "You must take your opponent into a deep dark forest
Box 51, Golden CO 80402 # where 2+2=5, and the path leading out is only wide
http://www.softwoehr.com # enough for one." - M
Erich Steinböck wrote:
> Let us know if you find other instances of this issue
Looks like the other samples are quoted correctly.
Loving proto-5.0.0 ... even have BSF running by softlinking librexx.so.4 ->
librexx.so etc.
Haven't tried on the Mac yet.
--
Jack Woehr
Jack Woehr wrote:
> -::requires treeDirectory.cls
> +::requires 'treeDirectory.cls'
I'm curious, not having been following too closely the mood of the OORexx dev
community.
Is Linux a tertiary platform for OORexx folks, after Windows and Mac?
If not, would you like some di
Jack Woehr wrote:
> CVBruce wrote:
>> Interesting. If you move treeDirectory.cls to the same place
> Uppercase issues.
>
>
jax@simandl:/usr/local/src/OORexx/oorexx-code-0/samples$ svn diff
Index: usetree.rex
=
les$ rexx ./usetree.rex
56 *-* ::requires treeDirectory.cls
REX0043E: Error 43 running
/usr/local/src/OORexx/oorexx-code-0/samples/usetree.rex line 56: Routine not
found.
REX0418E: Error 43.901: Could not find file "TREEDIRECTORY.CLS" for ::REQUIRES.
--
Jack Woehr # &
/usr/local/src/OORexx/oorexx-code-0/samples/usetree.rex line 56: Routine not
found.
REX0418E: Error 43.901: Could not find file "TREEDIRECTORY.CLS" for ::REQUIRES.
jax@simandl:/usr/local/src/OORexx/oorexx-code-0/samples$ echo $REXX_PATH
/usr/local/src/OORexx/oorexx-code-0/samples
k.engelbrechtsmuel...@gmx.at wrote:
I had to install following libraries to successfully execute the build:
sudo apt-get install build-essential -y
sudo apt-get install libncurses5-dev libncursesw5-dev
Tried it, that works for me, thank you!
--
Jack Woehr # "You must take
-essential -y
sudo apt-get install libncurses5-dev libncursesw5-dev
Thanks, I just shut down, will try that tomorrow.
--
Jack Woehr # "You must take your opponent into a deep dark forest
Box 51, Golden CO 80402 # where 2+2=5, and the path leading out is only wide
efile2:747: recipe for target 'CMakeFiles/orxncurses.dir/all'
failed
make[1]: *** [CMakeFiles/orxncurses.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2
Any tips?
--
Jack Woehr # "You must take your opponent into a deep
René Jansen wrote:
> I also think that this makes for more clarity than /usr/local/bin and
> /usr/local/lib, either to find things or to
> uninstall them.
How about /opt/oorexx
--
Jack Woehr # "There's too much emphasis on things
Box 51, Golden CO 80402 #
ns are followed by the complete path specification of the program
file.
--
Jack Woehr # "There's too much emphasis on things
Box 51, Golden CO 80402 # like pawn structure in modern chess.
http://www.softwoehr.com # Checkmate ends the g
Jack Woehr wrote:
Rony G. Flatscher wrote:
Is there anyone who has created a MacOSX version of 5.0 from trunk? If not, is
anyone interested in doing so?
I can try building on MacOSX if that would help.
The new instructions are not terribly helpful and I didn't install because I w
Rony G. Flatscher wrote:
> Is there anyone who has created a MacOSX version of 5.0 from trunk? If not,
> is anyone interested in doing so?
I can try building on MacOSX if that would help.
--
Jack Woehr # "There's too much emphasis on things
Box 51, Golden CO 804
/
Linux 5.0 builds are running on René's build server at
http://build.netrexx.org/jenkins/ but no build output has yet
been made available to the public.
No alpha for OpenBSD? :)
--
Jack Woehr # "There's too much emphasis on things
Box 51, Golden CO 80402 # like pa
Is anyone interested in trying to get OpenObjectRexx running on OpenBSD?
I had heard from René Jansen in December/January but just wondering if anyone
is pursuing this.
I might be in a better position now to help support such an effort.
--
Jack Woehr # "There's too muc
Erich Steinböck wrote:
Is there anywhere a concise listing of known bugs in 4.2.0?
Jack, the ooRexx Bug Tracker ist at https://sourceforge.net/p/oorexx/bugs/
I found the bug tracker, just not sure how to interpret some of the issues ...
thanks.
--
Jack Woehr # "Th
Is there anywhere a concise listing of known bugs in 4.2.0?
--
Jack Woehr # "There's too much emphasis on things
Box 51, Golden CO 80402 # like pawn structure in modern chess.
http://www.softwoehr.com # Checkmate ends the game.&q
ar in your
CLASSPATH you can
try out the test scripts in pigiron/scripts/oorexx/functest for examples of
usage.
Of course one will need to check out the latest code and build PigIron, because
I have not yet made a new release.
--
Jack Woehr # "There's too much emphasi
René Jansen wrote:
> Seems good, will look into that.
> Thanks!
Thanks, René, I and some other individuals with exposure to ObjectRexx and a
deep commitment to OpenBSD look forward to
a successful port!
happy new year,
Jack
>
> best regards,
>
> René
>> On 3 jan. 20
René Jansen wrote:
> Jack,
>
> do you have a logon on an OpenBSD machine for me? We can make it work.
>
René, I discover that http://devio.us offers free OpenBSD shell accounts. Would
that be satisfactory for trying to make
ObjectRexx compile on OpenBSD?
--
Jack Woehr
René Jansen wrote:
> do you have a logon on an OpenBSD machine for me? We can make it work.
My co-location provider is a friend of mine and is away from the New Year's
holiday, but we chatted briefly.
I will set up an OpenBSD instance for you probably sometime next week.
--
Ja
Jack Woehr wrote:
> René Jansen wrote:
>> do you have a logon on an OpenBSD machine for me? We can make it work.
>>
>
> I do not currently have an OpenBSD machine you could access. Let me look into
> that, please, and I will post again.
>
Of course, the easiest thing
René Jansen wrote:
> do you have a logon on an OpenBSD machine for me? We can make it work.
>
I do not currently have an OpenBSD machine you could access. Let me look into
that, please, and I will post again.
--
Jack Woehr # "There's too much emphasis on things
B
forms.
I never had any trouble debugging ooRexx, but it won't build on OpenBSD.
--
Jack Woehr # "There's too much emphasis on things
Box 51, Golden CO 80402 # like pawn structure in modern chess.
http://www.softwoehr.com # Checkmate en
Chip Davis wrote:
> That's interesting. I played around with Forth back in the mid-70's and,
> while
> I have never been a fan of RPN, I remember being impressed with its
> flexibility.
>
> What I don't remember is there being any sort of list construct that took an
> index.
: regards ( --) 2
Chip Davis wrote:
> _Only_C_programmers_ adjust their thinking to start lists with '0'.
>
>
Nah, we did that in Forth too.
--
Jack J. Woehr# Reality is unpredictable, and no amount of computer
technology
http://www.well.com/~jax # is going to change that. - David Brooks,
conserv
David Ashley wrote:
C uses zero-based indexes for thing like
memory, array positions, etc. My code could be architected to either
carry this forward to the ooRexx interface when it calls the C functions
or it could translate the zero-based numbers to the more user friendly
(and Rexx default)
Jack Woehr wrote:
Got busy with other stuff, mostly learning to play the trumpet.
If he gets it going on z/Linux, he'll still run into that rxapi problem
I'm pretty sure.
Awesome. I'll try to sneak away from the brass to the iron and give it a
shot.
--
Jack J. Woehr
Rick McGuire wrote:
> I was sure I had seen a similar traceback to this one before, so I
> search my mail archives again. I did see this...this is the same
> problem Jack Woehr encountered back in October, which we unfortunately
> never solved. He was also trying to build on Z Linux
Rick McGuire wrote:
> Which are all possibilities I've already eliminated.
>
You have looked in /var/log to see if anything interesting is being
reported?
--
Jack J. Woehr# "Self-delusion is
http://www.well.com/~jax # half the battle!"
http://www.softwoehr.com # - Zippy the Pinhead
Rick McGuire wrote:
> Jack,
>
> I know how this works. I wrote that code. This is just a very
> standard client-server pattern (implemented as objects).
Oh, and I did not mean to criticise the design pattern. I've used
it myself. I just meant there's something hiding in the implementation.
On Op
Rick McGuire wrote:
> I'm looking
> for an explanation for why making a request involving a second send
> operation for a tiny bit of data would make this operation two orders
> of magnitude slower than an operation that involves just a single
> send.
>
Um, because in the second case something (
Rick McGuire wrote:
> Does anybody have any insights into why this problem might be
> occurring? I'm not seeing anytihng similar in Windows, but AIX and
> Linux appear to be hit by the same problem, and I'm stumped as to the
> root cause.
It's somehow related to why rxapi goes off into neverland o
Rick McGuire wrote:
> Ok, I've managed to kill rxapi, but I still have a problem that I'm
> only able to start it if I'm running as root.
>
>
That's because it tries to write to /var/run ... that's why there's
a comment-out field RUN_AS_DAEMON in one of OORexx's files. You
comment that out and i
Well, for what it is worth, I have found where 4.0 rxapi hangs on OpenBSD.
rexxapi/common/platform/unix/SysCSStream.cpp:
/**
* Read from the connection.
*
* @param buf Target buffer for the read operation.
* @param bufsize Size of the target buffer.
* @param bytesr
Rainer Tammer wrote:
What happens if a user (non root) starts rxapi on a machine and the a
other user (root or non root) also starts rxapi ?
ISTR that an rexx instance looks for rxapi by the PID file. Since your
user rxapi instance can't overwrite root's PID file
of the same name, root wins.
r
Rainer Tammer wrote:
> Hello,
> I have changed the unix/SysSemaphore.hpp a bit:
>
>
>
Sounds like Rainer is closing in or has closed in upon the same sort of
problem
I'm looking at with rxapi ...
--
Jack J. Woehr# "Self-delusion is
http://www.well.com/~jax # half the battle
Rick McGuire wrote:
> All of the manager subsystems run in the rxapi process. They are just
> object instances that manage each of the APIs inside rxapi, so nothing
> else gets started other than rxapi.
>
>
Thanks, now I know where to look during my next episode of
"Dammit, OORexx has GOT to r
Rick McGuire wrote:
> One of the first things the Rexx client will do will contact the rxapi
> daemon asking it to create a "session queue" for that process.
>
I've traced through this in gdb. It seems to execute correctly.
> In-bound
> requests get dispatched to 1 of 3 subsystems (the queue ma
Debugging 4.0 on OpenBSD .. rxapi seems to go away looking for the Queue ..
Anybody have any comments about the interaction of rxapi with the Queue
to save me research time, or am I the first archaeologist to excavate there
in recent memory? :)
--
Jack J. Woehr# "Self-delusion is
http
Jack Woehr wrote:
*Re: [Oorexx-devel] More Building 4.0 on OpenBSD 4.3*
From: Rick McGuire <[EMAIL PROTECTED]> - 2008-10-11 17:23
ooRexx has launches a daemon process call rxapi, which is used to
manage the IPC used for queues, function registrations, and
macrospace.
Here we see that yes
>
> *Re: [Oorexx-devel] More Building 4.0 on OpenBSD 4.3*
> From: Rick McGuire <[EMAIL PROTECTED]> - 2008-10-11 17:23
> ooRexx has launches a daemon process call rxapi, which is used to
> manage the IPC used for queues, function registrations, and
> macrospace. That process is started when required
David Ashley wrote:
> There is no configure option, unfortunately. This is because the people
> who have gotten this working have not contributed their fixes back to
> the project. So the project team has no idea how they got things working.
>
Well, I will work on this in the background. The t
Rick McGuire wrote:
> Wow, I can't think of any circumstances that would produce that
> particular stack trace other than "compiler bug". A lot of that stack
> trace doesn't even make sense to me, particularly the bit that was the
> root cause of the problem back in register command handlers.
>
Rick McGuire wrote:
> By stack traceback, I'm referring to a traceback obtained by a
> debugger when a segfault happens. There's nothing in the Rexx code
> that's capable of generating that information itself.
>
Ah. Okay. I know there are some funky Rexx commandline options, thought
you were
Rick McGuire wrote:
> Note also that 4.0 should be capable of working in 64-bit mode.
Well, rexximage segfaults during the build.
> If
> you're getting a crash, please try to provide more information that
> "it crashes". At stack traceback, for example, would be a great
You know what would be gr
David Ashley wrote:
>
> 1. ooRexx 3.2.0 MUST be built as a 31-bit application
>
Yeah, I see the problem I'm having is it's trying to build 64. Is there
a configure option
to suppress that behavior?
> 2. There are some minor problems which can be worked around
> 3. This will all be much easier w
I used to see this all the time in Solaris like three years ago and then
you guys fixed it.
Anybody know what this turned out to be for Sol?
May if I #ifdef whatever's #ifdef'ed for Solaris, it will run on Linux
for Z.
(cd .libs && rm -f librexxutil.la && ln -s ../librexxutil.la
librex
Anybody else building any version of OORexx on Linux 390?
--
Jack J. Woehr# "Self-delusion is
http://www.well.com/~jax # half the battle!"
http://www.softwoehr.com # - Zippy the Pinhead
-
This SF.Net email is
David Ruggles wrote:
> For us it was because the telephony interface started back around '95 on
> OS/2 and Rexx was the scripting language. Since then we've migrated to other
> platforms and have brought Rexx with us.
>
Yeah, see, it's the same discussion. Forth hung around like that for
years,
David Ruggles wrote:
> Personally: my company uses ooRexx in three areas: server-side web
> development, back-end processing (often using OLE to automate MS Excel) and
> telephony integration with Asterisk. We do this on a mixture of Linux and
> Windows. ooRexx has been a good fit for us in this so
David Ashley wrote:
All -
This is a very interesting read.
http://weblog.infoworld.com/archives/emailPrint.jsp?R=printThis&A=/article/08/10/13/42TC-dynamic-futures_1.html
I would like to start a discussion on where we go next so ooRexx can
play successfully in this kind of future.
Interes
Mark Miesfeld wrote:
> You can use svn status -u to see if any your local files are out of
> date with the files on the repository.
>
Thanks. Built it, though I will post one patch to the tracker, a patch
which didn't get in apparently.
But the result at runtime is the same.
Jack J. Woehr
Mark Miesfeld wrote:
> You are making sure you keep your source tree up to date aren't you?
>
Um, *thought* I was. The semantics of svn diff are different than cvs
diff ...
Building afresh right now. Though I did mention on the list I have the same
problem with 3.2 on OBSD.
Thanks!!
--
Jack
Getting there. There are little platform reasons rxapi doesn't want to
run. I have it
running now but the client doesn't connect. I'm on it ...
--
Jack J. Woehr# "Self-delusion is
http://www.well.com/~jax # half the battle!"
http://www.softwoehr.com # - Zippy the Pinhead
Hmmm ... if I edit APIService.cpp
// #define RUN_AS_DAEMON
so the OOREXX_PIDFILE is "/tmp/ooRexx.pid" I can start rxapi by hand.
With the pidfile set to /var/run/ooRexx.pid it "can't find PID file".
Then things still don't work, but it doesn't leave the mis-forked parent
around spinning.
Rick McGuire wrote:
> That's a question that David will need to answer, I think.
>
> On Sat, Oct 11, 2008 at 1:54 PM, Jack Woehr <[EMAIL PROTECTED]> wrote:
>
>> Rick McGuire wrote:
>>
>>> ooRexx has launches a daemon process call rxapi,
>
Rick McGuire wrote:
> ooRexx has launches a daemon process call rxapi,
Does it matter that the script bin/rxapid is hideously wrong
for OpenBSD? Or is that just an optional tool for launching
rxapi at bootup?
--
Jack J. Woehr# "Self-delusion is
http://www.well.com/~jax # half the bat
Rick McGuire wrote:
ooRexx has launches a daemon process call rxapi, which is used to
manage the IPC used for queues, function registrations, and
macrospace. That process is started when required, and converts
itself to a system daemon that continues to run when the spawning Rexx
process termina
Rick McGuire wrote:
> I've applied these patches, but it would be helpful in the future if
> you submitted patches using the Patches Tracker system:
>
> https://sourceforge.net/tracker/?group_id=119701&atid=684732
>
Oops, had no idea it were there :)
> It's strange that you get similar
> symptom
This is a summary of diffs (two already posted) after which trunk builds
with a lot less warnings.
But rexx still spins on input, and when ^C'ed, rexx leaves a rexx
process spinning that has to be kill'ed
separately ... the api mgr?
Index: rexxapi/server/RegistrationManager.cpp
=
uname -m = i386
uname -r = 4.3
uname -s = OpenBSD
uname -v = 4.3#0
/usr/bin/uname -p = Intel(R) Pentium(R) 4 CPU 3.00GHz ("GenuineIntel"
686-class)
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = OpenBSD.i386
/usr/convex/getsysinfo = unknown
hostinfo
Rick McGuire wrote:
That looks like a semaphore or shared memory problem with the rexxapi
codecode that is not well understood and scheduled for replacement
in 4.0. You might be better off trying to get things working with the
4.0 codebase.
I've built 4.0 and it does the same thing
Because my head didn't hurt enough yet, I'm back playing with OORexx on
OpenBSD.
3.2.0 compiles but doesn't run correctly. Anytime anything like console
I/O is called for
it busywaits with an error and has to be killed externally, doesn't get
the SIG_QUIT. E.g.,
here is the ktguard.rexx sampl
David Ruggles wrote:
I'm not here to argue which one is correct (I'm sure Linux is) However, it's
not working even in accordance with what's documented.
Excuse me for misunderstanding your problem. I thought you were troubled
merely w/r/t the skew
between L and W.
Do you have a copy of ?
David Ruggles wrote:
> As I mentioned before Linux seems to treat sockets differently then windows.
>
No, Windows treats sockets differently than Linux, always has, and has
often been wrong
thereby. The crappy Redmond implementation in NT throughout the 1990's
helped create a
wider market for
Moritz Hoffmann wrote:
Here are some instructions on building ooRexx trunk on Solaris 10 using
SunStudio:
http://oorexx.wiki.sourceforge.net/compileSolarisSunStudio
Awesome. That link needs a trailing directory slash BTW. Also, it
doesn't seem to show up in
the list of pages for some reas
Dan Carter wrote:
> Jack, I have a pair of Ultra 20's on which I plan to install ooRexx. Is
> there anything not obvious that I should know? I also have a SPARC
> server that will want to place it on, as well, but that is far into the
> future. All three machines are SOL10.
>
I believe 3.2.
Moritz Hoffmann wrote:
> Jack Woehr wrote:
>
>> Plodding along in the background at compiling 4.0 on Solaris
>>
> Is this Solaris for x86 or SPARC?
>
x86 ... I have two (old) Sparc machines, both running OpenBSD. They're a bit
slow for developing ObjectRex
Dan Carter wrote:
>
> Jack, thanks for your running commentary on installing ooRexx 4.0 on
> solaris. I am not an experienced Solaris anything, but I will install
> 4.0 on my Solaris boxes as soon as I can. Your notes will be most
> helpful.
>
"Install" is too fine a word for where I've gotte
Plodding along in the background at compiling 4.0 on Solaris
* had to #include in
rexxapi/common/platform/unix/SysCSStream.hpp for bcopy()
* think also it needs -lxnet.so to link
--
Jack J. Woehr# "Self-delusion is
http://www.well.com/~jax # half the battle!"
http://www.
David Ashley wrote:
The problem here is that on *nix environment the base environment is
*owned* byt the parent spawning process. On Windows you get a copy of
the environment when the process starts. On *nix the environment is
inherited form the spawning process and since you do not own the
spawn
Dan Carter wrote:
>
> Do you know of a VM/CMS workalike that runs under SUSE?
>
Well, you can run VM/CMS on top of Hercules System/370, ESA/390, and
z/Architecture Emulator
http://www.hercules-390.org/
Of course you have to have VM to run it!
--
Jack J. Woehr# "Self-delusion i
Moritz Hoffmann wrote:
David Ashley wrote:
That patch should be safe to apply.
This builds:
Index: rexxapi/common/platform/unix/SysCSStream.cpp
===
--- rexxapi/common/platform/unix/SysCSStream.cpp(revision 342
Hmm ... I mailed this message days ago and it just arrived at my
mailbox. So I see why that
other developer was puzzled by his non-receipt of email from the list.
Jack Woehr wrote:
> Rick McGuire wrote:
>
>> I have no idea what version of the code you're try
Rick McGuire wrote:
> I have no idea what version of the code you're trying to build from,
>
Straight from SourceForge cvs up -PAd
Does trunk reside somewhere else now?
--
Jack J. Woehr# "Self-delusion is
http://www.well.com/~jax # half the battle!"
http://www.softwoehr.com # -
http://oorexx.wiki.sourceforge.net/message/list/REXX+Friendly+Editors
1. Can't post discussion to the Wiki discussion. Is this locked or is
this just another
aspect of SourceForge that is broken over the past few days with all the
trouble
they are having in the migration to Chicago?
2. Is the W
Trying to build 4.0 on OpenBSD 4.3.
Here first are two diffs ... not suggested verbatim for the tree but
showing what
I have to do to make it compile at all:
Index: rexxapi/common/platform/unix/SysCSStream.cpp
===
--- rex
1 - 100 of 129 matches
Mail list logo
