Package: dpkg-dev Version: 1.10.18 Severity: normal I was building mplayer on my ultrasparc from a debian repo I use on x86. I used there sourcepkgs, not sparc aware. I found mysellf using 'sparc32 dpkg-buildpackage' alot and I wondered why dpkg-buildpackage didn't know when to use 64 or 32. ppl say to use 32bit for sparc, unless there is need for 64. If there was need for 64 or even a working 64bit build. Then I would expect special care needed to be taken to facilitate this.
Also I don't know how libs are to be built on a dual bit system. I would hope that dpkg would build both sets of libs if needed. I posted the results at "http://www.technofoundry.com/~cheako/"; and touched sparc32 in the output dirs where I needed to use it. The full build dirs can also be found there. -- System Information: Debian Release: testing/unstable Architecture: sparc Kernel: Linux train 2.6.0-test11 #1 Wed Dec 31 00:10:05 CST 2003 sparc64 Locale: LANG=C, LC_CTYPE=C Versions of packages dpkg-dev depends on: ii binutils 2.14.90.0.7-3 The GNU assembler, linker and bina ii cpio 2.5-1.1 GNU cpio -- a program to manage ar ii make 3.80-4 The GNU version of the "make" util ii patch 2.5.9-1 Apply a diff file to an original ii perl [perl5] 5.8.2-2 Larry Wall's Practical Extraction ii perl-modules 5.8.2-2 Core Perl modules. -- no debconf information
