I would say for this PR, back out the LGTM changes and just move forward
ignoring the LGTM results.
> On Jul 31, 2019, at 12:14 PM, Blake Bender wrote:
>
> Still looking into this, don’t expect to have a resolution today
> necessarily. I turned off network support in our build of Xerces, since
Still looking into this, don’t expect to have a resolution today
necessarily. I turned off network support in our build of Xerces, since we
don’t use it, and that got rid of some, but not all, of the unresolved
references. I’ll have to get hold of the LGTM Docker image to see what’s
going on with
In preparation for cutting the release branch have we confirmed that
Geode's LICENSE and NOTICE file been confirmed to accurately reflect what
is being shipped for v1.10?
>From Apache: http://www.apache.org/dev/licensing-howto.html
*"*The LICENSE and NOTICE files must exactly represent the content
Linking errors look like (perhaps among other things) missing symbols for
libcurl(?) needed by the Xerces library, which was recently added. We
build internally against RHEL 7, Ubuntu, Windows, and develop on MacBook
Pros, but it appears LGTM is attempting to build on some other OS flavor
and mayb
Hi,
I updated the .lgtm.yml file so that the right version of Apache Geode
is downloaded and now I get errors in the linking process about some
symbols not found.
Could anybody help with this?
Thanks,
Alberto
On 30/7/19 15:50, Jacob Barrett wrote:
> Yes, that seems to be the issue. Can you u
