Re: programming guide current state

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: programming guide current state

rvjansen

On 18 apr. 2014, at 22:32, Tom Maynard <[hidden email]> wrote:


  1. In 27.6, setting up the And config was (probably) exactly as you describe it. Any variances were insignificant, but: The build itself failed. It was going just fine at the start, but then:
[buildnrc] Compilation of 'Rexx.nrx' failed [9 classes, one error]
 [buildnrc] Compilation of 'RexxComparator.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxIO.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxNode.nrx' successful
 [buildnrc] Compilation of 'RexxOperators.nrx' successful
 [buildnrc] Compilation of 'RexxParse.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxSet.nrx' failed [4 errors]
 [buildnrc] Compilation of 'RexxTrace.nrx' failed [2 errors]
 [buildnrc] Compilation of 'RexxUtil.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxWords.nrx' successful

BUILD FAILED
C:\Users\Tom\NetRexx\workspace\NetRexx303\build.xml:150: Compile failed, messages should have been provided.

Total time: 2 seconds

Since at least for now, building NetRexx is not my main goal, I’m simply reporting this as a deviation from the doc. I built it against (or with?) the current production release, just so you know.

You might wonder if I saw this because I never replied. Yes, I saw it and because of it we are in a bit of a bind. There is a problem with building on Java 8 on Windows- which is fixed if I use a Java-8 generated NetRexxC.jar from another platform ; this implies that we generate class format which is usable from Java 8 upwards, and we try to deliver a NetRexx compiler that still runs on 1.6. Otherwise we need to bump the version requirement to Java 8, which is also fine by me, but probably not all of our customers.

Previous releases were built using a Java 6 that is still on my MacBook using a script that changes paths to find Java. This does not work anymore because the ant we now use cannot load the class formats if executed under Java 6. I wanted to change to a build process that uses the current compiler and makes use of the flags to generate a downward compatible class format, but alas. I don't know how to do that (yet) with ant - with make that would be a breeze of course. All in all, however hard I try, I am not a happy ant user at the moment for at least these two reasons.

This needs fixing before we can release 3.03, and this is the reason I still did not deliver the package for that. So please stand by, and possibly suggest how I might compile a downward compatible class format with javac, the new ecj and ant. We have a new goal of releasing during the symposium in Memphis.

Maybe someone with time on their hand can look into: (1) installing a downlevel ant and see if that works for Java 6. (2) finding out where to put the compiler flags for javac or ecj. Fixing the UTF8 problem that Windows has at the moment would be a definite bonus.

best regards,

René Jansen.

_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/

Reply | Threaded
Open this post in threaded view
|

Re: programming guide current state

Kermit Kiser
I have not encountered any problems with the Ant build but I confess that I am still using the 1.8.2 release of Ant. I will upgrade to Ant 1.9.3 and check it for problems. As for the cross compile issue, I think the only way around that is to separate the NetRexx compiles from the Java compiles because NetRexx cannot pass -target and -source values currently. I plan to fix that soon when I add JSR199 compiler interface support.  I suspect that make would probably have the same issue as Ant since it is a limitation of the way NetRexxC calls javac.

-- Kermit

On 4/28/2014 2:05 PM, René Jansen wrote:

On 18 apr. 2014, at 22:32, Tom Maynard <[hidden email]> wrote:


  1. In 27.6, setting up the And config was (probably) exactly as you describe it. Any variances were insignificant, but: The build itself failed. It was going just fine at the start, but then:
[buildnrc] Compilation of 'Rexx.nrx' failed [9 classes, one error]
 [buildnrc] Compilation of 'RexxComparator.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxIO.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxNode.nrx' successful
 [buildnrc] Compilation of 'RexxOperators.nrx' successful
 [buildnrc] Compilation of 'RexxParse.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxSet.nrx' failed [4 errors]
 [buildnrc] Compilation of 'RexxTrace.nrx' failed [2 errors]
 [buildnrc] Compilation of 'RexxUtil.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxWords.nrx' successful

BUILD FAILED
C:\Users\Tom\NetRexx\workspace\NetRexx303\build.xml:150: Compile failed, messages should have been provided.

Total time: 2 seconds

Since at least for now, building NetRexx is not my main goal, I’m simply reporting this as a deviation from the doc. I built it against (or with?) the current production release, just so you know.

You might wonder if I saw this because I never replied. Yes, I saw it and because of it we are in a bit of a bind. There is a problem with building on Java 8 on Windows- which is fixed if I use a Java-8 generated NetRexxC.jar from another platform ; this implies that we generate class format which is usable from Java 8 upwards, and we try to deliver a NetRexx compiler that still runs on 1.6. Otherwise we need to bump the version requirement to Java 8, which is also fine by me, but probably not all of our customers.

