Currently the only other option for manually configuring the build platform
while cross compiling are devkits, which don't work on certain systems and are
also more focused on differentiating the build and target compilers instead.
This patch adds the ability to explicitly set the build platform
On Wed, 2 Mar 2022 08:11:51 GMT, TheShermanTanker wrote:
>This also removes support for the legacy cross compilation flags as well.
Hi,
without reading through building.md and your patch, which legacy flags are
would be removed by this?
Thanks, Thomas
Oh, and please describe whatever you do
On Wed, 2 Mar 2022 08:27:19 GMT, Thomas Stuefe wrote:
> > This also removes support for the legacy cross compilation flags as well.
>
> Hi,
>
> without reading through building.md and your patch, which legacy flags are
> would be removed by this?
>
> Thanks, Thomas
Specifically the flags tha
On Wed, 2 Mar 2022 08:33:58 GMT, TheShermanTanker wrote:
> > > This also removes support for the legacy cross compilation flags as well.
> >
> >
> > Hi,
> > without reading through building.md and your patch, which legacy flags are
> > would be removed by this?
> > Thanks, Thomas
>
> Specific
On Tue, 1 Mar 2022 20:18:11 GMT, Man Cao wrote:
> Hi all,
>
> Could anyone help review the addition of LICENSE file to hsdis directory?
>
> -Man
I'm not sure what the legal implications are of adding a separate general file
like this, instead of marking each individual file. I'd need to get s
On Wed, 2 Mar 2022 08:11:51 GMT, TheShermanTanker wrote:
> Currently the only other option for manually configuring the build platform
> while cross compiling are devkits, which don't work on certain systems and
> are also more focused on differentiating the build and target compilers
> instea
On Wed, 2 Mar 2022 08:11:51 GMT, TheShermanTanker wrote:
> Currently the only other option for manually configuring the build platform
> while cross compiling are devkits, which don't work on certain systems and
> are also more focused on differentiating the build and target compilers
> instea
Apologies for not creating a thread consulting the mailing list before
submitting the PR, I'm still getting used to the process (And also thought
this would create unnecessary noise for people within this list).
I initially believed that given how the legacy options had warnings when
they were set
Hi Jules,
On Wed, Mar 2, 2022 at 1:29 PM Jules W. wrote:
> Apologies for not creating a thread consulting the mailing list before
> submitting the PR, I'm still getting used to the process (And also thought
> this would create unnecessary noise for people within this list).
>
On the contrary, t
Hi Thomas,
I was referring to Magnus' issue with the markdown docs I edited when I
submitted the PR.
Thank you for the encouragement, it means a lot to me :)
best regards,
Julian
On Wed, Mar 2, 2022 at 8:42 PM Thomas Stüfe wrote:
> Hi Jules,
>
> On Wed, Mar 2, 2022 at 1:29 PM Jules W. wrote:
Hi Julian,
Thanks for bringing this back in a discussion format. If I understand
your problem correctly, it is that the --openjdk-target fully replaces
the autoconf --build/--host/--target triplet, and assumes that it can
autodetect the build platform. And if that autodetect fails, the only
r
> This PR adds a new configure argument, `--enable-hsdis-bundling`. Setting
> this, together with a valid backend using `--with-hsdis`, will bundle the
> generated hsdis library with the JDK.
>
> The PR also includes a refactoring of the hsdis handling in autoconf,
> breaking it out to a separa
On Wed, 2 Mar 2022 13:12:52 GMT, Magnus Ihse Bursie wrote:
>> This PR adds a new configure argument, `--enable-hsdis-bundling`. Setting
>> this, together with a valid backend using `--with-hsdis`, will bundle the
>> generated hsdis library with the JDK.
>>
>> The PR also includes a refactoring
On Wed, 2 Mar 2022 16:52:12 GMT, Magnus Ihse Bursie wrote:
> When doing reproducible builds, controlling the build time is imperative. To
> make this as easy as possible, some changes are needed in the build system.
>
> * If source-date is set to anything other than "updated" (meaning that it
When doing reproducible builds, controlling the build time is imperative. To
make this as easy as possible, some changes are needed in the build system.
* If source-date is set to anything other than "updated" (meaning that it
should be determined at build time), then the default value of
--wi
On Wed, 2 Mar 2022 16:52:12 GMT, Magnus Ihse Bursie wrote:
> When doing reproducible builds, controlling the build time is imperative. To
> make this as easy as possible, some changes are needed in the build system.
>
> * If source-date is set to anything other than "updated" (meaning that it
On Wed, 2 Mar 2022 14:30:43 GMT, Magnus Ihse Bursie wrote:
>> This PR adds a new configure argument, `--enable-hsdis-bundling`. Setting
>> this, together with a valid backend using `--with-hsdis`, will bundle the
>> generated hsdis library with the JDK.
>>
>> The PR also includes a refactoring
On Wed, 2 Mar 2022 16:54:21 GMT, Magnus Ihse Bursie wrote:
> To clarify, the end effect of these changes is that building OpenJDK will
> basically be compliant with the method of just setting SOURCE_DATE_EPOCH.
> (The caveat is that it must be set at configure time, not build time.) So
>
> ```
On Tue, 22 Feb 2022 16:10:22 GMT, Magnus Ihse Bursie wrote:
> This PR adds a new configure argument, `--enable-hsdis-bundling`. Setting
> this, together with a valid backend using `--with-hsdis`, will bundle the
> generated hsdis library with the JDK.
>
> The PR also includes a refactoring of
On Wed, 2 Mar 2022 16:52:12 GMT, Magnus Ihse Bursie wrote:
> When doing reproducible builds, controlling the build time is imperative. To
> make this as easy as possible, some changes are needed in the build system.
>
> * If source-date is set to anything other than "updated" (meaning that it
On Tue, 1 Mar 2022 20:18:11 GMT, Man Cao wrote:
> Hi all,
>
> Could anyone help review the addition of LICENSE file to hsdis directory?
>
> -Man
Thank you for reaching out for confirmation. This doc might help:
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-fea
The caller class returned by Reflection::getCallerClass was used to gain access
to it's module in most cases and class loader in one case. I added a method to
translate the caller class to caller module so that the decision of what module
represents the caller with no stack frame is made in a si
On Wed, 2 Mar 2022 18:56:40 GMT, Tim Prinzing wrote:
> The caller class returned by Reflection::getCallerClass was used to gain
> access to it's module in most cases and class loader in one case. I added a
> method to translate the caller class to caller module so that the decision of
> what m
On Wed, 2 Mar 2022 18:56:40 GMT, Tim Prinzing wrote:
> The caller class returned by Reflection::getCallerClass was used to gain
> access to it's module in most cases and class loader in one case. I added a
> method to translate the caller class to caller module so that the decision of
> what m
> The caller class returned by Reflection::getCallerClass was used to gain
> access to it's module in most cases and class loader in one case. I added a
> method to translate the caller class to caller module so that the decision of
> what module represents the caller with no stack frame is made
> The caller class returned by Reflection::getCallerClass was used to gain
> access to it's module in most cases and class loader in one case. I added a
> method to translate the caller class to caller module so that the decision of
> what module represents the caller with no stack frame is made
On Wed, 2 Mar 2022 21:53:01 GMT, Tim Prinzing wrote:
>> The caller class returned by Reflection::getCallerClass was used to gain
>> access to it's module in most cases and class loader in one case. I added a
>> method to translate the caller class to caller module so that the decision
>> of wh
> Currently the only other option for manually configuring the build platform
> while cross compiling are devkits, which don't work on certain systems and
> are also more focused on differentiating the build and target compilers
> instead. This patch adds the ability to explicitly set the build
> Currently the only other option for manually configuring the build platform
> while cross compiling are devkits, which don't work on certain systems and
> are also more focused on differentiating the build and target compilers
> instead. This patch adds the ability to explicitly set the build
29 matches
Mail list logo
