On Wed, Jul 8, 2009 at 10:39 AM, George Danchev<[email protected]> wrote: > Quoting Mathieu Malaterre <[email protected]>: > >> [Sorry I was not subscribed when I got the answer from George Danchev] >> >> So anyway I tried the --same-arch flag and it *seems* to be working on >> alpha (there is no log reporting failure), but it clearly does not >> work on armel: >> >> Here is a copy of the control file: >> >> ... >> Package: libgdcm-cil >> Section: cli-mono >> Architecture: i386 lpia kfreebsd-i386 powerpc amd64 kfreebsd-amd64 >> ia64 arm armeb sparc s390 > > you still have armel specified in the architecture of libvtkgdcm-cil package > section, while you don't have alpha listed for anywhere, that's why is > worked for alpha, but not for armel.
It did not worked for alpha... https://buildd.debian.org/fetch.cgi?pkg=gdcm;ver=2.0.12-3;arch=alpha;stamp=1247121765 dh_install --sourcedir=/build/buildd-gdcm_2.0.12-3-alpha-sCffwM/gdcm-2.0.12/debian/tmp --same-arch --fail-missing cp: cannot stat `/build/buildd-gdcm_2.0.12-3-alpha-sCffwM/gdcm-2.0.12/debian/tmp/usr/lib/gdcm-sharp.dll': No such file or directory dh_install: cp returned exit code 1 make[1]: *** [binary-common] Error 1 make[1]: Leaving directory `/build/buildd-gdcm_2.0.12-3-alpha-sCffwM/gdcm-2.0.12' make: *** [binary-arch] Error 2 -- Mathieu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
