-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: None
-
Component/s: core-libs
-
b19
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8310114 | 17.0.9 | Matthias Baesken | P4 | Resolved | Fixed | b01 |
When statically link a set of JDK native libraries and libjvm with the launcher executable (see JDK-8303796 for more details), the linker reports failure due to multiple definitions of 'handleSocketError', e.g.:
.../libsctp.a(SctpNet.o): in function `handleSocketError':
.../SctpNet.c:124: multiple definition of `handleSocketError'; .../libnio.a(Net.o):.../Net.c:918: first defined here
collect2: error: ld returned 1 exit status
.../libsctp.a(SctpNet.o): in function `handleSocketError':
.../SctpNet.c:124: multiple definition of `handleSocketError'; .../libnio.a(Net.o):.../Net.c:918: first defined here
collect2: error: ld returned 1 exit status
- backported by
-
JDK-8310114 Resolve multiple definition of 'handleSocketError' when statically linking with JDK native libraries
-
- Resolved
-
- relates to
-
JDK-8303796 Optionally build fully statically linked JDK image
-
- Open
-
- links to
-
Commit
openjdk/jdk17u-dev/faafe226
-
Commit
openjdk/jdk/2bbbff20
-
Review
openjdk/jdk17u-dev/1437
-
Review
openjdk/jdk/13433
-
Review
openjdk/jdk/13438
(2 links to)