From: Gareth H. <ga...@va...> - 2000-11-30 03:36:54
|
It's the SI GLU. I'd installed the RPM from the resources page (or wherever you get it) and was using that with the DRI, but all versions of standalone Mesa were using the Mesa GLU. Revert back to Mesa's GLU, and gloss runs perfectly. -- Gareth |
From: Brian P. <br...@va...> - 2000-11-30 04:44:35
|
Gareth Hughes wrote: > > It's the SI GLU. > > I'd installed the RPM from the resources page (or wherever you get it) > and was using that with the DRI, but all versions of standalone Mesa > were using the Mesa GLU. Revert back to Mesa's GLU, and gloss runs > perfectly. That's really strange. I think I'm just using gluBuild2DMipMaps() in gloss.c. I'd expect that function to be well tested in the SI GLU. Could you try linking with the SI GLU but copy&paste gluBuild2D- MipMaps() from Mesa's GLU into gloss.c (with a different name) to verify that's the problem? -Brian |
From: Gareth H. <ga...@va...> - 2000-11-30 13:36:03
|
Brian Paul wrote: > > That's really strange. I think I'm just using gluBuild2DMipMaps() > in gloss.c. I'd expect that function to be well tested in the SI GLU. > > Could you try linking with the SI GLU but copy&paste gluBuild2D- > MipMaps() from Mesa's GLU into gloss.c (with a different name) > to verify that's the problem? Will do. It suddenly hit me that this was the only real difference in the use of the Mesa-3.4 code between standalone and the DRI, but I'm as surprised as you are that something's going wrong. -- Gareth |