You're right that the compiler itself is not the problem. The resulting
dependency on libgfortran.so runtime library and the JAR including the .so file
is the problem. We can remove the .so file from the JAR and require that it's
present on the user's system. That would be similar to how we already
Are we really sure fortran compiler is the issue ? For example, gcc was GPL
but has an exception for compiled-linked binaries using libc, so that the
result binary won't be affected by GPL.
TQ
On Tue, May 12, 2020 at 2:47 PM Lausen, Leonard
wrote:
> On Tue, 2020-05-12 at 13:05 -0700, Zach Kimbe
On Tue, 2020-05-12 at 13:05 -0700, Zach Kimberg wrote:
> I would also like to ask how we use libgfortran? Since it is category X, we
> should not be depending on it for any of the core functionality in MXNet.
> It can only have an "optional feature" (
> https://www.apache.org/legal/resolved.html#op
On Tue, May 12, 2020 at 12:08 PM Lausen, Leonard
wrote:
> On Mon, 2020-05-11 at 13:56 -0400, Carin Meier wrote:
> > Does removing the jars from both of these solutions also remove them from
> > maven central?
>
> Does Maven Central automatically mirror jars from repository.apache.org?
> Or were
>
On Mon, 2020-05-11 at 13:56 -0400, Carin Meier wrote:
> Does removing the jars from both of these solutions also remove them from
> maven central?
Does Maven Central automatically mirror jars from repository.apache.org? Or were
these jars uploaded there manually?
> > 1) Ask the Infra team to dele
Cao
Subject: Re: Severe legal issues with releases on repository.apache.org
External email: Use caution opening links or attachments
On Sun, May 10, 2020 at 8:06 AM Markus Weimer wrote:
> On Sat, May 9, 2020 at 10:50 PM Tianqi Chen wrote:
> >
> > Seems the conclusion so far
y 11, 2020 10:44 AM
To: dev@mxnet.incubator.apache.org
Cc: ptre...@apache.org; Triston Cao
Subject: Re: Severe legal issues with releases on repository.apache.org
External email: Use caution opening links or attachments
On Sun, May 10, 2020 at 8:06 AM Markus Weimer wrote:
> On Sat, May 9, 2020 a
Does removing the jars from both of these solutions also remove them from
maven central?
>
>
> 1) Ask the Infra team to delete all MXNet releases on
> repository.apache.org
> 2) Ask the Infra team to delete all MXNet GPU releases on
> repository.apache.org
> and provide replacement releases without
On Sun, May 10, 2020 at 8:06 AM Markus Weimer wrote:
> On Sat, May 9, 2020 at 10:50 PM Tianqi Chen wrote:
> >
> > Seems the conclusion so far is only release source through apache and
> > release the binary builds as third party(as a different community, a
> > company or individual)
>
> Yes, tha
I agree, In the meanwhile. @Leonard I think we should ask trademark@apache
whether they would approve the use of
repo names: mxnet-cu80 mxnet-cu10 etc, given that
- they are distributed by individual contributors(as individuals and not as
ASF PPMC members),
- marked as thirdparty binary
- Build fr
On Sat, May 9, 2020 at 10:50 PM Tianqi Chen wrote:
>
> Seems the conclusion so far is only release source through apache and
> release the binary builds as third party(as a different community, a
> company or individual)
Yes, that is the precedent established in multiple projects. I think
it migh
Seems the conclusion so far is only release source through apache and
release the binary builds as third party(as a different community, a
company or individual)
TQ
On Sat, May 9, 2020 at 7:39 PM Lausen, Leonard
wrote:
> They actually statically link some libraries such as libcudnn. But even
>
They actually statically link some libraries such as libcudnn. But even removing
that won't necessarily help. Compiling with nvcc and including cuda headers
during compilation incorporates parts of the Cuda SDK into libmxnet.so, and
makes it per the formulation of Cuda EULA subject to certain ASF-i
do the gpu builds actually include the nvidia cuda libraries such as
libcudart.so or just link to them and expect them to be on the machine?
On Fri, May 8, 2020 at 1:50 PM Lausen, Leonard
wrote:
> Hi all,
>
> repository.apache.org is an official Apache Software Foundation release
> channel
> an
Hi all,
repository.apache.org is an official Apache Software Foundation release channel
and the MXNet project has been publishing convenience binaries via that channel
since quite a while. Unfortunately it appears that no-one has initiated a
license review of these convenience binaries, and unfort
15 matches
Mail list logo