Previous releases were built using a Java 6 that is still on my MacBook using a script that changes paths to find Java. This does not work anymore because the ant we now use cannot load the class formats if executed under Java 6. I wanted to change to a build process that uses the current compiler and makes use of the flags to generate a downward compatible class format, but alas. I don't know how to do that (yet) with ant - with make that would be a breeze of course. All in all, however hard I try, I am not a happy ant user at the moment for at least these two reasons.

This needs fixing before we can release 3.03, and this is the reason I still did not deliver the package for that. So please stand by, and possibly suggest how I might compile a downward compatible class format with javac, the new ecj and ant. We have a new goal of releasing during the symposium in Memphis.

Maybe someone with time on their hand can look into: (1) installing a downlevel ant and see if that works for Java 6. (2) finding out where to put the compiler flags for javac or ecj. Fixing the UTF8 problem that Windows has at the moment would be a definite bonus.

best regards,

René Jansen.


_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/



_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/

Reply | Threaded
Open this post in threaded view
|

Re: programming guide current state

rvjansen
Hi Kermit,

yes, I will probably go for the separate compilation. It would be great if you could get the flags in at the next drop. Have also to look at the netrexx_java environment variable.

René.

On 29 apr. 2014, at 01:09, Kermit Kiser <[hidden email]> wrote:

I have not encountered any problems with the Ant build but I confess that I am still using the 1.8.2 release of Ant. I will upgrade to Ant 1.9.3 and check it for problems. As for the cross compile issue, I think the only way around that is to separate the NetRexx compiles from the Java compiles because NetRexx cannot pass -target and -source values currently. I plan to fix that soon when I add JSR199 compiler interface support.  I suspect that make would probably have the same issue as Ant since it is a limitation of the way NetRexxC calls javac.

-- Kermit

On 4/28/2014 2:05 PM, René Jansen wrote:

On 18 apr. 2014, at 22:32, Tom Maynard <[hidden email]> wrote:


  1. In 27.6, setting up the And config was (probably) exactly as you describe it. Any variances were insignificant, but: The build itself failed. It was going just fine at the start, but then:
[buildnrc] Compilation of 'Rexx.nrx' failed [9 classes, one error]
 [buildnrc] Compilation of 'RexxComparator.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxIO.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxNode.nrx' successful
 [buildnrc] Compilation of 'RexxOperators.nrx' successful
 [buildnrc] Compilation of 'RexxParse.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxSet.nrx' failed [4 errors]
 [buildnrc] Compilation of 'RexxTrace.nrx' failed [2 errors]
 [buildnrc] Compilation of 'RexxUtil.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxWords.nrx' successful

BUILD FAILED
C:\Users\Tom\NetRexx\workspace\NetRexx303\build.xml:150: Compile failed, messages should have been provided.

Total time: 2 seconds

Since at least for now, building NetRexx is not my main goal, I’m simply reporting this as a deviation from the doc. I built it against (or with?) the current production release, just so you know.

You might wonder if I saw this because I never replied. Yes, I saw it and because of it we are in a bit of a bind. There is a problem with building on Java 8 on Windows- which is fixed if I use a Java-8 generated NetRexxC.jar from another platform ; this implies that we generate class format which is usable from Java 8 upwards, and we try to deliver a NetRexx compiler that still runs on 1.6. Otherwise we need to bump the version requirement to Java 8, which is also fine by me, but probably not all of our customers.

Previous releases were built using a Java 6 that is still on my MacBook using a script that changes paths to find Java. This does not work anymore because the ant we now use cannot load the class formats if executed under Java 6. I wanted to change to a build process that uses the current compiler and makes use of the flags to generate a downward compatible class format, but alas. I don't know how to do that (yet) with ant - with make that would be a breeze of course. All in all, however hard I try, I am not a happy ant user at the moment for at least these two reasons.

This needs fixing before we can release 3.03, and this is the reason I still did not deliver the package for that. So please stand by, and possibly suggest how I might compile a downward compatible class format with javac, the new ecj and ant. We have a new goal of releasing during the symposium in Memphis.

Maybe someone with time on their hand can look into: (1) installing a downlevel ant and see if that works for Java 6. (2) finding out where to put the compiler flags for javac or ecj. Fixing the UTF8 problem that Windows has at the moment would be a definite bonus.

best regards,

René Jansen.


_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/


_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/



_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/

