Bug#675972: gdal: FTBFS: fatal error: ruby.h: No such file or directory
Package: src:gdal Version: 1.9.0-2 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: make[2]: Entering directory `/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/swig/ruby' /bin/bash /build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/libtool --mode=compile --tag=CXX g++ -g -O2 -Wall -fPIC -DPIC -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/port -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/gcore -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/alg -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/ogr -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/ogr/ogrsf_frmts -I/usr/include/ruby-1.9.1 -I/usr/include/ruby-1.9.1/x86_64-linux -c gdal_wrap.cpp libtool: compile: g++ -g -O2 -Wall -fPIC -DPIC -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/port -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/gcore -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/alg -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/ogr -I/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/ogr/ogrsf_frmts -I/usr/include/ruby-1.9.1 -I/usr/include/ruby-1.9.1/x86_64-linux -c gdal_wrap.cpp -fPIC -DPIC -o .libs/gdal_wrap.o gdal_wrap.cpp:856:18: fatal error: ruby.h: No such file or directory compilation terminated. make[2]: *** [gdal_wrap.o] Error 1 make[2]: Leaving directory `/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/swig/ruby' make[1]: *** [build] Error 2 make[1]: Leaving directory `/build/buildd-gdal_1.9.0-2+b1-amd64-8y0tnm/gdal-1.9.0/swig/ruby' make: *** [build-stamp] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=gdalarch=kfreebsd-amd64ver=1.9.0-2%2Bb1stamp=1338821789 Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#675972: gdal: FTBFS: fatal error: ruby.h: No such file or directory
Hi, Does gdal need an explicit Build-Depends: ruby1.8 instead of ruby; would that cause the buildscripts to pick the right include paths? /bin/bash /build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/libtool --mode=compile --tag=CXX g++ -g -O2 -Wall -fPIC -DPIC -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/port -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/gcore -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/alg -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/ogr -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/ogr/ogrsf_frmts -I/usr/include/ruby-1.9.1 -I/usr/include/ruby-1.9.1/i486-kfreebsd-gnu -c gdal_wrap.cpp libtool: compile: g++ -g -O2 -Wall -fPIC -DPIC -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/port -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/gcore -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/alg -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/ogr -I/build/buildd-gdal_1.9.0-2+b1-kfreebsd-i386-sJevbb/gdal-1.9.0/ogr/ogrsf_frmts -I/usr/include/ruby-1.9.1 -I/usr/include/ruby-1.9.1/i486-kfreebsd-gnu -c gdal_wrap.cpp -fPIC -DPIC -o .libs/gdal_wrap.o gdal_wrap.cpp:856:18: fatal error: ruby.h: No such file or directory Build-Depends were: ruby ruby1.8-dev The buildd actually resolved these to: libruby1.8_1.8.7.358-4 libruby1.9.1_1.9.3.194-1 ruby_4.9 ruby1.8-dev_1.8.7.358-4 ruby1.9.1_1.9.3.194-1 Regards, -- Steven Chamberlain ste...@pyro.eu.org ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#675972: gdal: FTBFS: fatal error: ruby.h: No such file or directory
Hello, On Mon, Jun 4, 2012 at 9:18 PM, Steven Chamberlain ste...@pyro.eu.org wrote: Does gdal need an explicit Build-Depends: ruby1.8 instead of ruby; would that cause the buildscripts to pick the right include paths? Yep. The problem is that the calls to ruby with the package ruby installed now install the 1.9.1 version, but you only pull development files for ruby1.8. I've checked that it works changing from ruby to ruby1.8. You probably should try to use ruby1.9.1-dev at a later date. Cheers, Vincent ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#675972: gdal: FTBFS: fatal error: ruby.h: No such file or directory
tags 675972 + patch thanks Hi, On 04/06/12 21:14, Vincent Fourmond wrote: I've checked that it works changing from ruby to ruby1.8. You probably should try to use ruby1.9.1-dev at a later date. I'm not the maintainer, I was just asking. Thanks a lot for the help! Not tested this myself yet; I expect it to fix this on the buildds, but maybe it could still FTBFS on a system with ruby1.8 and ruby1.9.1 installed together. Then it might need an executable name or shebang line changing somewhere? --- a/debian/control +++ b/debian/control @@ -8,7 +8,7 @@ Build-Depends: debhelper (= 8), zlib1g-dev, libnetcdf-dev (= 1:4.0.0), libhdf4-alt-dev, libhdf5-serial-dev (= 1.6.6), libpq-dev, libxerces-c2-dev, unixodbc-dev (= 2.2.11), python-numpy, doxygen, d-shlibs, libgeos-dev, libmysqlclient-dev, python-all-dev (= 2.6.6-3~), libcurl4-gnutls-dev, libsqlite3-dev, libogdi3.2-dev, - ruby, ruby1.8-dev, chrpath, swig, patch, libexpat1-dev, libproj-dev, + ruby1.8, ruby1.8-dev, chrpath, swig, patch, libexpat1-dev, libproj-dev, libdap-dev, libxml2-dev, libspatialite-dev (= 2.4.0~rc2-4), libepsilon-dev (= 0.9.1), libpoppler-dev, liblzma-dev, libopenjpeg-dev, libarmadillo-dev, libfreexl-dev (= 1.0.0), libkml-dev, liburiparser-dev Regards, -- Steven Chamberlain ste...@pyro.eu.org ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#675972: gdal: FTBFS: fatal error: ruby.h: No such file or directory
On Mon, Jun 4, 2012 at 10:25 PM, Steven Chamberlain ste...@pyro.eu.org wrote: On 04/06/12 21:14, Vincent Fourmond wrote: I've checked that it works changing from ruby to ruby1.8. You probably should try to use ruby1.9.1-dev at a later date. I'm not the maintainer, I was just asking. Thanks a lot for the help! Not tested this myself yet; I expect it to fix this on the buildds, but maybe it could still FTBFS on a system with ruby1.8 and ruby1.9.1 installed together. Then it might need an executable name or shebang line changing somewhere? As far as I can tell, the package doesn't contain ruby scripts, only bindings. Dependencies will need to make sure ruby1.8 is used, though. (but there isn't ;-)...). Users will have to take care. Cheers, Vincent ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Processed: Re: Bug#675972: gdal: FTBFS: fatal error: ruby.h: No such file or directory
Processing commands for cont...@bugs.debian.org: tags 675972 + patch Bug #675972 [src:gdal] gdal: FTBFS: fatal error: ruby.h: No such file or directory Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 675972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#675972: gdal: FTBFS: fatal error: ruby.h: No such file or directory
On Mon, Jun 4, 2012 at 20:18:45 +0100, Steven Chamberlain wrote: Hi, Does gdal need an explicit Build-Depends: ruby1.8 instead of ruby; would that cause the buildscripts to pick the right include paths? I'd rather suggest removing gdal's ruby packages. They have no reverse deps in the archive anyway. Cheers, Julien signature.asc Description: Digital signature ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#675972: gdal: FTBFS: fatal error: ruby.h: No such file or directory
On Mon, Jun 4, 2012 at 22:33:42 +0200, Vincent Fourmond wrote: As far as I can tell, the package doesn't contain ruby scripts, only bindings. Dependencies will need to make sure ruby1.8 is used, though. (but there isn't ;-)...). Users will have to take care. That's entirely unacceptable. Cheers, Julien signature.asc Description: Digital signature ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
Bug#675972: gdal: FTBFS: fatal error: ruby.h: No such file or directory
On 04/06/12 21:42, Julien Cristau wrote: I'd rather suggest removing gdal's ruby packages. They have no reverse deps in the archive anyway. So if I understand this right, gdal only produces bindings for ruby1.8, which Ruby maintainers want to remove for Wheezy+1 anyway, and no packages in Wheezy are even using them. Therefore I agree. Changing the Build-Depends: ruby - ruby1.8 would fix the current FTBFS on buildds, but the existence of ruby1.9.1 would probably cause FTBFS on other systems. I've noticed this in the upstream changelog though: Ruby bindings: * Build SWIG Ruby Bindings against modern Ruby versions (1.8.7 and 1.9.2) (#3999) Regards, -- Steven Chamberlain ste...@pyro.eu.org ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
