[GRASS5] Sgi widgets license

GRASS GRASS developer
1

Hello all

I was trying to install GRASS on a linux machine when I came across the
infamous drawing area linking problem (ie, we need sgi widgets to
compile g3d code - see request below to change configure.in). While
looking in the sgi widget code in Mesa I came across the following in
the widgets-sgi/README file:

These files are NOT covered by Mesa's GNU copyright. The real copyright
is as follows.

* (c) Copyright 1993, Silicon Graphics, Inc.
* ALL RIGHTS RESERVED
* Permission to use, copy, modify, and distribute this software for
* any purpose and without fee is hereby granted, provided that the
* above copyright notice appear in all copies and that both the
* copyright notice and this permission notice appear in supporting
* documentation, and that the name of Silicon Graphics, Inc. not be
* used in advertising or publicity pertaining to distribution of the
* software without specific, written prior permission.
*
* THE MATERIAL EMBODIED ON THIS SOFTWARE IS PROVIDED TO YOU "AS-IS"
* AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE,
* INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR
* FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SILICON
* GRAPHICS, INC. BE LIABLE TO YOU OR ANYONE ELSE FOR ANY DIRECT,
* SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY
* KIND, OR ANY DAMAGES WHATSOEVER, INCLUDING WITHOUT LIMITATION,
* LOSS OF PROFIT, LOSS OF USE, SAVINGS OR REVENUE, OR THE CLAIMS OF
* THIRD PARTIES, WHETHER OR NOT SILICON GRAPHICS, INC. HAS BEEN
* ADVISED OF THE POSSIBILITY OF SUCH LOSS, HOWEVER CAUSED AND ON
* ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE
* POSSESSION, USE OR PERFORMANCE OF THIS SOFTWARE.
*
*
* US Government Users Restricted Rights
* Use, duplication, or disclosure by the Government is subject to
* restrictions set forth in FAR 52.227.19(c)(2) or subparagraph
* (c)(1)(ii) of the Rights in Technical Data and Computer Software
* clause at DFARS 252.227-7013 and/or in similar or successor
* clauses in the FAR or the DOD or NASA FAR Supplement.
* Unpublished-- rights reserved under the copyright laws of the
* United States. Contractor/manufacturer is Silicon Graphics,
* Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311.
*
* OpenGL(TM) is a trademark of Silicon Graphics, Inc.

I know little about licenses, so I was wondering if this license is
compatible with GPL?

Also, since g3d is not included in grass5 I think that configure should
be changed so that it does not search for this drawing area dependency.
What happened for me was that configure indicated that it failed to find
the OpenGL libraries and thus the head file was not updated properly.
Thus, nviz failed to compile. I tried to find where this was tested in
configure but my attempts to comment out the code failed. Could someone
comment out the proper code in configure.in so that nviz will compile
without the sgi widgets installed?

Thanks.

--
Sincerely,

Jazzman (a.k.a. Justin Hickey) e-mail: jhickey@hpcc.nectec.or.th
High Performance Computing Center
National Electronics and Computer Technology Center (NECTEC)
Bangkok, Thailand

People who think they know everything are very irritating to those
of us who do. ---Anonymous

Jazz and Trek Rule!!!

From neteler Fri Jun 29 15:12:10 2001
Return-Path: <neteler>
Received: by hgeo02.geog.uni-hannover.de (SMI-8.6/SMI-SVR4)
  id PAA17202; Fri, 29 Jun 2001 15:12:10 +0100
Date: Fri, 29 Jun 2001 15:12:10 +0100
From: Markus Neteler <neteler@geog.uni-hannover.de>
To: grass5 developers list <grass5@geog.uni-hannover.de>
Message-ID: <20010629151210.L16481@hgeo02.geog.uni-hannover.de>
Mail-Followup-To: grass5 developers list <grass5@geog.uni-hannover.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Subject: [GRASS5] shift bug in r.in.ascii/r.out.ascii
Sender: grass5-admin@geog.uni-hannover.de
Errors-To: grass5-admin@geog.uni-hannover.de
X-BeenThere: grass5@geog.uni-hannover.de
X-Mailman-Version: 2.0.5
Precedence: bulk
List-Help: <mailto:grass5-request@geog.uni-hannover.de?subject=help>
List-Post: <mailto:grass5@geog.uni-hannover.de>
List-Subscribe: <http://www.geog.uni-hannover.de/mailman/listinfo/grass5&gt;,
  <mailto:grass5-request@geog.uni-hannover.de?subject=subscribe>