Reply | Threaded
Open this post in threaded view
|

Re: programming guide current state

Kermit Kiser
@ René -

I can see that you are quite busy with the symposium at the moment - I am sitting it out as there does not seem to be anything NetRexx related. I am only sending this update now in case it is of any use to you in your planning sessions at the symposium.

There are still some build problems with the NetRexx trunk. If there is no objection, I will update trunk to a package-able state. I have tested the build on Windows 7 with Ant 1.8.2, Ant 1.9.3, Java 6, Java 7, Java 8 and ECJ with no problems. The Ant or Java versions do not affect the builds. However the repository copy of the bootstrap compiler NetRexxC.jar has somehow been replaced with a version compiled under Java 7 and that will not work on Java 6 systems. Also the issue #102 patch on RxVarpool that breaks some compiles (like DiagUTF8) on Windows systems has not been removed in the repository trunk. Those things must be changed to make trunk work correctly!

Otherwise things look good except for possibly missing the changes in some documents. But I may be looking at the wrong versions somehow.

-- Kermit


On 4/28/2014 4:51 PM, René Jansen wrote:
Hi Kermit,

yes, I will probably go for the separate compilation. It would be great if you could get the flags in at the next drop. Have also to look at the netrexx_java environment variable.

René.

On 29 apr. 2014, at 01:09, Kermit Kiser <[hidden email]> wrote:

I have not encountered any problems with the Ant build but I confess that I am still using the 1.8.2 release of Ant. I will upgrade to Ant 1.9.3 and check it for problems. As for the cross compile issue, I think the only way around that is to separate the NetRexx compiles from the Java compiles because NetRexx cannot pass -target and -source values currently. I plan to fix that soon when I add JSR199 compiler interface support.  I suspect that make would probably have the same issue as Ant since it is a limitation of the way NetRexxC calls javac.

-- Kermit

On 4/28/2014 2:05 PM, René Jansen wrote:

On 18 apr. 2014, at 22:32, Tom Maynard <[hidden email]> wrote:


  1. In 27.6, setting up the And config was (probably) exactly as you describe it. Any variances were insignificant, but: The build itself failed. It was going just fine at the start, but then:
[buildnrc] Compilation of 'Rexx.nrx' failed [9 classes, one error]
 [buildnrc] Compilation of 'RexxComparator.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxIO.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxNode.nrx' successful
 [buildnrc] Compilation of 'RexxOperators.nrx' successful
 [buildnrc] Compilation of 'RexxParse.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxSet.nrx' failed [4 errors]
 [buildnrc] Compilation of 'RexxTrace.nrx' failed [2 errors]
 [buildnrc] Compilation of 'RexxUtil.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxWords.nrx' successful

BUILD FAILED
C:\Users\Tom\NetRexx\workspace\NetRexx303\build.xml:150: Compile failed, messages should have been provided.

Total time: 2 seconds

Since at least for now, building NetRexx is not my main goal, I’m simply reporting this as a deviation from the doc. I built it against (or with?) the current production release, just so you know.

You might wonder if I saw this because I never replied. Yes, I saw it and because of it we are in a bit of a bind. There is a problem with building on Java 8 on Windows- which is fixed if I use a Java-8 generated NetRexxC.jar from another platform ; this implies that we generate class format which is usable from Java 8 upwards, and we try to deliver a NetRexx compiler that still runs on 1.6. Otherwise we need to bump the version requirement to Java 8, which is also fine by me, but probably not all of our customers.

Previous releases were built using a Java 6 that is still on my MacBook using a script that changes paths to find Java. This does not work anymore because the ant we now use cannot load the class formats if executed under Java 6. I wanted to change to a build process that uses the current compiler and makes use of the flags to generate a downward compatible class format, but alas. I don't know how to do that (yet) with ant - with make that would be a breeze of course. All in all, however hard I try, I am not a happy ant user at the moment for at least these two reasons.

This needs fixing before we can release 3.03, and this is the reason I still did not deliver the package for that. So please stand by, and possibly suggest how I might compile a downward compatible class format with javac, the new ecj and ant. We have a new goal of releasing during the symposium in Memphis.

Maybe someone with time on their hand can look into: (1) installing a downlevel ant and see if that works for Java 6. (2) finding out where to put the compiler flags for javac or ecj. Fixing the UTF8 problem that Windows has at the moment would be a definite bonus.

best regards,

René Jansen.


_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/


_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/




_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/



_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/

Reply | Threaded
Open this post in threaded view
|

Re: programming guide current state

rvjansen
Kermit,

