build 121 or later [1].*
[1]:
https://lists.apache.org/thread.html/5d4500fc2fcc7c0826fa7998512e9bf319d99037584011989ef5abe3@%3Cdev.geode.apache.org%3E
On Mon, Feb 12, 2018 at 2:51 PM, Daniel Farcovich <
daniel.farcov...@amdocs.com> wrote:
> I see sun.misc.ObjectInputFilter is available sin
I see sun.misc.ObjectInputFilter is available since java 9:
https://docs.oracle.com/javase/9/docs/api/java/io/ObjectInputFilter.html
Looks like this is a backward compatibility break :(
From: Daniel Farcovich
Sent: Monday, February 12, 2018 4:19 PM
To: dev@geode.apache.org
Cc: Gregory Vortman
Hi
We are facing a compilation error on
geode-core/src/main/java/org/apache/geode/internal/ObjectInputStreamFilterWrapper.java
sun.misc.ObjectInputFilter can't be found since we use java 8.
Has anyone encountered this in rel/v1.4.0?
Thanks,
Daniel
This message and the information contained herein
Barrett [mailto:jbarr...@amduat.net]
Sent: Wednesday, July 19, 2017 3:09 PM
To: dev@geode.apache.org
Subject: Re: Geode-Native Windows build
Great! Any hiccups with 2017 you can share? Did you install the VC140 toolkit
too?
Sent from my iPhone
> On Jul 19, 2017, at 1:45 AM, Daniel Farcov
dows build
Yup! It should match the the minimum requirements mentioned at the very least.
It should also compile fine under 2017 though I don't believe anyone has yet.
Sent from my iPhone
> On Jul 13, 2017, at 6:08 AM, Daniel Farcovich
> wrote:
>
> From BUILDING.md:
>
July 13, 2017 3:06 PM
To: dev@geode.apache.org
Subject: Re: Geode-Native Windows build
VS 2013 is not fully C++11 compliant. The minimum compiler on windows is VS
2015.
Sent from my iPhone
> On Jul 13, 2017, at 4:32 AM, Daniel Farcovich
> wrote:
>
> As I mentioned in the first em
ted:
#ifdef _WIN32
#if _MSC_VER > 1800 //VS2015 and higher
#define GF_CONSTEXPR constexpr
#else
#define GF_CONSTEXPR
#endif
#else
#define GF_CONSTEXPR constexpr
#endif
Daniel
-Original Message-
From: Daniel Farcovich
Sent: Thursday, July 13, 2017 10:07 AM
To: 'dev@geode.apache.org
you now. Some of the third part libraries built
as part of Geode native have deep directory structures. Your deep directory
structure to your sources combine with that may result in paths over the
windows limit.
Consider using something more shallow on windows, like C:\build. Your source
can
Hi,
I'm failing to build geode native cpp client on windows, although followed the
instructions on BUILDING.md
Looks like there are slash/backslash fixes should be done in the paths in cmake
files.
After overcoming cmake failures the build fails on stage "cmake --build . --
/m" with compilation
Raising this question again.
Daniel
From: Daniel Farcovich
Sent: Wednesday, July 05, 2017 1:26 PM
To: 'dev@geode.apache.org'
Subject: getSizeInBytes() return type
Hi,
We implement getSizeInBytes() in from Sizeable interface.
We have objects with size bigger than MAXINT, bigger than
.
Which mechanisms / functionalities will be affected from this change, I know
rebalancing will be affected for example.
Thanks,
Daniel Farcovich
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https
11 matches
Mail list logo
