From owner-ogl-sample@oss.sgi.com Wed Nov 1 00:31:28 2000 Received: by oss.sgi.com id ; Wed, 1 Nov 2000 00:31:18 -0800 Received: from mail04.syd.optusnet.com.au ([203.2.75.107]:34758 "EHLO mail04.syd.optusnet.com.au") by oss.sgi.com with ESMTP id ; Wed, 1 Nov 2000 00:31:14 -0800 Received: from bubs (milax1-021.dialup.optusnet.com.au [198.142.191.21]) by mail04.syd.optusnet.com.au (8.9.3/8.9.3) with SMTP id TAA22846 for ; Wed, 1 Nov 2000 19:30:42 +1100 From: root To: ogl-sample@oss.sgi.com Subject: [ogl-sample] Compile Problems Date: Wed, 1 Nov 2000 19:29:57 +1100 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00110119334600.14064@bubs> Content-Transfer-Encoding: 8bit Sender: owner-ogl-sample@oss.sgi.com Precedence: bulk Reply-To: ogl-sample@oss.sgi.com Return-Path: X-Orcpt: rfc822;ogl-sample-outgoing ok my compile problem is that I CANT COMPILE IT AT ALL i thought i was actually getting somewhere getting mose other things to compile and install alot of other programs but when i got this tar.gz file it stumped me pretty bad OK this stressed me out heaps Ok first question HOW DO I SET ENVIROMENT VARIABLES beats me how u do this i looked around and found didly do i just type set GLPRODUCT=DDX or what if i could work out how to set this enviroment i might get it to compile ALso would it be able to make it easier to compile this Need help ergently i run redhat 7 kernel 2.4-test9 tnt2 ultra NVIDIA drivers 0.9-5 Help apreciated From owner-ogl-sample@oss.sgi.com Fri Nov 3 08:43:20 2000 Received: by oss.sgi.com id ; Fri, 3 Nov 2000 08:43:09 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:16406 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Fri, 3 Nov 2000 08:42:43 -0800 Received: from oddhack.engr.sgi.com (oddhack.engr.sgi.com [130.62.54.158]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA28501 for ; Fri, 3 Nov 2000 08:34:53 -0800 (PST) mail_from (ljp@oddhack.engr.sgi.com) Received: (from ljp@localhost) by oddhack.engr.sgi.com (SGI-8.9.3/8.9.3) id IAA06795; Fri, 3 Nov 2000 08:41:27 -0800 (PST) Message-ID: <20001103084127.A6751@oddhack.engr.sgi.com> Date: Fri, 3 Nov 2000 08:41:27 -0800 From: Jon Leech To: ogl-sample@oss.sgi.com Subject: Re: [ogl-sample] gl.spec file missing offset values References: <14845.58250.506669.313124@arioch.engr.sgi.com> <39FDE614.B340AEE7@valinux.com> <14846.3002.95992.559934@arioch.engr.sgi.com> <39FE0E05.CE10A154@valinux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 In-Reply-To: <39FE0E05.CE10A154@valinux.com>; from Brian Paul on Mon, Oct 30, 2000 at 05:10:45PM -0700 Sender: owner-ogl-sample@oss.sgi.com Precedence: bulk Reply-To: ogl-sample@oss.sgi.com Return-Path: X-Orcpt: rfc822;ogl-sample-outgoing On Mon, Oct 30, 2000 at 05:10:45PM -0700, Brian Paul wrote: > I explained the "alias DeleteTextures" in another email last week. > Didn't that go through either??? > > I can live without that fix but if it's not an alias function then it > should have its own dispatch offset. DeleteTextures is defined to use different protocol from the EXT version, so they are not aliases according to the meaning used in the spec files (which is that not just the GL semantics, but *all* behavior beyond the subroutine entry point must be identical). Most extension entry points which get promoted really are aliases in this sense, because they share the same GLX rendering opcode, but for queries the protocol is changed from vendor private to GLX "single". So yes, it should have its own dispatch offset. The spec file needs a way to distinguish between aliasing on the client and server side - probably a new alias keyword - to capture this distinction, so that more of the GLX client/server code could be autogenerated. Jon From owner-ogl-sample@oss.sgi.com Tue Nov 21 06:48:28 2000 Received: by oss.sgi.com id ; Tue, 21 Nov 2000 06:48:19 -0800 Received: from gate.imi.nrc.ca ([206.167.202.2]:59662 "EHLO imi.nrc.ca") by oss.sgi.com with ESMTP id ; Tue, 21 Nov 2000 06:47:56 -0800 Received: from mcgill.ca (172.17.21.60 [172.17.21.60]) by NRCBOUEX1.imi.nrc.ca with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id W8B3PP0K; Tue, 21 Nov 2000 09:43:44 -0500 Message-ID: <3A1A8AF9.65174FC0@mcgill.ca> Date: Tue, 21 Nov 2000 09:47:21 -0500 From: Pierre Cyr X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.17 i686) X-Accept-Language: en MIME-Version: 1.0 To: ogl-sample@oss.sgi.com Subject: [ogl-sample] Building from scratch Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ogl-sample@oss.sgi.com Precedence: bulk Reply-To: ogl-sample@oss.sgi.com Return-Path: X-Orcpt: rfc822;ogl-sample-outgoing Hi, I have been building a Linux from scratch (www.linuxfromscratch.org) system and I am at the step just before installing XFree86 and OpenGL. First Question: When I first untarred ogl-sample and tried compiling it, the make World hung, so I digged and found this at line 105 in main/tools/libspec/libspec.sh while getopts "dD:T:P:" f which I changed for: while getopts "d:D:T:P" f Is this correct? It does not hang any more but my understanding of Bash is limited so I am not sure about this. Second question: Should I install XFree86 before trying to build OpenGL? (I got some error messages about header files that could not be found in the X11 directory (which is not in the XFree86 source tree but would be /usr/X11R6/include/X11 after installation of X)) Third question: I tried building on another linux from scratch system that has X already installed. I get some other error messages and OGL sample does not build all the libraries it is supposed to build. I assume this is because some of the commands used in the scripts are not installed in my system. What are the prerequesites for building OGL sample (appart from awk and Perl)? On my side I will make a log of the build and examine the things I seem to be missing. Thank you, Pierre Cyr From owner-ogl-sample@oss.sgi.com Mon Nov 27 01:34:10 2000 Received: by oss.sgi.com id ; Mon, 27 Nov 2000 01:34:00 -0800 Received: from mail1.worldcom.ch ([212.74.176.11]:14788 "EHLO mail.worldcom.ch") by oss.sgi.com with ESMTP id ; Mon, 27 Nov 2000 01:33:37 -0800 Received: from cyberbotics.com ([212.74.183.57]) by mail.worldcom.ch (8.9.3+Sun/8.9.3) with ESMTP id KAA20606; Mon, 27 Nov 2000 10:31:52 +0100 (MET) Message-ID: <3A222DDE.4880DB37@cyberbotics.com> Date: Mon, 27 Nov 2000 10:48:14 +0100 From: Olivier Michel Organization: Cyberbotics Ltd. X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.15-2.9.0 ppc) X-Accept-Language: en MIME-Version: 1.0 To: Sven Goethel CC: Brian Paul , mesa-dev , ogl-sample@oss.sgi.com Subject: [ogl-sample] Re: Thanxs for SGI's GLU 1.3 libs ! References: <00112702165206.01485@phalanx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ogl-sample@oss.sgi.com Precedence: bulk Reply-To: ogl-sample@oss.sgi.com Return-Path: X-Orcpt: rfc822;ogl-sample-outgoing Sven Goethel wrote: > Thanxs a lot ! > > How about integrating the SGI GLU Sources to the Mesa distribution ? > Did you asked Brian ? Yes. Brian told me that he would like to see this SGI GLU integrated into Mesa in a forthcoming version of Mesa, but I cannot tell you when. There may be problems with mixing different licenses into a single package... (SGI OSS license is different from Mesa LGPL, don't ask me where!). > The current GLU 1.1 Version is very useless > - - as Brian stated also on his Mesa site ! > > Yours, Sven > - -- > mailto:sgoethel@jausoft.com -Olivier From owner-ogl-sample@oss.sgi.com Mon Nov 27 08:39:31 2000 Received: by oss.sgi.com id ; Mon, 27 Nov 2000 08:39:12 -0800 Received: from smtp-fwd.valinux.com ([198.186.202.196]:41225 "EHLO mail.valinux.com") by oss.sgi.com with ESMTP id ; Mon, 27 Nov 2000 08:38:50 -0800 Received: from jens2.cmn.net ([207.174.125.34] helo=valinux.com) by mail.valinux.com with esmtp (Exim 3.16 #1 (Debian)) id 140RII-0007J3-00; Mon, 27 Nov 2000 08:38:18 -0800 Message-ID: <3A228F5A.C3942C72@valinux.com> Date: Mon, 27 Nov 2000 09:44:10 -0700 From: Brian Paul Organization: VA Linux Systems, Inc. X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.4.0-test10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Olivier Michel CC: Sven Goethel , mesa-dev , ogl-sample@oss.sgi.com Subject: [ogl-sample] Re: [Mesa3d-dev] Re: Thanxs for SGI's GLU 1.3 libs ! References: <00112702165206.01485@phalanx> <3A222DDE.4880DB37@cyberbotics.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ogl-sample@oss.sgi.com Precedence: bulk Reply-To: ogl-sample@oss.sgi.com Return-Path: X-Orcpt: rfc822;ogl-sample-outgoing Olivier Michel wrote: > > Sven Goethel wrote: > > > Thanxs a lot ! > > > > How about integrating the SGI GLU Sources to the Mesa distribution ? > > Did you asked Brian ? > > Yes. Brian told me that he would like to see this SGI GLU integrated > into Mesa in a forthcoming version of Mesa, but I cannot tell you when. I haven't started that work either, yet. > There may be problems with mixing different licenses into a single > package... (SGI OSS license is different from Mesa LGPL, don't ask me > where!). The main Mesa library is not LGPL, it's copyrighted XFree86-style. There are some other components in the Mesa distro such as GLUT, GLU and some drivers which have other copyrights. It's explained in the docs. The SI GLU copyright is compatible with XFree86 so there should be no problem including the sources with Mesa. The concern I have is what to do for people who do not have a C++ compiler. If they can't compile the SI GLU they'll either need to use the old Mesa GLU or find a precompiled library for their system. And until they solve that, they can't run many of the Mesa demos, etc. -Brian From owner-ogl-sample@oss.sgi.com Mon Nov 27 14:07:33 2000 Received: by oss.sgi.com id ; Mon, 27 Nov 2000 14:07:13 -0800 Received: from smtp.discreet.com ([209.58.5.130]:10983 "EHLO smtp.discreet.com") by oss.sgi.com with ESMTP id ; Mon, 27 Nov 2000 14:07:01 -0800 Received: from cuba.discreet.qc.ca (cuba.discreet.qc.ca [172.16.50.110]) by smtp.discreet.com (8.9.3/8.9.3) with ESMTP id RAA07045; Mon, 27 Nov 2000 17:05:03 -0500 (EST) Received: from discreet.com (norway.rd.discreet.qc.ca [192.168.10.71]) by cuba.discreet.qc.ca (8.9.3/8.9.3) with ESMTP id RAA1338081; Mon, 27 Nov 2000 17:06:55 -0500 (EST) Message-Id: <200011272206.RAA1338081@cuba.discreet.qc.ca> To: mesa-dev cc: ogl-sample@oss.sgi.com Subject: [ogl-sample] Re: [Mesa3d-dev] Re: Thanxs for SGI's GLU 1.3 libs ! In-Reply-To: Message from Brian Paul of "Mon, 27 Nov 2000 09:44:10 MST." <3A228F5A.C3942C72@valinux.com> Date: Mon, 27 Nov 2000 17:06:54 -0500 From: Jean-Francois Panisset Sender: owner-ogl-sample@oss.sgi.com Precedence: bulk Reply-To: ogl-sample@oss.sgi.com Return-Path: X-Orcpt: rfc822;ogl-sample-outgoing > > The SI GLU copyright is compatible with XFree86 so there should be > no problem including the sources with Mesa. The concern I have is > what to do for people who do not have a C++ compiler. If they > can't compile the SI GLU they'll either need to use the old Mesa > GLU or find a precompiled library for their system. And until > they solve that, they can't run many of the Mesa demos, etc. > And given the state of flux of the C++ ABI and runtime libraries under Linux, I'm personally not too fond of C++-compiled system libraries right now. For instance, the SGI GLU included with the SGI ProPack 1.3 overlay has a runtime dependency on /usr/lib/libstdc++-libc6.1-1.so.2 (ouch). If you need to compile a program with a newer version of g++ (for instance one of the 2.97 snapshots which installs its own libstdc++ in /usr/local/lib) where both the runtime library and the ABI are incompatible, you are likely to run into problems. I have no idea how this g++ ABI transition is going to be handled... JF From owner-ogl-sample@oss.sgi.com Mon Nov 27 14:42:03 2000 Received: by oss.sgi.com id ; Mon, 27 Nov 2000 14:41:54 -0800 Received: from mailout03.sul.t-online.com ([194.25.134.81]:39176 "EHLO mailout03.sul.t-online.com") by oss.sgi.com with ESMTP id ; Mon, 27 Nov 2000 14:41:41 -0800 Received: from fwd06.sul.t-online.com by mailout03.sul.t-online.com with smtp id 140Wxh-00060R-07; Mon, 27 Nov 2000 23:41:25 +0100 Received: from phalanx (05212399440-0001@[62.226.24.12]) by fmrl06.sul.t-online.com with smtp id 140Wxc-05ALyaC; Mon, 27 Nov 2000 23:41:20 +0100 From: Sven Goethel Organization: Jausoft - Sven Goethel Software Development Date: Mon, 27 Nov 2000 23:40:56 +0100 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" Cc: mesa-dev , ogl-sample@oss.sgi.com To: Brian Paul , Olivier Michel References: <00112702165206.01485@phalanx> <3A222DDE.4880DB37@cyberbotics.com> <3A228F5A.C3942C72@valinux.com> In-Reply-To: <3A228F5A.C3942C72@valinux.com> Subject: [ogl-sample] Re: [Mesa3d-dev] Re: Thanxs for SGI's GLU 1.3 libs ! MIME-Version: 1.0 Message-Id: <00112723405601.00861@phalanx> Content-Transfer-Encoding: 8bit X-Sender: 05212399440-0001@t-dialin.net Sender: owner-ogl-sample@oss.sgi.com Precedence: bulk Reply-To: ogl-sample@oss.sgi.com Return-Path: X-Orcpt: rfc822;ogl-sample-outgoing -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 27 November 2000 17:44, Brian Paul wrote: > Olivier Michel wrote: > > Sven Goethel wrote: > > > Thanxs a lot ! > > > > > > How about integrating the SGI GLU Sources to the Mesa distribution ? > > > Did you asked Brian ? > > > > Yes. Brian told me that he would like to see this SGI GLU integrated > > into Mesa in a forthcoming version of Mesa, but I cannot tell you when. > > I haven't started that work either, yet. > > > There may be problems with mixing different licenses into a single > > package... (SGI OSS license is different from Mesa LGPL, don't ask me > > where!). > > The main Mesa library is not LGPL, it's copyrighted XFree86-style. > There are some other components in the Mesa distro such as GLUT, GLU > and some drivers which have other copyrights. It's explained in > the docs. > > The SI GLU copyright is compatible with XFree86 so there should be > no problem including the sources with Mesa. The concern I have is > what to do for people who do not have a C++ compiler. If they > can't compile the SI GLU they'll either need to use the old Mesa > GLU or find a precompiled library for their system. And until > they solve that, they can't run many of the Mesa demos, etc. > > -Brian Aehem, well, but how about splitting the Mesa distribution from: MesaLib & MesaDemos to: MesaLib & (MesaSGIGLU || MesaGLU) & MesaDemos where, of course, the MesaSGIGLU is preferred .. just an idea. another Q: why do you revert the MesaGLU to GLU 1.1 ? kind regards, sven - -- mailto:sgoethel@jausoft.com www : http://www.jausoft.com ; pgp: http://www.jausoft.com/gpg/ voice : +49-521-2399440, +49-170-2115963; fax: +49-521-2399442 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6IuL4HdOA30NoFAARAtQ1AJ4oLroYFigJWYLOplMXk2dQaejbLQCgj9C1 kdzzSQDAx4+AdF7onEIFcIA= =Yju6 -----END PGP SIGNATURE----- From owner-ogl-sample@oss.sgi.com Mon Nov 27 14:49:34 2000 Received: by oss.sgi.com id ; Mon, 27 Nov 2000 14:49:14 -0800 Received: from smtp-fwd.valinux.com ([198.186.202.196]:30734 "EHLO mail.valinux.com") by oss.sgi.com with ESMTP id ; Mon, 27 Nov 2000 14:49:12 -0800 Received: from jens2.cmn.net ([207.174.125.34] helo=valinux.com) by mail.valinux.com with esmtp (Exim 3.16 #1 (Debian)) id 140X4y-0002Yf-00; Mon, 27 Nov 2000 14:48:56 -0800 Message-ID: <3A22E639.59E9415A@valinux.com> Date: Mon, 27 Nov 2000 15:54:49 -0700 From: Brian Paul Organization: VA Linux Systems, Inc. X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.4.0-test10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Sven Goethel CC: Olivier Michel , mesa-dev , ogl-sample@oss.sgi.com Subject: [ogl-sample] Re: [Mesa3d-dev] Re: Thanxs for SGI's GLU 1.3 libs ! References: <00112702165206.01485@phalanx> <3A222DDE.4880DB37@cyberbotics.com> <3A228F5A.C3942C72@valinux.com> <00112723405601.00861@phalanx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ogl-sample@oss.sgi.com Precedence: bulk Reply-To: ogl-sample@oss.sgi.com Return-Path: X-Orcpt: rfc822;ogl-sample-outgoing Sven Goethel wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Monday 27 November 2000 17:44, Brian Paul wrote: > > Olivier Michel wrote: > > > Sven Goethel wrote: > > > > Thanxs a lot ! > > > > > > > > How about integrating the SGI GLU Sources to the Mesa distribution ? > > > > Did you asked Brian ? > > > > > > Yes. Brian told me that he would like to see this SGI GLU integrated > > > into Mesa in a forthcoming version of Mesa, but I cannot tell you when. > > > > I haven't started that work either, yet. > > > > > There may be problems with mixing different licenses into a single > > > package... (SGI OSS license is different from Mesa LGPL, don't ask me > > > where!). > > > > The main Mesa library is not LGPL, it's copyrighted XFree86-style. > > There are some other components in the Mesa distro such as GLUT, GLU > > and some drivers which have other copyrights. It's explained in > > the docs. > > > > The SI GLU copyright is compatible with XFree86 so there should be > > no problem including the sources with Mesa. The concern I have is > > what to do for people who do not have a C++ compiler. If they > > can't compile the SI GLU they'll either need to use the old Mesa > > GLU or find a precompiled library for their system. And until > > they solve that, they can't run many of the Mesa demos, etc. > > > > -Brian > > Aehem, well, but how about splitting the Mesa distribution from: > MesaLib & MesaDemos > to: > MesaLib & (MesaSGIGLU || MesaGLU) & MesaDemos > > where, of course, the MesaSGIGLU is preferred .. Yes, I might do that. > another Q: why do you revert the MesaGLU to GLU 1.1 ? Because there were a few severe bugs in the (unfinished) 1.2 tessellator implementation. -Brian From owner-ogl-sample@oss.sgi.com Tue Nov 28 05:45:02 2000 Received: by oss.sgi.com id ; Tue, 28 Nov 2000 05:44:52 -0800 Received: from sunmgr.hti.com ([130.210.206.69]:53715 "EHLO issun6.hti.com") by oss.sgi.com with ESMTP id ; Tue, 28 Nov 2000 05:44:37 -0800 Received: from issun5.hti.com ([130.210.202.3]) by issun6.hti.com (Netscape Messaging Server 3.6) with ESMTP id AAA3617 for ; Tue, 28 Nov 2000 07:43:17 -0600 Received: from sutcliffe.bgm.link.com ([130.210.63.42]) by issun5.hti.com (Netscape Messaging Server 3.6) with SMTP id AAA70E1; Tue, 28 Nov 2000 07:42:49 -0600 Date: Tue, 28 Nov 2000 07:42:49 -0600 (CST) From: "Stephen J Baker" X-Sender: steve@sutcliffe.bgm.link.com To: ogl-sample@oss.sgi.com cc: Brian Paul , Olivier Michel , mesa-dev Subject: Re: [ogl-sample] Re: [Mesa3d-dev] Re: Thanxs for SGI's GLU 1.3 libs ! In-Reply-To: <00112723405601.00861@phalanx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ogl-sample@oss.sgi.com Precedence: bulk Reply-To: ogl-sample@oss.sgi.com Return-Path: X-Orcpt: rfc822;ogl-sample-outgoing On Mon, 27 Nov 2000, Sven Goethel wrote: > Aehem, well, but how about splitting the Mesa distribution from: > MesaLib & MesaDemos > to: > MesaLib & (MesaSGIGLU || MesaGLU) & MesaDemos > > where, of course, the MesaSGIGLU is preferred .. If there are going to be ugly issues with which C++ runtime library SGI-GLU pulls-in/requires then I think it's vital from an application support perspective to minimise the number of varients there can be out there. I would not want to see (say) Debian and RedHat shipping the SGI version of GLU with SuSE and Corel shipping GLU-classic. I'd also oppose splitting GLU off from Mesa's main download because that will result in lots of end-users installing "Mesa" and yet having no valid GLU implementation because they failed to download/install it. Supporting OpenGL applications under Linux is hard enough as it is - look at the mail archives for an active OpenGL application (TuxRacer for example) and you'll see that at least 95% of the posts are OpenGL installation problems of one kind or another. That consumes an insane amount of people's time - PLEASE, let's not make it any harder. IMHO, 99% of widely distributed OpenGL apps for Linux will not be using the problematic functions in GLU-classic - because those programs were almost certainly developed using that library and either don't use the broken functions or have work-arounds that work OK. Hence most existing applications will get no benefit from SGI-GLU. In any case, the kinds of applications that need things like tesselators and spline patches tend not to be games - more often they are things like scientific visualisers and custom applications which are not widely circulated. Hence, I suggest that until the g++ standard library stuff settles A down, we avoid making SGI-GLU the default. I think the Mesa documentation should point out that we *WILL* make the transition - but not yet - and advise people who experience problems with GLU-classic to switch over immediately. Meanwhile I think we should continue to ship GLU-classic by default. --- Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation & Training (817)619-2466 (Fax) Work: sjbaker@link.com http://www.link.com Home: sjbaker1@airmail.net http://web2.airmail.net/sjbaker1