On Wed, Apr 12, 2000 at 09:18:30AM -0700, Jeff Bailey wrote:
> On Wed, Apr 12, 2000 at 04:01:21PM +0200, Marcus Brinkmann wrote:
>
> > It is currently in version 0.4, while 0.5 is being prepared. Beside
> > improving the source,
> > there is also the task of setting up a hurd machine as an autobuilder.
> > This is done in
> > parallel, and the only reason it is not currently running is that I
> > don't trust the
> > Hurd ext2fs server (it produces blocks of zero data in my files= :( ).
>
> Will turtle work with a cross-compiler?
It could easily (I just had to add a option to dpkg-buildpackage), and I
might add the necessary changes to it, but the autobuilder for the Debian
GNU/Hurd will not be (is not) a cross compilation environment, but a
native machine.
Many, many Debian packages can't be cross build. Not everyone uses autoconf,
and not everyone uses it correctly :)
> I've almost finished setting up
> my automated cross-builds for libc and the Hurd (OSKit still doesn't love
> me), and I was thinking that it would be lovely to add a couple of other
> things like Gcc snapshots. I'm produce them in .tar.gz files now, but if
> this thing can deal with making the .deb's for me that would be lovely.
Well, creating debs is not difficult in a Debian environment (having
dpkg-dev installed it is easy). However, I assume you build from CVS, and
automatically creating snapshots from CVS in Debian format is non-trivial.
(And requires manual preperation for each package).
Turtle works with the Debian source archive, and only compiles source
packages that were uploaded by Debian developers.
This is not a severe limitation, as it is a rule that Debian packages
should be compiled on an up-to-date Debian machine, using only Debian
packages. However, turtle is extensible by its group mechanism, and you
could easily write your automated cross builds as a perl group in Turtle,
and thus have a combined autobuilder. (If you are interested, we can talk
about it in more detail).
BTW, OSKit needs a compiler which defines __ELF__, so make sure your gcc
does it (the Debian gcc currently doesn't), or add it to your specs file.
To illustrate, here is what turtle is doing right now:
Processing package `groff'.
Processing package `groff' version `1.15-3.ja.3'
Calling `install_source' for groff (1.15-3.ja.3).
Error processing package `groff':
dpkg-source errno=512 at /usr/local/lib/site_perl/Turtle/Lock.pm line 443
at /usr/local/lib/site_perl/Turtle/Group/Debian/Version.pm line 438
at /usr/local/lib/site_perl/Turtle/Group/Debian/Version.pm line 383
at /usr/local/lib/site_perl/Turtle/Group/Debian/Version.pm line 591
at /usr/local/lib/site_perl/Turtle/Group/Debian/Version.pm line 510
Processing package `grub'.
Processing package `grub' version `0.5.94'
Calling `install_source' for grub (0.5.94).
Calling `build_package' for grub (0.5.94).
Calling `send_notification' for grub (0.5.94).
Processing package `guile-core'.
Skipping binary-all package `guile-core'.
Processing package `hello'.
Skipping up-to-date package `hello'.
Processing package `hello-debhelper'.
Skipping up-to-date package `hello-debhelper'.
Processing package `jed'.
Processing package `jed' version `0.99.9-14'
Calling `install_source' for jed (0.99.9-14).
Calling `build_package' for jed (0.99.9-14).
Thanks,
Marcus
