> 16 feb. 2019 kl. 07:47 skrev Franco Gastón Pellegrini
> :
>
> Yes, removing --debug-mode enables a 32 bits compilation, with warnings.
> Thanks!
Great!
Did the patch help for debug builds?
/Magnus
>
> El vie., 15 de feb. de 2019 a la(s) 08:05, Magnus Ihse Bursie
>
Yes, removing --debug-mode enables a 32 bits compilation, with warnings.
Thanks!
El vie., 15 de feb. de 2019 a la(s) 08:05, Magnus Ihse Bursie (
magnus.ihse.bur...@oracle.com) escribió:
>
>
> On 2019-02-12 15:42, Alexey Ivanov wrote:
> > On 12/02/2019 14:37, Magnus Ihse Bursie wrote:
> >> There
On 2019-02-12 15:42, Alexey Ivanov wrote:
On 12/02/2019 14:37, Magnus Ihse Bursie wrote:
There has been some fallout due to the mapfile/linking changes made
in JDK 12 that affected JNICALL. However, that should not be
affecting JDK 11.
Wasn't it done in JDK 11?
If my memory serves me
On 12/02/2019 14:37, Magnus Ihse Bursie wrote:
There has been some fallout due to the mapfile/linking changes made in
JDK 12 that affected JNICALL. However, that should not be affecting
JDK 11.
Wasn't it done in JDK 11?
If my memory serves me right, it was done in JDK 11.
--
Alexey
On 2019-02-12 14:38, Alexey Ivanov wrote:
On 12/02/2019 04:25, David Holmes wrote:
On 12/02/2019 1:45 pm, Franco Gastón Pellegrini wrote:
I just downloaded again (to be sure about my errors) JDK 12 and use
this command:
bash ./configure --enable-debug --disable-warnings-as-errors
On 12/02/2019 04:25, David Holmes wrote:
On 12/02/2019 1:45 pm, Franco Gastón Pellegrini wrote:
I just downloaded again (to be sure about my errors) JDK 12 and use
this command:
bash ./configure --enable-debug --disable-warnings-as-errors
--with-target-bits=32 --with-toolchain-version=2017
On 12/02/2019 1:45 pm, Franco Gastón Pellegrini wrote:
I just downloaded again (to be sure about my errors) JDK 12 and use this
command:
bash ./configure --enable-debug --disable-warnings-as-errors
--with-target-bits=32 --with-toolchain-version=2017
--with-jvm-variants=client
I just downloaded again (to be sure about my errors) JDK 12 and use this
command:
bash ./configure --enable-debug --disable-warnings-as-errors
--with-target-bits=32 --with-toolchain-version=2017
--with-jvm-variants=client --with-boot-jdk="/cygdrive/c/Program
Files/Java/jdk-11.0.2/";
and I get:
On 12/02/2019 8:28 am, Franco Gastón Pellegrini wrote:
My mistake to not fully describe it but I tried jdk 11 and 12 using the
disable warning as error on both, getting similar errors. (Both 32 bits)
The "operator delete" issue has already been encountered:
My mistake to not fully describe it but I tried jdk 11 and 12 using the
disable warning as error on both, getting similar errors. (Both 32 bits)
El lun., 11 de feb. de 2019 19:26, David Holmes
escribió:
> On 12/02/2019 12:03 am, Alexey Ivanov wrote:
> > Hi David,
> >
> > On 11/02/2019 11:33,
On 12/02/2019 12:03 am, Alexey Ivanov wrote:
Hi David,
On 11/02/2019 11:33, David Holmes wrote:
Hi Alexey,
On 11/02/2019 7:12 pm, Alexey Ivanov wrote:
Hi Franco,
On 11/02/2019 02:03, David Holmes wrote:
On 8/02/2019 5:07 am, Franco Gastón Pellegrini wrote:
I tried compiling JDK 12 for 32
Hi David,
On 11/02/2019 11:33, David Holmes wrote:
Hi Alexey,
On 11/02/2019 7:12 pm, Alexey Ivanov wrote:
Hi Franco,
On 11/02/2019 02:03, David Holmes wrote:
On 8/02/2019 5:07 am, Franco Gastón Pellegrini wrote:
I tried compiling JDK 12 for 32 bits, and I get similar errors:
=== Output
Hi Alexey,
On 11/02/2019 7:12 pm, Alexey Ivanov wrote:
Hi Franco,
On 11/02/2019 02:03, David Holmes wrote:
On 8/02/2019 5:07 am, Franco Gastón Pellegrini wrote:
I tried compiling JDK 12 for 32 bits, and I get similar errors:
=== Output from failing command(s) repeated here ===
* For target
Hi Franco,
On 11/02/2019 02:03, David Holmes wrote:
On 8/02/2019 5:07 am, Franco Gastón Pellegrini wrote:
I tried compiling JDK 12 for 32 bits, and I get similar errors:
=== Output from failing command(s) repeated here ===
* For target hotspot_variant-client_libjvm_objs_classFileParser.obj:
On 8/02/2019 5:07 am, Franco Gastón Pellegrini wrote:
I tried compiling JDK 12 for 32 bits, and I get similar errors:
=== Output from failing command(s) repeated here ===
* For target hotspot_variant-client_libjvm_objs_classFileParser.obj:
classFileParser.cpp
I tried compiling JDK 12 for 32 bits, and I get similar errors:
=== Output from failing command(s) repeated here ===
* For target hotspot_variant-client_libjvm_objs_classFileParser.obj:
classFileParser.cpp
c:/cygwin64/home/franc/java/jdk12/src/hotspot/share/classfile/classFileParser.cpp(312):
I just tried --disable-warnings-as-errors, and JDK 11 64bits as a bootjdk,
but I get a lots of errors, and it refuse to build, like this:
c:/cygwin64/home/franc/java/jdk11/src/hotspot/share/classfile/classFileParser.cpp(310):
warning C4267: '=': conversion from 'size_t' to 'u2', possible loss of
Thanks for the tip!
El mié., 6 de feb. de 2019 a la(s) 16:15, Erik Joelsson (
erik.joels...@oracle.com) escribió:
> If you are running into warnings treated as errors, please try
> configuring with --disable-warnings-as-errors. That is often needed on
> less tested platforms.
>
> Note that as
If you are running into warnings treated as errors, please try
configuring with --disable-warnings-as-errors. That is often needed on
less tested platforms.
Note that as long as you run the build on a 64 bit system, you can use a
64 bit bootjdk to build a 32 bit JDK.
/Erik
On 2019-02-06
Can this be fixed before JDK 12? I will not able to compile java 12 32bits
because I will not have java 11 32bits as a boot-jdk.
El sáb., 24 de nov. de 2018 a la(s) 03:59, David Holmes (
david.hol...@oracle.com) escribió:
> On 23/11/2018 7:10 pm, Magnus Ihse Bursie wrote:
> >
> > On 2018-11-23
On 23/11/2018 7:10 pm, Magnus Ihse Bursie wrote:
On 2018-11-23 08:35, Franco Gastón Pellegrini wrote:
Using the same command as before, and then using
make CONF=windows-x86-normal-client-fastdebug clean;
make CONF=windows-x86-normal-client-fastdebug;
I get warnings as error, and cannot
On 2018-11-23 08:35, Franco Gastón Pellegrini wrote:
Using the same command as before, and then using
make CONF=windows-x86-normal-client-fastdebug clean;
make CONF=windows-x86-normal-client-fastdebug;
I get warnings as error, and cannot compile. The output is (and I
attached the logs):
$
Using the same command as before, and then using
make CONF=windows-x86-normal-client-fastdebug clean;
make CONF=windows-x86-normal-client-fastdebug;
I get warnings as error, and cannot compile. The output is (and I attached
the logs):
$ make CONF=windows-x86-normal-client-fastdebug;
Building
yes, it was gcc, for some reason it get broken. I reinstall cygwin and
reconfigure it, an now it works, thanks!
El lun., 5 de nov. de 2018 a la(s) 07:00, Magnus Ihse Bursie (
magnus.ihse.bur...@oracle.com) escribió:
> On 2018-11-04 06:16, Franco Gastón Pellegrini wrote:
>
> I used this command:
On 2018-11-04 06:16, Franco Gastón Pellegrini wrote:
I used this command:
/bash ./configure --enable-debug --with-target-bits=32
--with-toolchain-version=2017 --with-jvm-variants=client
--with-boot-jdk="/home/Franco/Java/jdk10/build/windows-x86-normal-client-fastdebug/jdk/";/
I tried Visual
I used this command:
*bash ./configure --enable-debug --with-target-bits=32
--with-toolchain-version=2017 --with-jvm-variants=client
--with-boot-jdk="/home/Franco/Java/jdk10/build/windows-x86-normal-client-fastdebug/jdk/";*
I tried Visual studio 2015 and 2017 (with-toolchain-version).
I attached
Have you tried running
/cygdrive/c/progra~1/micros~1/2017/commun~1/vc/tools/msvc/1415~1.267/bin/hostx86/x86/cl
from the same prompt you ran configure to see what happens? It seems to
have located a compiler but fails to run it.
There is also a second log file, config.log, generated by
27 matches
Mail list logo
