OpenJDK 7u and Fedora 17

[Andrew Hughes]

----- Original Message -----
> On 8/29/12 1:56 PM, Henri Gomez wrote:
> > Shouldn't it be general case for OpenJDK on Linux to use dynamic
> > linking with stdc++ like all others libs ?
> 
> For 7 updates? Probably not.
> 
> See http://markmail.org/message/yqexkr4ty7s4gelz for details. As
> Kelly
> said then "It is quite possible that we don't need to static link
> anything
> anymore, but that would need to be verified."
> 
> Not worth the bother from my POV, as it's
> 
> a) not a bug - it's the intended behavior,
> b) those who desire not to statically link with libsdtc++ can do so
> easily,
> c) it would have to be done and verified on 8 first, and
> d) 8 is getting a new build system anyway
> 
> So, in short, there is not much of a point in changing it here now.
> 

The OpenJDK packages in most distributions have been turning off static
linking for years.  What more verification is needed?

To respond to your points,

a) I presume you mean Oracle's intended behaviour.  Most developers on GNU/Linux would
not expect static linking to be taking place, as it's not the norm.
b) This assumes they are a) aware it is happening in the first place and b)
know how to turn it off.  Neither are that obvious, IMHO.  I believe we
turned it off initially but then spotted it had regressed again, because
Fedora moved the static library into its own package.  It's easier
for Oracle to turn ON static linking for their packages, than it is to
for users new to OpenJDK to know to install a non-standard package.
c) This I agree with.  I hadn't realised it was being discussed on 7u and
not build-dev (now CCed).
d) I believe the new build system is copying verbatim from the old one
at present, and comparing resulting images, so I don't see it changing
as a result of that.

I think the general issue here is we need to consider whether the build defaults
should remain suited to producing proprietary binaries for Oracle, as they have previously,
or whether they should instead fit the expected "norm" on the appropriate platform (i.e. how
the majority of other packages do it).  One of the hurdles in attracting
new developers to OpenJDK is the ease of initial builds.   I think a good aim
would be to have it buildable by a simple "configure; make" on a standard install,
without having to install a mass of non-standard packages or set lots of options.

> cheers,
> dalibor topic
> --
> Oracle <http://www.oracle.com>
> Dalibor Topic | Principal Product Manager
> Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
> <tel:+491737185961>
> Oracle Java Platform Group
> 
> ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg
> 
> ORACLE Deutschland B.V. & Co. KG
> Hauptverwaltung: Riesstr. 25, D-80992 München
> Registergericht: Amtsgericht München, HRA 95603
> Geschäftsführer: Jürgen Kunz
> 
> Komplementärin: ORACLE Deutschland Verwaltung B.V.
> Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
> Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
> Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher
> 
> Green Oracle <http://www.oracle.com/commitment> Oracle is committed
> to developing practices and products that help protect the
> environment
> 

-- 
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07