Hi,
I try to build a kernel module (legousbtower to get Lego Mindstorm with
USB working). I builded a module-source package and tried
fakeroot make-kpkg modules_image
This process stops by
config.status: creating Makefile
sed: file ./confstatnlBJkF/subs-1.sed line 47: Unterminated `s' command
sed: file ./confstatnlBJkF/subs-2.sed line 11: Unterminated `s' command
The reason is the following: If I call ./configure in the build
directory all works fine. But make-kpkg calls configure from out
of a makefile. Make has the behaviour to print
make: Entering directory `/u/gnu/make'
which might be switched of by the --no-print-directory option but I
have no idea how to birng this in into make-kpkg. This behaviour of make
results in the following difference:
( "<" called from make-kpkg, ">" called from /bin/sh )
< checking for kernel compile parameters... make[3]: Entering directory
`/usr/src/l
inux-2.4.23'
< gcc
< make[3]: Leaving directory `/usr/src/linux-2.4.23' make[3]: Entering
directory `/
usr/src/linux-2.4.23'
< -D__KERNEL__ -I/usr/src/linux-2.4.23/include -Wall -Wstrict-prototypes
-Wno-trigr
aphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe
-mpreferred-st
ack-boundary=2 -march=athlon -DMODULE -DMODVERSIONS -include
/usr/src/linux-2.4.23/
include/linux/modversions.h
< make[3]: Leaving directory `/usr/src/linux-2.4.23'
---
> checking for kernel compile parameters... gcc -D__KERNEL__
> -I/usr/src/linux-2.4.2
3/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-co
mmon -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon
-DMODULE
-DMODVERSIONS -include /usr/src/linux-2.4.23/include/linux/modversions.h
The result is a broken sed line which looks like this:
[EMAIL PROTECTED]@%make[3]: Entering directory `/usr/src/linux-2.4.23'
-D__KERNEL__ -I/usr/src/linux-2.4.23/include -Wall -Wstrict-prototypes
-Wno-trigrap
make[3]: Leaving directory `/usr/src/linux-2.4.23'%g
Here obviousely the "make[3]..." lines have to be removed.
While I would consider this as a bug of autoconf which should circumvent
this kind of behaviour I would like to know how to work around this problem
sanely.
Kind regards
Andreas.
