Package: grass
Version: 6.0.2-2
Severity: serious
Tags: patch

When building 'grass' in a clean 'unstable' chroot,
I get the following error:

checking for XmStringCreate in -lXm... yes
checking whether to use GLw... yes
checking for location of GLw includes... 
checking for GL/GLwMDrawA.h... no
checking for X11/GLw/GLwMDrawA.h... no
configure: error: *** Unable to locate GLwM includes.
make: *** [config-stamp] Error 1

The attached patch fixes this problem by changing the Build-Depends 
from 'xlibmesa-gl-dev' to 'libgl1-mesa-swx11-dev' in debian/control.

Regards
Andreas Jochens

diff -urN ../tmp-orig/grass-6.0.2/debian/control ./debian/control
--- ../tmp-orig/grass-6.0.2/debian/control      2006-06-14 09:54:52.000000000 
+0000
+++ ./debian/control    2006-06-14 09:44:15.000000000 +0000
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Debian GIS Project <pkg-grass-devel@lists.alioth.debian.org>
 Uploaders: Francesco Paolo Lovergine <[EMAIL PROTECTED]>, Steve Halasz <[EMAIL 
PROTECTED]>
-Build-depends: flex, bison, libreadline5-dev | libreadline-dev, 
libncurses5-dev, lesstif2-dev, debhelper (>= 4.0.2), dpatch, libtiff4-dev, 
tcl8.4-dev, tk8.4-dev, fftw3-dev, libxmu-dev, xlibmesa-gl-dev, libglu1-xorg-dev 
| xlibmesa-glu-dev, libfreetype6-dev, autoconf2.13, autotools-dev, 
libgdal1-1.3.1-dev, proj (>= 4.4.7), libjpeg62-dev, libpng12-dev, libpq-dev | 
postgresql-dev, unixodbc-dev, doxygen, fakeroot, libmysqlclient15-dev | 
libmysqlclient14-dev, graphviz
+Build-depends: flex, bison, libreadline5-dev | libreadline-dev, 
libncurses5-dev, lesstif2-dev, debhelper (>= 4.0.2), dpatch, libtiff4-dev, 
tcl8.4-dev, tk8.4-dev, fftw3-dev, libxmu-dev, libgl1-mesa-swx11-dev, 
libglu1-xorg-dev | xlibmesa-glu-dev, libfreetype6-dev, autoconf2.13, 
autotools-dev, libgdal1-1.3.1-dev, proj (>= 4.4.7), libjpeg62-dev, 
libpng12-dev, libpq-dev | postgresql-dev, unixodbc-dev, doxygen, fakeroot, 
libmysqlclient15-dev | libmysqlclient14-dev, graphviz
 Standards-Version: 3.6.2
 
 Package: grass


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to