Further more, I want to thank CCT Internationala 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!
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
<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.
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) 22.214.171.12440403-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.