From: Sven M. H. <pe...@gm...> - 2000-05-21 06:11:59
|
Hi everyone, I've been in touch with Brian for some days, have fixed some issues with the configure script, and am now trying to resolve other compilation issues, namely bug #104528 (Mesa 3.2b1 fails to link on Compaq Tru64 UNIX) and #104856 (compilation on cygwinB + win2k fails). Unfortunately I don't have access to Tru64 UNIX so it would be of great help is someone else who does could assist me in finding the reason for the strange behaviour. Over. On the same note, I've already patched configure.in to include the compiler flags suggested in bug #104648 (Tru64 Mesa crashes if not compiled with -g) when on Tru64. Can someone verify the correctness of this? The cygwin case isn't that bad, I have cygwin installed here but am not too familiar with its internals. If there's somebody with more experience I'd greatly appreciate any advice. Thanks, Sven -- "Think for yourself, Schmuck!" [ KeyID........: 0x0F520CF9 ] [ Fingerprint..: 56 61 00 18 14 B4 01 01 06 90 D0 29 96 BD 58 6F ] |
From: Suhaib M. S. <ssi...@nc...> - 2000-05-21 14:46:26
|
> The cygwin case isn't that bad, I have cygwin installed here but > am not too > familiar with its internals. If there's somebody with more experience I'd > greatly appreciate any advice. > > What do you want to do with Cygwin, or what kind of help do you need? Basically, you need to watch out the #ifdef WIN32 and #ifdef __CYGWIN32__ conflicts. I have fixed them several times, but till now I did not participated in Mesa3D developements therefore they never became part of official source tree. A few times, I sent Makefile patches to Brian and they were added config files. BTW: I sawa note on Mesa3D home Page that Brian needs help for Win32 etc. I will be willing to help as time permits. Suhaib > Thanks, > Sven > > -- > "Think for yourself, Schmuck!" > [ KeyID........: 0x0F520CF9 ] > [ Fingerprint..: 56 61 00 18 14 B4 01 01 06 90 D0 29 96 BD 58 6F ] > > _______________________________________________ > Mesa3d-dev mailing list > Mes...@li... > http://lists.sourceforge.net/mailman/listinfo/mesa3d-dev |
From: Sven M. H. <pe...@gm...> - 2000-05-21 17:14:36
|
On Mon, May 22, 2000 at 10:47:36AM -0400, Suhaib M. Siddiqi wrote: > What do you want to do with Cygwin, or what kind of help do you need? There's just an open bug stating that Mesa doesn't compile on cygwin, nothing more. Well I can confirm it doesnt compile. I don't remember exactly what the error was, but I'll post it sometime soon when I get around booting windoze again. > Basically, you need to watch out the #ifdef WIN32 and #ifdef __CYGWIN32__ > conflicts. > I have fixed them several times, but till now I did not participated in > Mesa3D developements > therefore they never became part of official source tree. A few times, I > sent Makefile > patches to Brian and they were added config files. The best thing will probably be if you try to compile Mesa under cygwin yourself, patching those errors you already know. Then just send the patches in so we can, having those all ruled out, start fixing other problems together (if you have time that is). Thanks, Sven -- "Think for yourself, Schmuck!" [ KeyID........: 0xC297FEAB ] [ Fingerprint..: FEA5 0F93 7320 3F39 66A5 AED3 073F 2D5F C297 FEAB ] |
From: Suhaib M. S. <ssi...@nc...> - 2000-05-21 23:59:26
|
> On Mon, May 22, 2000 at 10:47:36AM -0400, Suhaib M. Siddiqi wrote: > > What do you want to do with Cygwin, or what kind of help do you need? > > There's just an open bug stating that Mesa doesn't compile on > cygwin, nothing > more. Well I can confirm it doesnt compile. I don't remember > exactly what the > error was, but I'll post it sometime soon when I get around > booting windoze > again. > What the bug is which prevents its compilation? I will have a look when I get time. > > > Basically, you need to watch out the #ifdef WIN32 and #ifdef > __CYGWIN32__ > > conflicts. > > I have fixed them several times, but till now I did not participated in > > Mesa3D developements > > therefore they never became part of official source tree. A > few times, I > > sent Makefile > > patches to Brian and they were added config files. > > The best thing will probably be if you try to compile Mesa under cygwin > yourself, patching those errors you already know. Then just send > the patches > in so we can, having those all ruled out, start fixing other > problems together > (if you have time that is). > > > Thanks, > Sven > > -- > "Think for yourself, Schmuck!" > [ KeyID........: 0xC297FEAB ] > [ Fingerprint..: FEA5 0F93 7320 3F39 66A5 AED3 073F 2D5F C297 FEAB ] |
From: Sven M. H. <pe...@gm...> - 2000-05-22 10:34:39
|
On Sun, May 21, 2000 at 08:00:19PM -0400, Suhaib M. Siddiqi wrote: > > There's just an open bug stating that Mesa doesn't compile on > > cygwin, nothing > > more. Well I can confirm it doesnt compile. I don't remember > > exactly what the > > error was, but I'll post it sometime soon when I get around > > booting windoze > > again. > > > > > What the bug is which prevents its compilation? > I will have a look when I get time. OK, great. Thanks, Sven -- "Think for yourself, Schmuck!" [ KeyID........: 0xC297FEAB ] [ Fingerprint..: FEA5 0F93 7320 3F39 66A5 AED3 073F 2D5F C297 FEAB ] |
From: Brian P. <br...@pr...> - 2000-05-22 14:15:31
|
"Suhaib M. Siddiqi" wrote: > > > The cygwin case isn't that bad, I have cygwin installed here but > > am not too > > familiar with its internals. If there's somebody with more experience I'd > > greatly appreciate any advice. > > > > > > What do you want to do with Cygwin, or what kind of help do you need? > Basically, you need to watch out the #ifdef WIN32 and #ifdef __CYGWIN32__ > conflicts. > I have fixed them several times, but till now I did not participated in > Mesa3D developements > therefore they never became part of official source tree. A few times, I > sent Makefile > patches to Brian and they were added config files. > > BTW: I sawa note on Mesa3D home Page that Brian needs help for Win32 etc. > I will be willing > to help as time permits. I get occasional emails from people asking why the Windows or DOS drivers don't compile and I explain that nobody has volunteered to maintain them. It would be great if you could help out with this. Later today I'll probably check in a bunch of changes I made to clean-up the GL/gl.h header. I moved a lot of the Windows-related #defines and #pragmas into other files. Testing on Windows will probably expose some typos, etc. -Brian |
From: Sven M. H. <pe...@gm...> - 2000-05-22 14:26:55
|
On Mon, May 22, 2000 at 08:14:24AM -0600, Brian Paul wrote: > > I get occasional emails from people asking why the Windows or DOS > drivers don't compile and I explain that nobody has volunteered to > maintain them. It would be great if you could help out with this. Agreed, that would be good. If something has to be done on the configure process, be sure to let me know, I'll be happy to take it. However I don't have the time or experience to actually do much work on the Win/DOS compilation itself. Sven -- "Think for yourself, Schmuck!" [ KeyID........: 0xC297FEAB ] [ Fingerprint..: FEA5 0F93 7320 3F39 66A5 AED3 073F 2D5F C297 FEAB ] |
From: Stephen J B. <sj...@ht...> - 2000-05-23 12:27:26
|
On Mon, 22 May 2000, Sven M. Hallberg wrote: > On Mon, May 22, 2000 at 08:14:24AM -0600, Brian Paul wrote: > > > > I get occasional emails from people asking why the Windows or DOS > > drivers don't compile and I explain that nobody has volunteered to > > maintain them. It would be great if you could help out with this. > > Agreed, that would be good. If something has to be done on the configure > process, be sure to let me know, I'll be happy to take it. However I > don't have the time or experience to actually do much work on the Win/DOS > compilation itself. Yep - but welcome to the land of freeware. If there is so little interest in something that nobody will step forward to maintain it, it *will* die. It's unreasonable to expect people who are primarily focussed on Linux (and a few other non-Microsoft OS's) to care very much about an OS that already has quite a few reasonable OpenGL implementations. Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation & Training (817)619-2466 (Fax) Work: sj...@ht... http://www.hti.com Home: sjb...@ai... http://web2.airmail.net/sjbaker1 |
From: Suhaib M. S. <ssi...@in...> - 2000-05-22 15:44:22
|
> > I get occasional emails from people asking why the Windows or DOS > drivers don't compile and I explain that nobody has volunteered to > maintain them. It would be great if you could help out with this. > I can help with WIndows, but DOS is beyond my reach. I do not have it installed. > Later today I'll probably check in a bunch of changes I made to > clean-up the GL/gl.h header. I moved a lot of the Windows-related > #defines and #pragmas into other files. Testing on Windows will > probably expose some typos, etc. > There are several options for Windows 1) Microsoft Viusal C/C++ and build Mesa3D with wgl 2) Many developers want Mesa3D with glx API instead of wgl so they can port UNIX OpenGL applications to Windows without rewriting the code. Of course it requires an X-server for Windodws. I had been using Mesa for this option for a while. 3) Cygwin and MingW32 both cane be used to compile Mesa with wgl 4) Cygwin and Microsoft compilers, both, can be used to compile Mesa3D with glx Suhaib > -Brian > > _______________________________________________ > Mesa3d-dev mailing list > Mes...@li... > http://lists.sourceforge.net/mailman/listinfo/mesa3d-dev |