Re: R280 texture pipe bug still there [PATCH]
On Thu, 2005-08-25 at 00:44 -0500, Alan Grimes wrote: ^^^ Just install libdrm from DRM CVS. It's a requirement now. IN FILE xf86drm.h AND include/GL/internal/dri_interface.h CHANGE #include drm.h #include drm/drm.h All that does is paper over the cracks. It's a symptom of pkg-config not finding libdrm. You need to find out why pkg-config isn't finding libdrm -- whether that be that you didn't make install it properly, but just copied it, or that the place you installed it to isn't in your PKG_CONFIG_PATH, whatever -- and fix that. --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R280 texture pipe bug still there [PATCH]
Daniel Stone wrote: On Thu, 2005-08-25 at 00:44 -0500, Alan Grimes wrote: ^^^ Just install libdrm from DRM CVS. It's a requirement now. IN FILE xf86drm.h AND include/GL/internal/dri_interface.h CHANGE #include drm.h #include drm/drm.h All that does is paper over the cracks. It's a symptom of pkg-config not finding libdrm. You need to find out why pkg-config isn't finding libdrm -- whether that be that you didn't make install it properly, but just copied it, or that the place you installed it to isn't in your PKG_CONFIG_PATH, whatever -- and fix that. 1. I have no idea what pkgconfig is. 2. I successfully (relatively) installed the package without knowing what pkgconfig is with minimial effort. 3. The existance of pkgconfig therefore places an increased UNNECESSARY managment/learning/fussingwith burdeon on the USER, a mortal sin for any developer, and should therefore be removed from all *nix/*nux systems with the most extreme prejudice. 4. /me adds pkgconfig to the multi-volume list of things I hate about unix. 5. Unless someone starts paying me, I'm not even going to waste another second thinking about pkgconfig. If it decides to start working FINE, if it doesn't I DON'T CARE, I HAVE BETTER THINGS TO DO WITH MY LIFE!! -- Friends don't let friends use GCC 3.4.4 GCC 3.3.6 produces code that's twice as fast on x86! Non-sequiter item: Charleston, South Carolina --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R280 texture pipe bug still there [PATCH]
On 8/25/05, Alan Grimes [EMAIL PROTECTED] wrote: Daniel Stone wrote: On Thu, 2005-08-25 at 00:44 -0500, Alan Grimes wrote: ^^^ Just install libdrm from DRM CVS. It's a requirement now. IN FILE xf86drm.h AND include/GL/internal/dri_interface.h CHANGE #include drm.h #include drm/drm.h All that does is paper over the cracks. It's a symptom of pkg-config not finding libdrm. You need to find out why pkg-config isn't finding libdrm -- whether that be that you didn't make install it properly, but just copied it, or that the place you installed it to isn't in your PKG_CONFIG_PATH, whatever -- and fix that. 1. I have no idea what pkgconfig is. 2. I successfully (relatively) installed the package without knowing what pkgconfig is with minimial effort. 3. The existance of pkgconfig therefore places an increased UNNECESSARY managment/learning/fussingwith burdeon on the USER, a mortal sin for any developer, and should therefore be removed from all *nix/*nux systems with the most extreme prejudice. 4. /me adds pkgconfig to the multi-volume list of things I hate about unix. 5. Unless someone starts paying me, I'm not even going to waste another second thinking about pkgconfig. If it decides to start working FINE, if it doesn't I DON'T CARE, I HAVE BETTER THINGS TO DO WITH MY LIFE!! believe it or not pkgconfig actually makes your life easier...once you get to know it ;) It's the unix way. It basically tells you where to find header information for various packages. You copy the package's .pc file to the pkgconfig directory (often /usr/lib/pkgconfig). then try and build again. Alex -- Friends don't let friends use GCC 3.4.4 GCC 3.3.6 produces code that's twice as fast on x86! Non-sequiter item: Charleston, South Carolina --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R280 texture pipe bug still there [PATCH]
believe it or not pkgconfig actually makes your life easier...once you get to know it ;) It's the unix way. It basically tells you where to find header information for various packages. You copy the package's .pc file to the pkgconfig directory (often /usr/lib/pkgconfig). then try and build again. Alex To someone just wanting to get DRI working the libdrm stuff makes things more complicated. I think libdrm just just install itself to some location where it is found by pkgconfig by default, so that one doesn't have to learn about pkgconfig just to compile Mesa. Philipp --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R280 texture pipe bug still there [PATCH]
On 8/25/05, Philipp Klaus Krause [EMAIL PROTECTED] wrote: believe it or not pkgconfig actually makes your life easier...once you get to know it ;) It's the unix way. It basically tells you where to find header information for various packages. You copy the package's .pc file to the pkgconfig directory (often /usr/lib/pkgconfig). then try and build again. Alex To someone just wanting to get DRI working the libdrm stuff makes things more complicated. I think libdrm just just install itself to some location where it is found by pkgconfig by default, so that one doesn't have to learn about pkgconfig just to compile Mesa. well, once libdrm becomes standard in distributions, that will be the case. You are using development code you must remember. Alex Philipp --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R280 texture pipe bug still there [PATCH]
^^^ Just install libdrm from DRM CVS. It's a requirement now. IN FILE xf86drm.h AND include/GL/internal/dri_interface.h CHANGE #include drm.h #include drm/drm.h -- Friends don't let friends use GCC 3.4.4 GCC 3.3.6 produces code that's twice as fast on x86! Non-sequiter item: Charleston, South Carolina --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
