Kelly O'Hair kirjoitti:
> Wait a minute, where did you get libdeploy.so?
>
> It's not part of the OpenJDK, at least not yet, and not that I'm aware of.
>
> -kto
>
>
Nope. It's from the proprietary binary builds but this mailing list
seemed the best place to ask about it as there could be a val
Wait a minute, where did you get libdeploy.so?
It's not part of the OpenJDK, at least not yet, and not that I'm aware of.
-kto
Petteri Räty wrote:
Kelly O'Hair kirjoitti:
I am not seeing this dependency on our jdk7 build images from older
Linux releases.
I suspect that the Makefile logic th
Kelly O'Hair kirjoitti:
>
> I am not seeing this dependency on our jdk7 build images from older
> Linux releases.
>
> I suspect that the Makefile logic that triggers static links might be
> broken for some Linux systems, or more likely for gcc 4. But I'd need
> more information about the system.
I am not seeing this dependency on our jdk7 build images from older Linux
releases.
I suspect that the Makefile logic that triggers static links might be
broken for some Linux systems, or more likely for gcc 4. But I'd need
more information about the system.
What version of Linux and gcc was u
Petteri Räty kirjoitti:
> All other parts of the JDK link libstdc++ statically so it's weird that
> libdeploy (from that I understand java web start and plugin related
> stuff and as such still closed source) links it dynamically. This means
> that our packages need to depend on the the old version
All other parts of the JDK link libstdc++ statically so it's weird that
libdeploy (from that I understand java web start and plugin related
stuff and as such still closed source) links it dynamically. This means
that our packages need to depend on the the old version of libstdc++.
[EMAIL PROTECTED
