Florian Lohoff wrote:
On Tue, Apr 03, 2001 at 12:22:48AM +0200, Kevin D. Kissell wrote:
I'm not sure exactly what you mean here. That no one would
consider using your Debian cross environment? That no one
I am not building cross, i am not building the debian cross
toolchain. Just for completeness.
would consider doing cross-development? What part of it
seems to you to be a show-stopper?
A major problem get the thing in which the configure try to
begin to build executables and guess on the behaviour of the
OS to run on. This ends to be a hack and reminds me on
"pre gnu configure" times where one had to deal
with hundrets of "config.h" or "os.h" files.
Perfect it is not, but it's not nearly _that_ bad either. I would say 40% of the RPMs
I've tried will configure out of the box for a cross build. Another 40% or so require a
few "export ac_cv_sizeof_long=4" kind of settings to configure for a cross
build. The remaining 20% are painful.
Most of the package maintainers have been very receptive to configuration help for cross build environments. Of course some seem to have died or gone to work for Microsoft (is there a measurable difference?).
If you are going to use anything like a package format
might it be "rpm" or "deb" the dependencies tend to be
utterly broken as the dependcies are guessed by stuff like
"ldd" output and friends.
You can of course specify the target to rpm when unpacking the source...
If you have a 90Meg source tarball and build a 4Meg Ramdisk
for a Nino out of it. Fine.
Of course you could compile the packages natively on the Nino on a NFS mount
over serial-ppp... ;)