On Mon, Nov 06, 2000 at 09:16:38AM -0500, Itai Zukerman wrote: > > The proposal makes perfect sense, I just have one concern: I see that > dpkg-buildpackage takes an architecture flag, but I don't think > there's a way to specify a "system type" (i386-hurd, for example). If > I want to put stuff in /usr/local, should I do i386-linuxlocal, and > how? I think it would be nice to: > > dpkg-buildpackage --system-type i386-linuxlocal > > (or something). And, if that's the case, probably the system type > should be part of the deb (the Architecture field)?
It's more complicated. Actually you can specifyu -ti386-gnu to dpkg-buildpackage, but it will be mapped to -ahurd-i386. The Debian Architecture system currently only allows a fixed number of *distinct* architectures. A rough proposal how to change this was written by me (which uses dependencies to reflect architecture requirements). I think it is a bad idea to confuse path's with GNU system types and architectures. It is entirely orthogonal. Please don't mix them up. i386-linuxlocal doesn't make any sense at all. The only connection is that sometimes to mix architectures (32/64 bit systems) you need to specify different default paths. > PS. I'm not very familiar with the build process, so maybe this makes > no sense. Also, is it possible to compile hurd packages on linux > build machines? You can sometimes cross compile (-ahurd-i386) if you have i386-gnu-gcc installed, a hurd partition with libs and headers mounted on /gnu, and the package is prepared for it. Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED] Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.marcus-brinkmann.de
