On Wed, 28 Feb 2024 19:29:13 GMT, Erik Joelsson wrote:
> There is no supported usecase that I can think of for injecting other
> versions of such libraries in a JDK distribution.
I can imagine it could be used to allow "hot patching" of the installed
JDK/JRE. Whether anyone has ever needed to
On Tue, 27 Feb 2024 13:55:53 GMT, Ludvig Janiuk wrote:
> Clarifying text in `make help` output on how to list variables for e.g.
> JTREG='...'.
> I have no idea what causes it.
Nevermind. The patch looks good.
-
Marked as reviewed by gli (Committer).
PR Review: https://git.openj
On Wed, 28 Feb 2024 12:26:54 GMT, Magnus Ihse Bursie wrote:
> We have seen a build failure along the lines of:
>
> /usr/bin/mv: cannot move
> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
> to
> '.../build/windows-x64-open-debug/hotspot/variant-server/l
On Wed, 28 Feb 2024 17:06:17 GMT, Magnus Ihse Bursie wrote:
>> We have seen a build failure along the lines of:
>>
>> /usr/bin/mv: cannot move
>> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
>> to
>> '.../build/windows-x64-open-debug/hotspot/variant-se
Executables and dynamic libraries on Linux can encode a search path that the
dynamic linker will use when looking up library dependencies, generally
referred to as an "rpath". In the JDK we use this with the $ORIGIN feature to
set search paths relative to the location of the binary itself. Typic
On Sat, 17 Feb 2024 08:28:56 GMT, Kim Barrett wrote:
> Please review this change that updates the minimum supported version of gcc
> to be used for building OpenJDK from 6.0 to 10.0.
>
> This permits enabling C++17 (JDK-8314488), though gcc 9.0 might suffice for
> that. A minimum of gcc 10 also
On Wed, 28 Feb 2024 17:06:17 GMT, Magnus Ihse Bursie wrote:
>> We have seen a build failure along the lines of:
>>
>> /usr/bin/mv: cannot move
>> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
>> to
>> '.../build/windows-x64-open-debug/hotspot/variant-se
On Wed, 28 Feb 2024 17:06:17 GMT, Magnus Ihse Bursie wrote:
>> We have seen a build failure along the lines of:
>>
>> /usr/bin/mv: cannot move
>> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
>> to
>> '.../build/windows-x64-open-debug/hotspot/variant-se
On Wed, 28 Feb 2024 15:54:38 GMT, Hannes Wallnöfer wrote:
>> Jonathan Gibbons has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Refactor most of TestMarkdown.java into separate tests, grouped by
>> functionality
>
> src/jdk.javadoc/share/
> We have seen a build failure along the lines of:
>
> /usr/bin/mv: cannot move
> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
> to
> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def':
> No such file or directory
>
> on W
On Fri, 23 Feb 2024 22:27:43 GMT, Jonathan Gibbons wrote:
>> Please review a patch to add support for Markdown syntax in documentation
>> comments, as described in the associated JEP.
>>
>> Notable features:
>>
>> * support for `///` documentation comments in `JavaTokenizer`
>> * new module `j
On Fri, 23 Feb 2024 22:27:43 GMT, Jonathan Gibbons wrote:
>> Please review a patch to add support for Markdown syntax in documentation
>> comments, as described in the associated JEP.
>>
>> Notable features:
>>
>> * support for `///` documentation comments in `JavaTokenizer`
>> * new module `j
> WIP
Julian Waters has updated the pull request incrementally with one additional
commit since the last revision:
Remove shared targets
-
Changes:
- all: https://git.openjdk.org/jdk/pull/18046/files
- new: https://git.openjdk.org/jdk/pull/18046/files/aefff3e8..0d29a355
Webr
WIP
-
Commit messages:
- 8326964
Changes: https://git.openjdk.org/jdk/pull/18046/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=18046&range=00
Issue: https://bugs.openjdk.org/browse/JDK-8326964
Stats: 3 lines in 1 file changed: 0 ins; 3 del; 0 mod
Patch: https://git.o
On Wed, 28 Feb 2024 14:53:13 GMT, Magnus Ihse Bursie wrote:
>> We have seen a build failure along the lines of:
>>
>> /usr/bin/mv: cannot move
>> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
>> to
>> '.../build/windows-x64-open-debug/hotspot/variant-se
On Wed, 28 Feb 2024 11:24:06 GMT, Magnus Ihse Bursie wrote:
> This is part of a general "spring cleaning" of the build system, addressing
> old code that has bit-rotted, been subject to lava flow, or just had bad or
> smelly code that we've never gotten around to fix.
>
> This particular patch
> We have seen a build failure along the lines of:
>
> /usr/bin/mv: cannot move
> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
> to
> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def':
> No such file or directory
>
> on W
On Fri, 23 Feb 2024 22:27:43 GMT, Jonathan Gibbons wrote:
>> Please review a patch to add support for Markdown syntax in documentation
>> comments, as described in the associated JEP.
>>
>> Notable features:
>>
>> * support for `///` documentation comments in `JavaTokenizer`
>> * new module `j
On Tue, 27 Feb 2024 13:55:53 GMT, Ludvig Janiuk wrote:
> Clarifying text in `make help` output on how to list variables for e.g.
> JTREG='...'.
It's interesting that the order of those two lines can change. I have no idea
what causes it.
-
PR Comment: https://git.openjdk.org/jdk/
On Wed, 28 Feb 2024 12:26:54 GMT, Magnus Ihse Bursie wrote:
> We have seen a build failure along the lines of:
>
> /usr/bin/mv: cannot move
> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
> to
> '.../build/windows-x64-open-debug/hotspot/variant-server/l
On Wed, 28 Feb 2024 13:12:14 GMT, Julian Waters wrote:
>> We have seen a build failure along the lines of:
>>
>> /usr/bin/mv: cannot move
>> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
>> to
>> '.../build/windows-x64-open-debug/hotspot/variant-server/
On Wed, 28 Feb 2024 12:26:54 GMT, Magnus Ihse Bursie wrote:
> We have seen a build failure along the lines of:
>
> /usr/bin/mv: cannot move
> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
> to
> '.../build/windows-x64-open-debug/hotspot/variant-server/l
On Wed, 28 Feb 2024 11:24:06 GMT, Magnus Ihse Bursie wrote:
> This is part of a general "spring cleaning" of the build system, addressing
> old code that has bit-rotted, been subject to lava flow, or just had bad or
> smelly code that we've never gotten around to fix.
>
> This particular patch
On Wed, 28 Feb 2024 12:26:54 GMT, Magnus Ihse Bursie wrote:
> We have seen a build failure along the lines of:
>
> /usr/bin/mv: cannot move
> '.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
> to
> '.../build/windows-x64-open-debug/hotspot/variant-server/l
We have seen a build failure along the lines of:
/usr/bin/mv: cannot move
'.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def.tmp'
to
'.../build/windows-x64-open-debug/hotspot/variant-server/libjvm/win-exports.def':
No such file or directory
on Windows.
My guess
On Tue, 27 Feb 2024 13:55:53 GMT, Ludvig Janiuk wrote:
> Clarifying text in `make help` output on how to list variables for e.g.
> JTREG='...'.
I use the command `make test-only JTREG=help` locally, the outputed message
seems an error (shown below). Does it work as expected?
Building target
On Wed, 28 Feb 2024 11:24:06 GMT, Magnus Ihse Bursie wrote:
> This is part of a general "spring cleaning" of the build system, addressing
> old code that has bit-rotted, been subject to lava flow, or just had bad or
> smelly code that we've never gotten around to fix.
>
> This particular patch
This is part of a general "spring cleaning" of the build system, addressing old
code that has bit-rotted, been subject to lava flow, or just had bad or smelly
code that we've never gotten around to fix.
This particular patch tries to make MakeBase truly minimal; only including the
core parts of
On Thu, 22 Feb 2024 16:28:20 GMT, Magnus Ihse Bursie wrote:
> Once [JDK-8017234](https://bugs.openjdk.org/browse/JDK-8017234) has been
> integrated, it is possible to do some cleanup. The goal of
> [JDK-8017234](https://bugs.openjdk.org/browse/JDK-8017234) was to not change
> any behavior, eve
On Sat, 17 Feb 2024 08:28:56 GMT, Kim Barrett wrote:
> Please review this change that updates the minimum supported version of gcc
> to be used for building OpenJDK from 6.0 to 10.0.
>
> This permits enabling C++17 (JDK-8314488), though gcc 9.0 might suffice for
> that. A minimum of gcc 10 also
On Tue, 27 Feb 2024 13:55:53 GMT, Ludvig Janiuk wrote:
> Clarifying text in `make help` output on how to list variables for e.g.
> JTREG='...'.
Thanks for the insight Erik!
-
PR Comment: https://git.openjdk.org/jdk/pull/18028#issuecomment-1968538692
On Mon, 26 Feb 2024 16:00:42 GMT, Andrew Leonard wrote:
> Adds Linux -fdebug-prefix-map'ing for SUPPORT_OUTPUTDIR and HOTSPOT_OUTPUTDIR
> when absolute paths are not allowed in the binaries, thus making the building
> of a JDK identically reproducible from different build directories.
This pul
On Sat, 17 Feb 2024 08:28:56 GMT, Kim Barrett wrote:
> Please review this change that updates the minimum supported version of gcc
> to be used for building OpenJDK from 6.0 to 10.0.
>
> This permits enabling C++17 (JDK-8314488), though gcc 9.0 might suffice for
> that. A minimum of gcc 10 also
33 matches
Mail list logo
