Why dpkg is linux-centric?

[Piotr_Roszatycki@internetia.pl (Piotr Roszatycki)]

I've tried compile dpkg on freebsd and atheos. Unfortunately, dpkg is 
linux-centric.

I.e. dpkg requires gcc. I think dpkg should fallback to compile-time defaults.

dexter@sawa:/backup0/home/dexter/tmp/dpkg/main> ./dpkg --print-architecture
dpkg: unexpected output from `gcc --print-libgcc-file-name':
 `/usr/lib/libgcc.a'
 dpkg: compiler libgcc filename not understood: no gcc-lib component
 
The default should be:

dexter@sawa:/backup0/home/dexter/tmp/dpkg/main> ./dpkg --print-installation-architecture
freebsd-i386

Another point - start-stop-daemon:

gcc -D_GNU_SOURCE  -I../optlib -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I../intl -I../intl -I../include -I.. -I. -I../include -I.. -I. -c start-stop-daemon.c
start-stop-daemon.c:27: #error Unknown architecture - cannot build start-stop-daemon
gmake[1]: *** [start-stop-daemon.o] Error 1

I'd like to see ./configure --without-start-stop-daemon (fortunately
--without-dselect works).

I've included line to archtable:
i386-freebsd4.0         freebsd-i386    undefined

Unfortunately, I should include entry for each release (freebsd4.1, etc.).
I think archtable could search substring (*i386-freebsd*).

config.guess doesn't detect atheos, but it isn't problem as far as we have
./configure --host= option. Another idea, if system isn't detected, we can
find it by 'uname'.

I'd like to fixup these problems. Can I send some patches?

-- 
Piotr Roszatycki, SD Specialist, InterNetia Telekom     .''`.
mailto:Piotr_Roszatycki@internetia.pl                  : :' :
mailto:dexter@debian.org                               `. `'
                                                         `-