On Wed, Oct 06, 2010, Neil Williams wrote:
> Non-standard build configuration - you'll need to discuss with upstream
> just how this is meant to support cross-compilation. Probably just have
> to patch the source to make this script truly cross-platform by having
> all the variables defined and selecting according to the
> dpkg-architecture environment variables.
Telling upstream that the fix is calling a Debian specific utility to
fix cross-builds is not going to work; but they could check some
triplet location
> .... a wdiff would have been a lot more helpful here. Exactly what
> changed on those long, long lines?
from amd64 to armel
[--DTCL_WIDE_INT_IS_LONG=1-] {+-DTCL_WIDE_INT_TYPE=long\ long
-DHAVE_STRUCT_STAT64=1 -DHAVE_OPEN64=1 -DHAVE_LSEEK64=1 -DHAVE_TYPE_OFF64_T=1+}
> Carrying build meta data inside a package is dumb. It's one thing to
> have libtool and Makefile hanging around in the source package, it's
> quite another to package something like config.h in the binary -dev
> package. That is what this -dev package is trying to do - include
> buildd meta-data into a runtime -dev package. That data needs to come
> from somewhere else, as with the pkg-config system, not from the -dev
> package.
Uh, pkg-config is exactly the same thing; it's fair enough to say they
should be using pkg-config, but they could as well dismiss their own
implementation as superior, or just dislike the pkg-config dep.
--
Loïc Minier
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