List-Id: GRASS 5 Developers mailing list <grass5.geog.uni-hannover.de>
List-Unsubscribe: <http://www.geog.uni-hannover.de/mailman/listinfo/grass5&gt;,
  <mailto:grass5-request@geog.uni-hannover.de?subject=unsubscribe>
List-Archive: <http://www.geog.uni-hannover.de/pipermail/grass5/&gt;
Status: O
Content-Length: 492
Lines: 23

Hi all,

just found (obviously) a bug in r.in.ascii/r.out.ascii:

if you export/import the same map several times, it get's
shifted each time!

     r.out.ascii in=dem out=dem0.asc
     r.in.ascii in=dem0.asc out=dem1

     r.out.ascii in=dem1 out=dem1.asc
     r.in.ascii in=dem1.asc out=dem2

     r.out.ascii in=dem2 out=dem2.asc
     r.in.ascii in=dem2.asc out=dem3
     d.rast dem
     d.rast dem1
     d.rast dem2
     d.rast dem3

As being lack of time today, any volunteers?

Markus

2

Justin Hickey wrote:

I was trying to install GRASS on a linux machine when I came across the
infamous drawing area linking problem (ie, we need sgi widgets to
compile g3d code - see request below to change configure.in). While
looking in the sgi widget code in Mesa I came across the following in
the widgets-sgi/README file:

These files are NOT covered by Mesa's GNU copyright. The real copyright
is as follows.

[snip]

I know little about licenses, so I was wondering if this license is
compatible with GPL?

For binary distribution it might be better to use the version which
comes with XFree86 4.0.* (configure won't detect it automatically, but
you can force its use). I think that should qualify for the "anything
that is normally distributed ... with the major components ... of the
operating system" exception.

Also, since g3d is not included in grass5 I think that configure should
be changed so that it does not search for this drawing area dependency.
What happened for me was that configure indicated that it failed to find
the OpenGL libraries and thus the head file was not updated properly.
Thus, nviz failed to compile.

Isn't this just because the OpenGL libraries weren't found, rather
than due to libGLwM?

For me, configure always fails to find libGLwM[1], but NVIZ still gets
built.

[1] This is a Mesa-ism; XFree86 has both Motif and non-Motif widgets
in libGLw, but GLwCreateMDrawingArea is a macro, which causes the test
to fail.

I tried to find where this was tested in
configure but my attempts to comment out the code failed. Could someone
comment out the proper code in configure.in so that nviz will compile
without the sgi widgets installed?

NVIZ should already compile regardless of whether the SGI widgets are
installed. What error message(s) do you get during NVIZ' compilation?

--
Glynn Clements <glynn.clements@virgin.net>

3

On Fri, Jun 29, 2001 at 05:05:47PM +0700, Justin Hickey wrote:

looking in the sgi widget code in Mesa I came across the following in
the widgets-sgi/README file:

These files are NOT covered by Mesa's GNU copyright. The real copyright
is as follows.

* Permission to use, copy, modify, and distribute this software for
* any purpose and without fee is hereby granted, provided that the
* above copyright notice appear in all copies and that both the
* copyright notice and this permission notice appear in supporting
* documentation,

* US Government Users Restricted Rights
* Use, duplication, or disclosure by the Government is subject to
* restrictions set forth in FAR 52.227.19(c)(2) or subparagraph
* (c)(1)(ii) of the Rights in Technical Data and Computer Software
* clause at DFARS 252.227-7013 and/or in similar or successor
* clauses in the FAR or the DOD or NASA FAR Supplement.

I know little about licenses, so I was wondering if this license is
compatible with GPL?

Good question.
I think it comes close, but does not quite make it.
I am not absolutly sure though.

The question is if the additional restrictions actually have an effect.
If they do it is incompatible to the GPL which does not allow
additional restrictions.

We should mail the question to
  licensing@gnu.org