excellent, go ahead. When I can find the time, I will try to release it - but not after checking with you.

best regards,

René.

On 6 mei 2014, at 04:10, Kermit Kiser <[hidden email]> wrote:

@ René -

I can see that you are quite busy with the symposium at the moment - I am sitting it out as there does not seem to be anything NetRexx related. I am only sending this update now in case it is of any use to you in your planning sessions at the symposium.

There are still some build problems with the NetRexx trunk. If there is no objection, I will update trunk to a package-able state. I have tested the build on Windows 7 with Ant 1.8.2, Ant 1.9.3, Java 6, Java 7, Java 8 and ECJ with no problems. The Ant or Java versions do not affect the builds. However the repository copy of the bootstrap compiler NetRexxC.jar has somehow been replaced with a version compiled under Java 7 and that will not work on Java 6 systems. Also the issue #102 patch on RxVarpool that breaks some compiles (like DiagUTF8) on Windows systems has not been removed in the repository trunk. Those things must be changed to make trunk work correctly!

Otherwise things look good except for possibly missing the changes in some documents. But I may be looking at the wrong versions somehow.

-- Kermit


On 4/28/2014 4:51 PM, René Jansen wrote:
Hi Kermit,

yes, I will probably go for the separate compilation. It would be great if you could get the flags in at the next drop. Have also to look at the netrexx_java environment variable.

René.

On 29 apr. 2014, at 01:09, Kermit Kiser <[hidden email]> wrote:

I have not encountered any problems with the Ant build but I confess that I am still using the 1.8.2 release of Ant. I will upgrade to Ant 1.9.3 and check it for problems. As for the cross compile issue, I think the only way around that is to separate the NetRexx compiles from the Java compiles because NetRexx cannot pass -target and -source values currently. I plan to fix that soon when I add JSR199 compiler interface support.  I suspect that make would probably have the same issue as Ant since it is a limitation of the way NetRexxC calls javac.

-- Kermit

On 4/28/2014 2:05 PM, René Jansen wrote:

On 18 apr. 2014, at 22:32, Tom Maynard <[hidden email]> wrote:


  1. In 27.6, setting up the And config was (probably) exactly as you describe it. Any variances were insignificant, but: The build itself failed. It was going just fine at the start, but then:
[buildnrc] Compilation of 'Rexx.nrx' failed [9 classes, one error]
 [buildnrc] Compilation of 'RexxComparator.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxIO.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxNode.nrx' successful
 [buildnrc] Compilation of 'RexxOperators.nrx' successful
 [buildnrc] Compilation of 'RexxParse.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxSet.nrx' failed [4 errors]
 [buildnrc] Compilation of 'RexxTrace.nrx' failed [2 errors]
 [buildnrc] Compilation of 'RexxUtil.nrx' failed [one error]
 [buildnrc] Compilation of 'RexxWords.nrx' successful

BUILD FAILED
C:\Users\Tom\NetRexx\workspace\NetRexx303\build.xml:150: Compile failed, messages should have been provided.

Total time: 2 seconds

Since at least for now, building NetRexx is not my main goal, I’m simply reporting this as a deviation from the doc. I built it against (or with?) the current production release, just so you know.

You might wonder if I saw this because I never replied. Yes, I saw it and because of it we are in a bit of a bind. There is a problem with building on Java 8 on Windows- which is fixed if I use a Java-8 generated NetRexxC.jar from another platform ; this implies that we generate class format which is usable from Java 8 upwards, and we try to deliver a NetRexx compiler that still runs on 1.6. Otherwise we need to bump the version requirement to Java 8, which is also fine by me, but probably not all of our customers.

Previous releases were built using a Java 6 that is still on my MacBook using a script that changes paths to find Java. This does not work anymore because the ant we now use cannot load the class formats if executed under Java 6. I wanted to change to a build process that uses the current compiler and makes use of the flags to generate a downward compatible class format, but alas. I don't know how to do that (yet) with ant - with make that would be a breeze of course. All in all, however hard I try, I am not a happy ant user at the moment for at least these two reasons.

This needs fixing before we can release 3.03, and this is the reason I still did not deliver the package for that. So please stand by, and possibly suggest how I might compile a downward compatible class format with javac, the new ecj and ant. We have a new goal of releasing during the symposium in Memphis.

Maybe someone with time on their hand can look into: (1) installing a downlevel ant and see if that works for Java 6. (2) finding out where to put the compiler flags for javac or ecj. Fixing the UTF8 problem that Windows has at the moment would be a definite bonus.

best regards,

René Jansen.


_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/


_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/




_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/


_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/



_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/