Christian T. Steigies dixit:
>> I cross-built the kernels I ran for testing the patches, but that
>> was an exception ??? packages that I upload to Debian are *always*
>> built natively.
>
>Brave
No, it’s a must, clean build environment and native builds.
But I’m a BSD person so I’m used to slow boxen ;)
>I haven't used cowbuilder yet, for debian packages I us this, which I guess
>is equivalent to your cowbuilder script:
>DEB_HOST_ARCH=m68k debuild -B -am68k
No, debuild doesn’t create a clean chroot environment with
only the necessary build dependencies installed, and as such
your command, sorry, WILL produce broken packages.
Only cowbuilder, sbuild/buildd and pbuilder (which cowbuilder
is just the user-friendly, decent and fast wrapper around)
can produce “clean” packages. (And can be persuaded to cross-
compile at least binutils; gcc is possible too, easily because
it allows to create a “COW shell”, in which I can then do the
necessary steps.)
>Yes, but I am not trying to build a debian package, I try to build directly
>from linux-m68k.
Yeah but the last time I’ve done that was a one-off with
2.4.3-aa7-aa1-rwsem I think, before that 2.0.3x kernels…
>PS 2.6.28 did not boot: kernel too old. When was TLS introduced?
Much later, 2.6.32 got only a backport of it.
bye,
//mirabilos
--
If Harry Potter gets a splitting headache in his scar
when he’s near Tom Riddle (aka Voldemort),
does Tom get pain in the arse when Harry is near him?
-- me, wondering why it’s not Jerry Potter………
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
