All,
I placed Windows installation packages on the build machine:
http://build.oorexx.org/builds/interpreter-main/6209/windows/
There are 32-bit and 64-bit builds of 4.1.0 and 4.2.0, both debug and
non-debug versions.
--
Mark Miesfeld
On Tue, Sep 21, 2010 at 9:56 AM, Brandon Cherry wrote:
> S
I have verified that the fixes work on openSUSE 1.3. So I think we can put
this one to bed.
David Ashley
On 09/23/2010 08:08 AM, Manfred Lotz wrote:
> On Thu, 23 Sep 2010 08:10:16 -0400
> Rick McGuire wrote:
>
>> Ok, a slightly different new operator declaration defeated my global
>> search.
On Thu, Sep 23, 2010 at 1:53 PM, David Ashley
wrote:
> Although not yet commited, I am playing around with the RPM spec file for
> ooRexx. I have added some new macros to the file that create additional
> information in the name of the RPM. A typical RPM name produced by these
> macros
> looks l
All -
Although not yet commited, I am playing around with the RPM spec file for
ooRexx. I have added some new macros to the file that create additional
information in the name of the RPM. A typical RPM name produced by these macros
looks like this:
ooRexx-4.2.0-6212.fedora13.x86_64.rpm
This is really good news. I will bring the openSuse 11.3 VMs back up on the
build machine and see if it all works.
David Ashley
On 09/23/2010 08:08 AM, Manfred Lotz wrote:
> On Thu, 23 Sep 2010 08:10:16 -0400
> Rick McGuire wrote:
>
>> Ok, a slightly different new operator declaration defeate
On Thu, 23 Sep 2010 08:10:16 -0400
Rick McGuire wrote:
> Ok, a slightly different new operator declaration defeated my global
> search. I just committed a fix for the RexxMemory problem. I think
> that get's all of the problem places.
>
> Rick
>
Yep, that did it. Now it builds nicely on my s
Ok, a slightly different new operator declaration defeated my global
search. I just committed a fix for the RexxMemory problem. I think
that get's all of the problem places.
Rick
On Thu, Sep 23, 2010 at 7:58 AM, Manfred Lotz wrote:
> On Thu, 23 Sep 2010 07:07:58 -0400
> Rick McGuire wrote:
>
On Thu, 23 Sep 2010 07:07:58 -0400
Rick McGuire wrote:
> I just took another look at this, and found a description of the
> problem that gave me more information on what the root cause of the
> error. This problem appears to be much less pervasive than I
> originally suspected. I committed a ch
Since we frequently celebrate each 1000 commits on this project, I
thought I'd mention that the Apache Software Foundation just had their
1 millionth commit! I've been working on ASF projects long enough to
remember when they hit 500,000.
Rick
I just took another look at this, and found a description of the
problem that gave me more information on what the root cause of the
error. This problem appears to be much less pervasive than I
originally suspected. I committed a change to trunk that I *think*
will correct this, but I don't have
gcc 4.5 introduced an error that is causing these failures.
Unfortunately, this is not a simple fix in the code. This problem
might be fixed in the 4.5.1 version, but I'm not aware that anybody
has tried the experiment yet.
Rick
On Thu, Sep 23, 2010 at 6:12 AM, Manfred Lotz wrote:
> Hi folks,
>
Hi folks,
I'm running Arch Linux and tried to build oorexx ooRexx-4.0.0 on x86-64
architecture and got the following:
g++ -DHAVE_CONFIG_H -I.-DORX_VER=4 -DORX_REL=0 -DORX_MOD=0
-DORX_FIX=0 -DORX_SYS_STR=\"LINUX\" -DORX_CATDIR=\"/usr/bin\"
-DORX_SHARED_LIBRARY_EXT=\".so\" -I./lib -I./api -I./
12 matches
Mail list logo
