Hi Magnus,
This is it:
...
[14] VERSIONINFO_RESOURCE :=
/cygdrive/c/cygwin64/home/ssadetsk/projects/jdk8/jdk8u-dev/jdk/src/windows/resource/version.rc
[15] RC_FLAGS := -nologo -l 0x409 -r -d
JDK_BUILD_ID=1.8.0-internal-fastdebug-ssadetskrussadetsk_2015_04_29_10_24-b00
-d JDK_COMPANY=Oracle
On 2015-04-29 09:50, Semyon Sadetsky wrote:
Hello,
Please advise what is the source of the next issue:
(...libfdlibm/e_acos.obj file is really absent)
Hi Semyon,
Please re-run with make LOG=debug JOBS=1 to get a better log prior to
the failure.
/Magnus
## Starting jdk
Importing CORBA
I've found that disable ccache fixes problems building e_acos ( the
first native file in the jdk portion of the build).
On 4/29/15 4:23 AM, Magnus Ihse Bursie wrote:
On 2015-04-29 09:50, Semyon Sadetsky wrote:
Hello,
Please advise what is the source of the next issue:
Hello Semyon,
To disable ccache explicitly, you need to run add --disable-ccache to
the configure command line. I thought we had fixed this, but perhaps we
still pick up ccache automatically in 8u even if it's not supported.
Anyway, ccache is certainly not compatible with Visual Studio.
Hello Sergey,
No, that wasn't known. I wasn't aware that Cygwin had bumped its version
to 2.0. Thanks for pointing that out.
Filed: https://bugs.openjdk.java.net/browse/JDK-8079087
/Erik
On 2015-04-29 10:46, Sergey Bylokhov wrote:
Hello.
Is that known issue that current version of cygwin
Hello.
Is that known issue that current version of cygwin 2.0 [1] is unsupported?
configure: Your cygwin is too old. You are running 2.0.0(0.287/5/3), but
at least cygwin 1.7 is required. Please upgrade.
configure: error: Cannot continue
[1]
On 30/04/2015 3:26 PM, David Holmes wrote:
Hi Nevill,
Sorry Ed!
David
Just realized this was sent to hotspot-dev (attempting bcc) but is not a
hotspot issue. With your new approach this is a build issue so cc'ing
build-dev.
The new approach seems better to me but build folk need to confirm
Hi Nevill,
Just realized this was sent to hotspot-dev (attempting bcc) but is not a
hotspot issue. With your new approach this is a build issue so cc'ing
build-dev.
The new approach seems better to me but build folk need to confirm the
placement.
Thanks,
David
On 29/04/2015 8:52 PM,
