[DebianGIS-dev] OpenMPI support for hdf FTBFS on several arches
The OpenMPI support recently introduced in hdf5 has made the package FTBFS on several arches (arm, armel, hppa, mips, mipsel, and s390), because openmpi also FTBFS on them. I think you should disable the build of libhdf5-openmpi for those architectures. This is a highly important issue, because hdf5 will prevent the transition of octave3.0 into testing, which is part of the complex suitesparse transition [1]. If you think I should file a bug report about this, please tell me. [1] http://www.nabble.com/Suitesparse-transition-to16153452.html -- Rafael ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#473328: hdf5: Drop openmpi support on some architectures
Package: hdf5 Version: 1.6.6-1 Severity: important The OpenMPI support recently introduced in hdf5 has made the package FTBFS on several arches (arm, armel, hppa, mips, mipsel, and s390), because openmpi also FTBFS on them. Please, disable the build of libhdf5-openmpi for those architectures. This is a highly important issue, because hdf5 will prevent the transition of octave3.0 into testing, which is part of the complex suitesparse transition [1]. [1] http://www.nabble.com/Suitesparse-transition-to16153452.html -- Rafael ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#473328: hdf5: Drop openmpi support on some architectures
* Rafael Laboissiere <[EMAIL PROTECTED]> [2008-03-30 11:13]: > package hdf5 > severity 473328 serious > thanks > > Following a suggestion of Steve Langasek [1], I am raising the severity of > this bug report to "serious". > > R. > > [1] With the link this time: [1] http://www.nabble.com/Re%3A-OpenMPI-support-for-hdf-FTBFS-on-several-arches-p16376387.html -- Rafael ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#473328: hdf5: Drop openmpi support on some architectures
package hdf5 tags 473328 patch thanks Attached below is a patch for disabling the building of libhdf5-openmpi-* packages on some problematic architectures. Note that I did not take the approach of adding an Architecture field for the libhdf5-openmpi-* package stanzas in debian/control.in. Instead this file is filtered through slice before generating the final debian/control. In debian/rules, conditional compilation is managed using new variables. Please, consider fixing this bug in a timely manner. If you wish, I could NMU the package. Regards, -- Rafael Index: debian/control.in === --- debian/control.in (revision 1487) +++ debian/control.in (working copy) @@ -3,7 +3,7 @@ Priority: optional Maintainer: Debian GIS Project Uploaders: Francesco Paolo Lovergine <[EMAIL PROTECTED]> -Build-Depends: libmpich1.0-dev (>= 1.2.7-1), zlib1g-dev, lam4-dev (>= 7.1.1-3.2), libopenmpi-dev, libjpeg62-dev, debhelper (>> 5) +Build-Depends: libmpich1.0-dev (>= 1.2.7-1), zlib1g-dev, lam4-dev (>= 7.1.1-3.2), libopenmpi-dev [!arm !armel !hppa !mips !mipsel !s390], libjpeg62-dev, debhelper (>> 5), slice Standards-Version: 3.7.3 Homepage: http://hdf.ncsa.uiuc.edu/HDF5/ Vcs-Browser: http://svn.debian.org/viewsvn/pkg-grass/packages/hdf5/trunk/ @@ -69,6 +69,7 @@ . This package contains development files for use with LAM. +[OPENMPI: Package: [EMAIL PROTECTED]@-0 Section: libs Priority: extra @@ -99,6 +100,7 @@ files larger than 2 GB, and supports parallel I/O. . This package contains development files for use with OpenMPI. +:] Package: [EMAIL PROTECTED]@-0 Section: libs Index: debian/changelog === --- debian/changelog (revision 1487) +++ debian/changelog (working copy) @@ -1,9 +1,15 @@ hdf5 (1.6.6-2) UNRELEASED; urgency=low + [ Francesco Paolo Lovergine ] * Fixed changelog due to patch dropped before release, but still logged. - -- Francesco Paolo Lovergine <[EMAIL PROTECTED]> Thu, 20 Mar 2008 12:55:54 +0100 + [ Rafael Laboissiere ] + * NMU + * Do not create the libdhf5-openmpi-* packages on some selected +architectures (closes: #473328) + -- Rafael Laboissiere <[EMAIL PROTECTED]> Mon, 31 Mar 2008 02:48:15 +0200 + hdf5 (1.6.6-1) unstable; urgency=low [ Francesco Paolo Lovergine ] Index: debian/rules === --- debian/rules (revision 1487) +++ debian/rules (working copy) @@ -18,7 +18,36 @@ DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH) +ifeq ($(DEB_BUILD_ARCH),arm) +build_openmpi = no +else ifeq ($(DEB_BUILD_ARCH),armel) +build_openmpi = no +else ifeq ($(DEB_BUILD_ARCH),hppa) +build_openmpi = no +else ifeq ($(DEB_BUILD_ARCH),mips) +build_openmpi = no +else ifeq ($(DEB_BUILD_ARCH),mipsel) +build_openmpi = no +else ifeq ($(DEB_BUILD_ARCH),s390) +build_openmpi = no +else +build_openmpi = yes +endif + +ifeq ($(build_openmpi),yes) +sliceterm = UNDEF+OPENMPI +configure_stamp_openmpi = configure-stamp-openmpi +build_stamp_openmpi = build-stamp-openmpi +install_openmpi = install-openmpi +else +sliceterm = UNDEF +configure_stamp_openmpi = +build_stamp_openmpi = +install_openmpi = +endif + ifeq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) USE_PROD = yes else @@ -49,7 +78,7 @@ --enable-shared --enable-production=$(USE_PROD) -configure: configure-stamp-debian configure-stamp-serial configure-stamp-lam configure-stamp-openmpi configure-stamp-mpich +configure: configure-stamp-debian configure-stamp-serial configure-stamp-lam $(configure_stamp_openmpi) configure-stamp-mpich configure-stamp-debian: debian/control.in cd debian && for i in *_devlib; do j=`basename $$i _devlib`; \ @@ -107,7 +136,7 @@ --enable-parallel=yes touch configure-stamp-mpich -build: build-stamp-serial build-stamp-lam build-stamp-openmpi build-stamp-mpich +build: build-stamp-serial build-stamp-lam $(build_stamp_openmpi) build-stamp-mpich build-stamp-serial: configure-stamp-serial dh_testdir @@ -137,7 +166,8 @@ -rm -rf debian/build-openmpi -rm -rf debian/build-mpich -find debian -type l | xargs rm -f - grep -v ^\% debian/control.in | sed "s/@VERSION@/$(version)/g" > debian/control + grep -v ^\% debian/control.in | sed "s/@VERSION@/$(version)/g" \ + | slice -o$(sliceterm):debian/control dh_clean configure-stamp* build-stamp* install-stamp* debian/*.shlibs install: install-serial install-lam install-openmpi install-mpich install-doc @@ -191,7 +221,7 @@ dh_md5sums -i dh_builddeb -i -binary-arch: build install-serial install-lam install-openmpi install-mpich +binary-arch: build install-serial install-lam $(install_openmpi) install-mpich dh_testdir
[DebianGIS-dev] Bug#473328: hdf5: Drop openmpi support on some architectures
* Bastian Blank <[EMAIL PROTECTED]> [2008-03-31 11:27]: > On Mon, Mar 31, 2008 at 03:41:11AM +0200, Rafael Laboissiere wrote: > > Note that I did not take the approach of adding an Architecture field for > > the libhdf5-openmpi-* package stanzas in debian/control.in. Instead this > > file is filtered through slice before generating the final debian/control. > > The amount and names of packages included in the control file must not > change during the build. If you do that, you have to abort the build. I did not know that. Is that written somewhere in the Policy? -- Rafael ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#473669: hdf5: OpenMPI support still failing
Package: hdf5 Version: 1.6.6-2 Severity: serious Tags: patch Justification: FTBFS The fix in 1.6.6-2 was not enough, the buildds on hppa, mips, and mipsel failed with: dh_gencontrol -a dpkg-gencontrol: error: current host architecture 'hppa' does not appear in package's architecture list (alpha amd64 i386 ia64 powerpc sparc kfreebsd-i386 kfreebsd-amd64) dh_gencontrol: command returned error code 65280 make: *** [binary-arch] Error 1 The patch attached below should fix the problem. Thanks R. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Index: debian/rules === --- debian/rules (revision 1490) +++ debian/rules (working copy) @@ -221,20 +221,20 @@ binary-arch: build install-serial install-lam $(install-openmpi) install-mpich dh_testdir dh_testroot - dh_installdocs -a - dh_installman -a - dh_installchangelogs -a -k release_docs/RELEASE.txt - dh_link -a - dh_strip -a - dh_compress -a - dh_fixperms -a + dh_installdocs -s + dh_installman -s + dh_installchangelogs -s -k release_docs/RELEASE.txt + dh_link -s + dh_strip -s + dh_compress -s + dh_fixperms -s # dh_makeshlibs -p$(serpack) -V "$(serpack) | $(virtpack)" dh_makeshlibs -p$(lampack) -V $(lampack) ifeq ($(build_openmpi),yes) dh_makeshlibs -p$(openmpipack) -V $(openmpipack) endif dh_makeshlibs -p$(mpichpack) -V $(mpichpack) - dh_installdeb -a + dh_installdeb -s dh_shlibdeps -phdf5-tools -L$(serpack) -ldebian/$(serpack)/usr/lib:debian/build-serial/test/.libs dh_shlibdeps -p$(serpack) -L$(serpack) -ldebian/$(serpack)/usr/lib:debian/build-serial/test/.libs dh_shlibdeps -p$(lampack) -L$(lampack) -ldebian/$(lampack)/usr/lib @@ -242,9 +242,9 @@ dh_shlibdeps -p$(openmpipack) -L$(openmpipack) -ldebian/$(openmpipack)/usr/lib endif dh_shlibdeps -p$(mpichpack) -L$(mpichpack) -ldebian/$(mpichpack)/usr/lib - dh_gencontrol -a - dh_md5sums -a - dh_builddeb -a + dh_gencontrol -s + dh_md5sums -s + dh_builddeb -s binary: binary-indep binary-arch ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#473871: hdf5: Doesn't actually build openmpi libs
* Francesco P. Lovergine <[EMAIL PROTECTED]> [2008-04-02 10:21]: > On Tue, Apr 01, 2008 at 11:13:16PM -0400, Adam C Powell IV wrote: > > Package: hdf5 > > Version: 1.6.6-3 > > > > Greetings, > > > > I'm afraid your rules file doesn't build openmpi libraries on the > > architectures where it's supposed to, so the openmpi packages are empty. > [snip] > > I don't like that so much because OpenMPI detection should be done > without using paths which could be subject to changes due to > other maintainers' choices :-/ > I'll try to find out why it does not work properly and how manage > better the issue. It was my fault, sorry. I used hyphens instead of underscores in the variable names in debian/rules. The patch attached below should fix it. Thanks, -- Rafael Index: debian/rules === --- debian/rules (revision 1493) +++ debian/rules (working copy) @@ -80,7 +80,7 @@ --enable-shared --enable-production=$(USE_PROD) -configure: configure-stamp-debian configure-stamp-serial configure-stamp-lam $(configure-stamp-openmpi) configure-stamp-mpich +configure: configure-stamp-debian configure-stamp-serial configure-stamp-lam $(configure_stamp_openmpi) configure-stamp-mpich configure-stamp-debian: debian/control.in cd debian && for i in *_devlib; do j=`basename $$i _devlib`; \ @@ -138,7 +138,7 @@ --enable-parallel=yes touch configure-stamp-mpich -build: build-stamp-serial build-stamp-lam $(build-stamp-openmpi) build-stamp-mpich +build: build-stamp-serial build-stamp-lam $(build_stamp_openmpi) build-stamp-mpich build-stamp-serial: configure-stamp-serial dh_testdir @@ -171,7 +171,7 @@ grep -v ^\% debian/control.in | sed "s/@VERSION@/$(version)/g" > debian/control dh_clean configure-stamp* build-stamp* install-stamp* debian/*.shlibs -install: install-serial install-lam install-openmpi install-mpich install-doc +install: install-serial install-lam $(install_openmpi) install-mpich install-doc install-serial: build-stamp-serial dh_testdir @@ -222,7 +222,7 @@ dh_md5sums -i dh_builddeb -i -binary-arch: build install-serial install-lam $(install-openmpi) install-mpich +binary-arch: build install-serial install-lam $(install_openmpi) install-mpich dh_testdir dh_testroot dh_installdocs $(ARCH_FLAG) ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#474051: libhdf5-serial-dev: libhdf5 appears to write uninitialized memory to file
* Jason Kraftcheck <[EMAIL PROTECTED]> [2008-04-02 19:04]: > Package: libhdf5-serial-dev > Version: 1.6.5-3 > Severity: grave > Tags: security > Justification: user security hole > > > valgrind reports writes of unitialized memory in hdf5 library. This > could be a serious security issue, depending on what that memory > contains. This can be reproduced by running almost any application > (that uses the library to write a file) in valigrind. > > The valgrind error message is: > > ==29786== Memcheck, a memory error detector. > ==29786== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. > ==29786== Using LibVEX rev 1804, a library for dynamic binary translation. > ==29786== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. > ==29786== Using valgrind-3.3.0-Debian, a dynamic binary instrumentation > framework. > ==29786== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. > ==29786== For more details, rerun with: -v > ==29786== > ==29786== Syscall param write(buf) points to uninitialised byte(s) > ==29786==at 0x51119F0: __write_nocancel (in /usr/lib/debug/libc-2.7.so) > ==29786==by 0x4E83FCD: (within /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E757DF: H5FD_flush (in /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E6E14A: (within /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E6F7B2: H5F_try_close (in /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E6F9BB: (within /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E9B313: H5I_dec_ref (in /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E6D880: H5Fclose (in /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x400AEE: main (hdf5_bug.c:22) > ==29786== Address 0x5add820 is 440 bytes inside a block of size 1,864 alloc'd > ==29786==at 0x4C21FAB: malloc (vg_replace_malloc.c:207) > ==29786==by 0x4E87873: (within /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E87E05: H5FL_blk_malloc (in > /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E883A3: H5FL_blk_realloc (in > /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E75D9F: H5FD_write (in /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E6C9A1: H5F_block_write (in > /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4EA05EA: (within /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E505B0: (within /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E51826: H5C_flush_cache (in > /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E4C16E: H5AC_flush (in /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E6DF8C: (within /usr/lib/libhdf5-1.6.5.so.0.0.0) > ==29786==by 0x4E6F7B2: H5F_try_close (in /usr/lib/libhdf5-1.6.5.so.0.0.0) I cannot reproduce the problem above with libhdf5-serial-1.6.6, version 1.6.6-4 (currently in unstable). Using the C program that you provided, I get the following output from valgrind: ==11598== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 8 from 1) ==11598== malloc/free: in use at exit: 1,312 bytes in 2 blocks. ==11598== malloc/free: 1,014 allocs, 1,012 frees, 494,404 bytes allocated. ==11598== For counts of detected errors, rerun with: -v ==11598== searching for pointers to 2 not-freed blocks. ==11598== checked 142,048 bytes. ==11598== ==11598== LEAK SUMMARY: ==11598==definitely lost: 0 bytes in 0 blocks. ==11598== possibly lost: 0 bytes in 0 blocks. ==11598==still reachable: 1,312 bytes in 2 blocks. ==11598== suppressed: 0 bytes in 0 blocks. Could you please confirm this? -- Rafael ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#516453: Bug#516453: h5utils: Please switch to octave3.0
* Rafael Laboissiere [2009-02-28 11:25]: > * Rafael Laboissiere [2009-02-23 23:41]: > > > * Francesco P. Lovergine [2009-02-23 23:01]: > > > > > Thanks, did you consider to forward the configure.in patch upstream? > > > > No. It is perhaps better if you do it, as the package maintainer? > > Did you do it, or do you prefer that I do it myself. > > Another question: Bug#516453 (h5utils: Please switch to octave3.0) is > currently the only blocker of our removal request for octave2.1. Are you > planning to upload a fixed package soon. If you wish, I can do an NMU and > commit the changes to the SVN repository of pkg-grass. If you do not object, I will NMU soon a fixed h5utils package, such that octave2.1 can be removed from unstable (see Bug#516402). Thanks, -- Rafael ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#516453: Bug#516453: Bug#516453: h5utils: Please switch to octave3.0
* Francesco P. Lovergine [2009-03-09 22:30]: > Feel free to NMU if urgent for you, HDF4 and HDF5 need care before updating > h5utils to 1.11.1, so this package will not be updated any time soon. Done, thanks. -- Rafael ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
Bug#667063: h5utils: Adjust for the new octave package version 3.6.1
Package: src:h5utils Version: 1.12.1-1 Severity: important The current version of h5utils build-depends on octave3.2-headers. This later package will be removed from unstable once the transition to the new version of octave (currently 3.6.1) will be completed (see the wiki page of the DOG [1]). Simply changing the build-dependency from octave3.2-headers to liboctave-dev fixes the issue. Two additional comments, that are not really related to the bug reported here but are worth mentioning (tell me if you prefer that I file separated bug reports for the points below): 1) You might add "Suggests: octave" to h5utils. This would give an indication to the users that there is an Octave plugin included in the package. 2) On my i386 system, the h5read.oct file is installed in: /usr/lib/i386-linux-gnu/octave/3.6.1/site/oct/i486-pc-linux-gnu/ Notice that this is a versioned path. This means that the script will not be in the Octave path if the octave package is upgraded upstream (unless the user explicitly include it via addpath). Actually, the directory above is reserved for the pristine Octave files, not really appropriate for plugins. This path is obtained by the following code in configure.ac: OCT_INSTALL_DIR=`octave-config --oct-site-dir Plugins should be installed in one of the following paths (the example below is shown is for the i386 architeture): $ octave-config --print LOCALOCTFILEDIR /usr/lib/i386-linux-gnu/octave/site/oct/i486-pc-linux-gnu $ octave-config --print LOCALAPIOCTFILEDIR /usr/lib/i386-linux-gnu/octave/site/oct/api-v48+/i486-pc-linux-gnu Note that the last one has the API number, which may be (or not) a good thing. Rafael [1] http://wiki.debian.org/Teams/DebianOctaveGroup -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (650, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Rafael ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
[DebianGIS-dev] Bug#422537: [Pkg-jed-sl-modules] Bug#422537: cfitsio3: GPL/PD but includes GPL compress.c from gzip
* Aurelien Jarno <[EMAIL PROTECTED]> [2007-05-07 00:07]: > reassign 422537 libcfitsio2, slang-cfitsio, libgdal1-1.3.2 > thanks > > On Sun, May 06, 2007 at 03:37:00PM -0400, Justin Pryzby wrote: > > Package: libcfitsio2, libcfitsio3, slang-cfitsio, libgdal1-1.3.2 > > # apt-cache rdepends output > > # kst-plugins is gpl > > # fv is written by the same guy as fitsio so.. > > > > The debian/copyright file has been feixed is cfitsio3 3.040-1. I am > therefore reassigning the bugs to the remaining packages. Could you please tell me what should be changed in the slang-cfitsio package in order to close this bug report? Thanks, -- Rafael ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel
Bug#734047: octave-gmt: Use unversioned paths for installting the Octave files
Package: octave-gmt Version: 4.5.11-1 Severity: normal Tags: patch Please, use an unversioned path for installing the *.m and *.mex files provided in this package. This will avoid breaking your package when the octave package is updated. The patch attached below fixes this problem. Note also that this patch creates private directories for the Octave files, which is the common practice for packages providing add-ons for Octave in Debian. Best, Rafael Laboissiere -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (550, 'stable'), (500, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.10-rc7-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash >From 36f994bd6b51cae572a89676d2a1aae82d781407 Mon Sep 17 00:00:00 2001 From: Rafael Laboissiere Date: Fri, 3 Jan 2014 04:34:52 +0100 Subject: [PATCH] Use unsversioned paths for installing the Octave files Furthermore, the files are now installed into private directories */gmt/. --- debian/rules | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/rules b/debian/rules index 8b29265..40c6ecd 100755 --- a/debian/rules +++ b/debian/rules @@ -38,8 +38,8 @@ build-stamp: $(CURDIR)/configure \ --enable-shared $(PATHCONFIG) --disable-mex --enable-netcdf=/usr \ --enable-octave \ - --enable-mex-mdir=$(shell octave-config --m-site-dir) \ - --enable-mex-xdir=$(shell octave-config --oct-site-dir) + --enable-mex-mdir=$(shell octave-config -p LOCALFCNFILEDIR)/gmt \ + --enable-mex-xdir=$(shell octave-config -p LOCALOCTFILEDIR)/gmt $(MAKE) CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)" all suppl touch $@ -- 1.8.5.2 ___ Pkg-grass-devel mailing list Pkg-grass-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
