On Thu, Apr 15, 2010 at 1:16 PM, Rick McGuire wrote:
> On Thu, Apr 15, 2010 at 4:05 PM, CVBruce wrote:
>>
>> The question I have is this.
>>
>> I can make three different installer packages, or I could make one
>> universal binary installer package. What do you think our users would
>> prefer?
>
If you've had problems in the past with people getting the wrong
version, then I agree universal would be the way to go. Let the
operating system figure out which on it wants to run. It would also
benefit those that have to install on many machines, just one install
method.
I'll start wo
On Thu, Apr 15, 2010 at 4:05 PM, CVBruce wrote:
> Well it looks like I've create 3 working versions of ooRexx, one each
> architecture in i386, x86_64, and ppc. They all pass testOORexx.rex.
> I haven't been able to make a ppc64 version yet. Not sure why.
>
> The question I have is this.
>
> I c
Well it looks like I've create 3 working versions of ooRexx, one each
architecture in i386, x86_64, and ppc. They all pass testOORexx.rex.
I haven't been able to make a ppc64 version yet. Not sure why.
The question I have is this.
I can make three different installer packages, or I could m
On Thu, Apr 15, 2010 at 8:57 AM, CVBruce wrote:
> It's got to be something like that.
> When I build the x86_64 architecture, rexximage hung.
> The ppc buss erred.
> I deleted my /opt/ooRexx installation, which was i386, and stopped the rxapi
> server/service, and I think that was the problem. L
It's got to be something like that.
When I build the x86_64 architecture, rexximage hung.
The ppc buss erred.
I deleted my /opt/ooRexx installation, which was i386, and stopped the
rxapi server/service, and I think that was the problem. Look I know
have a ppc executable:
bjske...@bookwormm
On Thu, Apr 15, 2010 at 7:53 AM, Rick McGuire wrote:
> rexximage is building the loadable class image (rexx.img file) that is
> part of the interpreter. We've seen this exception before, and
> typically it is seen when there's some confusion in the build as to
> whether the code is running in 32
rexximage is building the loadable class image (rexx.img file) that is
part of the interpreter. We've seen this exception before, and
typically it is seen when there's some confusion in the build as to
whether the code is running in 32-bit or 64-bit mode. Unfortunately,
it can also be a sign of a
Hi All,
I'm still working on trying to create a PowerPC(ppc) version of 4.0.1
Beta 1. Just to recap, the i386 version works just fine.
I guess rexximage is executed during the make. i386, no problem, ppc
I get:
./rexximage
creating the system specific methods ...
Adding setlike methods to R
