Release 2.3.2 - Finally

Release 2.3.2  <https://jogamp.org/wiki/index.php/Release_2.3.2>

Tracking report <http://jogamp.org/wiki/index.php/SW_Tracking_Report_Objectives_for_the_release_2.3.2>

Maven packages are deployed on jogamp for 2.3.2,
Mark will update them on official maven repo soon.

Yes .. we were a bit late, but we had a few nasty bugs
to squish first. Thx to Xerxes and others who found quite a few issues
and who were 'holding my hand' and validated!
Thank you!

Have fun .. and lets see how we can 'break the game' for 2.4.0
  <http://jogamp.org/wiki/index.php/SW_Tracking_Report_Objectives_for_the_release_2.4.0>
which shall be a 'new feature' release focusing on Graph UI and more ..

Cheers, Sven

Further more, I want to thank CCT International a lot
for financial and technological support of Göthel Software e.K., supporting JogAmp!
Without CCT's unconditional and no questions asked support since May 2010,
this project would not be possible at all!
Thank you CCT!

I thank Sven and all contributors for their pugnacity. I thank CCT International too for its financial support.

Thanks for this release and their contributors.

I used the build 1462 for Sweet Home 3D 5.1 at the beginning of the week, but will upgrade to this more official release for next version.

Hi Sven,

On Fri, 2015-10-09 at 21:23 -0700, Sven Gothel [via jogamp] wrote:
> Release 2.3.2  <https://jogamp.org/wiki/index.php/Release_2.3.2>
>

Thanks for the new release. However, there seems to be a problem
building v2.3.2 on openSUSE that I did not see with v2.3.1, viz., when
linking using ld, I get the error:
ld unrecognized -a option `tic-libstdc++'

This happens probably due to the new linker-argument added to the make
file 'make/gluegen-cpptasks-base.xml':
<linkerarg value="-static-libstdc++" if="isGCC"/>

Compiling v2.3.2 after removing every occurrence of this line from the
'make/gluegen-cpptasks-base.xml' file leads to a successful build again.
Please let me know if this is because I am doing something wrong, or if
indeed patching out this line is the way to go.

Thanks.

--
Atri Bhattacharya
Sun 11 Oct 12:25:36 MST 2015

Sent from openSUSE 13.2 on my laptop.

There is something wrong on your side as the expected error message should be "ld unrecognized option `-static-libstdc++' ", it behaves like the linker argument had been broken into parts or misread on your machine :s

On my system, ld has the short-form options -s, -t and -a. The '-a' option takes a keyword immediately following it. From the man entry:
"-a KEYWORD                  Shared library control for HP/UX compatibility"
As a result, ld -static-libstdc++ is read as being equivalent to:
ld -s -t -a tic-libstdc++
so that "tic-libstdc++" is interpreted as the keyword, which is obviously undefined.
I think this is a very generic behaviour for ld, and not something particular to my system. Fwiw, I tested on a couple of other Linux systems too with similar results [same version of ld used: GNU ld (GNU Binutils; openSUSE 13.2) 2.24.0.20140403-6.1].
Anyway, my point is that ld does not have a -static-libstdc++ option in the first place, so this should be probably removed either way.

Thanks.