And on first test after letting libgpg-error, libgcrypt and cryptsetup back in the build, they just worked "out of the hat" so they are back on. And with autogen working, so is the new version of re2c for building ninja. So there is just grub2 to go, and the autogen templates to add and 20-~ is complete.

On 11/03/20 16:08, scsijon wrote:
OK, a new packageset for autogen, a diff for autogen.desc and a needed autogen.conf to suit.

You need the guile2 package though as autogen wants guile v2.x.x and not guile v3.0.x, so I'm also attaching the guile2.desc and guile2.cache, you need to create a package/develop/guile2 directory and put them in it, it seems to build happily. It's an old T2 revision guile from before the V3, just renamed and tested.

Autogen will then build happily, and work generally, although there are a couple of templates ocasionally needed, see the .conf for details off what's missing to have them build, I just haven't worked out how/where to put the setting yet is all.

And I have a working 20-minimal build with kmod/udev, except for grub2, libgpg-error, libgcrypt and cryptsetup, which I haven't worried about up to this point. Since we don't use grub2, i'm not worrying about that, and i'll look at the others soon. My other build system with kmod/eudev is still a work-in-progress, but should happily move forward now I have a working autogen.

Since I am still at r49158 modified I think I will supply a 10-~ and 20-~ updated files, a copy off my packages file, and a svn diff as an interim step, so others can compare what they have with the settings I am using, there are a 'few' changes. When I get the last few mentioned above sorted out, I will start to move them to a later revision T2 dataset.

regards to all
scsijon

-------- Forwarded Message --------
Subject: Re: [t2] autogen and 'gufff'
Date: Wed, 11 Mar 2020 08:46:14 +1100
From: scsijon <[email protected]>
To: [email protected]

as promised a new autogen at 5.18.16

On 10/03/20 14:16, scsijon wrote:

I've found an even later autogen source release on Debian's site, I shall add another diff when I get it all sorted out this evening. I'm testing a build of the cuurrent update now. Had to add and change a few stage settings though to start it.

On 09/03/20 13:51, scsijon wrote:
I found our autogen is out of date, i've attached a patch, but haven't tried it out yet, the other T2 dev box is busy  at prep for a 40-~ test build, the kmod-eudev awa its a response on the auutogen problem!

btw, i've sucessfully built a 20-minimal on the kmod-udev machine at last, although at r49158(mod6), not your latest revision. I'll see how the autogen update goes first on a rebuild before extracting a svn diff and starting on a fresh T2 svn download.

?I wonder what would happen if we used mdev, i've never tried it but some systems work quite happily. Especially if we added toybox, as Rob Landley did write mdev for Busybox before moving on, so I would expect that it would be an updated and expanded version in toybox.

I've already got a commit off him to add the last two missing commands (insmod, rmmod, lsmod, modinfo, libkmod are already there), modprobe & depmod are not, into toybox, that would mean 'kmod / module-init-tools / $equiv' shouldn't be needed too.

regards
scsijon

On 09/03/20 09:01, scsijon wrote:
Rene, is there a problem with autogen? I can run it, but it only runs by itself, it ignores any added 'var_append confopt " " " " statements.

Attached is my first testrun eudev.conf which needs them. I can't see anything seriously wrong in the code (except possibly my extraneous notes), but it just won't work. It tries to run it as if the only thing in the eudev.conf is the autogen=1 line!

I've added the .desc in case you want to try it out, but beware as it's not finished yet.

thanks
scsijon



----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2





----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to