On Fri, Oct 26, 2012 at 12:35:06AM -0400, Asheesh Laroia wrote: > I just tried to build my debdiff and do an NMU, and it ends with > this message: > > Finished tests in 0.001844s, 2711.3306 tests/s, 15725.7175 assertions/s. > > 5 tests, 29 assertions, 0 failures, 0 errors, 0 skips > make[1]: Leaving directory `/tmp/buildd/rhash-1.2.9/bindings' > /usr/bin/make -C bindings build > LIBRHASH_INC="-I/tmp/buildd/rhash-1.2.9/debian/tmp" > LIBRHASH_LD="-Wl,--as-needed -L/tmp/buildd/rhash-1.2.9/debian/tmp" > BINDINGS="mono" > make[1]: Entering directory `/tmp/buildd/rhash-1.2.9/bindings' > make -C mono > make[2]: Entering directory `/tmp/buildd/rhash-1.2.9/bindings/mono' > gmcs -target:library -define:UNIX -out:RHash.dll -debug > -keyfile:RHash.snk AssemblyInfo.cs Bindings.cs Hasher.cs HashType.cs > make[2]: gmcs: Command not found > make[2]: *** [RHash.dll] Error 127 > make[2]: Leaving directory `/tmp/buildd/rhash-1.2.9/bindings/mono' > make[1]: *** [build-mono] Error 2 > make[1]: Leaving directory `/tmp/buildd/rhash-1.2.9/bindings' > make: *** [build-indep] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > E: Failed autobuilding of package > I: unmounting dev/pts filesystem > I: unmounting proc filesystem > I: cleaning the build env > I: removing directory /var/cache/pbuilder/build//16252 and its > subdirectories > > ...why is gmcs not findable in my pbuilder chroot? I checked, and > mono-gmcs is still a dependency. Yeah, I've seen that too. mono-gmcs was not installed by pbuilder even though it's in the deps, but "mono-gmcs (>= 1.1.8) | c-sharp-2.0-compiler" dep was apparently resolved by mono-devel pulled by other deps (actually I don't know whether pbuilder dep resolution works that way or there is something else happening here).
-- WBR, wRAR
signature.asc
Description: Digital signature
