On Sat, Mar 22, 2003 at 11:00:09PM +0100, Dimitri Chausson wrote:
> Hi,
>
> > The problems you've observed after moving ~/modules to /usr/src have
> > been fixed in the latest alsa-source package in unstable, so that's OK.
> >
> > This is the block of code that fills in the list between 'in' and ';'
> > when you do make-kpkg modules_image: (Formatted for reading)
> > (kernel-package 8.020, current testing version, unchanged in unstable
> > version 8.022)
>
> Ok, a good thing.
>
> As you can see in the following script output, even if I export
> $MODULE_LOC, it won't resolve the problem.
> I also executed tried the find, and it behaves correctly, so the '~'
> character is not the pb. The deb package I obtain is, as you can see, in
> the directory /root/modules/ and the name doesn't contain any own
> version information..
> So I think, that it's not the right behavior,
Umm, I said the latest version in Unstable... That hasn't propogated to
your machine yet...
[Trimmed /usr/share/doc/alsa-source/changelog.Debian.gz]
alsa-driver (0.9.0rc7-5) unstable; urgency=low
* Steve Kowalik:
- Alsa-source building:
+ Append $KDREV onto the package version. (Closes: #182147)
And you're only building 0.9.0rc7-2 according to the log.
Also, looking at your log, with MODULE_LOC set it seems to work,
apart from trying /root/modules as a module directory as well as
/root/modules/alsa-source... This is because you're using ~/modules
in your find line, but only the first one is expanded to
/root/modules... So the grep -v doesn't remove that line from the
output. Try exporting MODULE_LOC=/root/modules and see what happens.
From the output below, that should give you a correct build.
> Here the output:
(Trimmed again. :-)
> keats:/usr/src/linux# export MODULE_LOC="~/modules"
> keats:/usr/src/linux# find ~/modules -follow -maxdepth 1 -type d -print |grep -v '^~/modules$'
> /root/modules
> /root/modules/alsa-driver
That actually executed
find /root/modules -follow -maxdepth 1 -type d -print |grep -v '^~/modules$'
which is not correct, what you intended was
find /root/modules -follow -maxdepth 1 -type d -print |grep -v '^/root/modules$'
Or just avoid '~' in this situation.
> keats:/usr/src/linux# make-kpkg --revision=keats+1.5 modules_image
> for module in /root/modules /root/modules/alsa-driver ; do \
So it's finding your modules now.
> if test -d $module; then \
> (cd $module; \
> if ./debian/rules KVERS="2.4.20" KSRC="/usr/src/linux" \
> KMAINT="Dimitri Chausson" KEMAIL="tri2000@gmx.net" \
> KDREV="keats+1.5" kdist_image; then \
> echo "Module $module processed fine"; \
> else \
> echo "Module $module failed."; \
> echo "Hit return to Continue"; \
> read ans; \
> fi; \
> ); \
> fi; \
> done
This next three lines is due to the 'find' getting /root/modules as
a hit, and the 'grep -v' not filtering it.
> /bin/sh: line 1: ./debian/rules: No such file or directory
> Module /root/modules failed.
> Hit return to Continue
And after this point, it looks all right.
--
-----------------------------------------------------------
Paul "TBBle" Hampson, MCSE
6th year CompSci/Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
Paul.Hampson@Anu.edu.au
Of course Pacman didn't influence us as kids. If it did,
we'd be running around in darkened rooms, popping pills and
listening to repetitive music.
-- Kristian Wilson, Nintendo, Inc, 1989
This email is licensed to the recipient for non-commercial
use, duplication and distribution.
-----------------------------------------------------------
Attachment:
pgpqw0lKyBKAO.pgp
Description: PGP signature