As per the README...
[asuardi@dolphin module-init-tools-0.9.3]$ aclocal
[asuardi@dolphin module-init-tools-0.9.3]$ automake --add-missing --copy
Makefile.am: installing `./depcomp'
[asuardi@dolphin module-init-tools-0.9.3]$ autoconf
[asuardi@dolphin module-init-tools-0.9.3]$ ./configure --prefix=/
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/download/kernel/v2.5/module-init-tools-0.9.3/missing: Unknown `--run' option
Try `/download/kernel/v2.5/module-init-tools-0.9.3/missing --help' for more information
configure: WARNING: `missing' script is too old or missing
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
configure: creating ./config.status
config.status: creating Makefile
config.status: executing depfiles commands
So - it complains about 'missing' not knowing the --run option. Indeed:
[asuardi@dolphin module-init-tools-0.9.3]$ ./missing --help
./missing [OPTION]... PROGRAM [ARGUMENT]...
Handle `PROGRAM [ARGUMENT]...' for when PROGRAM is missing, or return an
error status if there is no known handling for PROGRAM.
Options:
-h, --help display this help and exit
-v, --version output version information and exit
Supported PROGRAM values:
aclocal touch file `aclocal.m4'
autoconf touch file `configure'
autoheader touch file `config.h.in'
automake touch all `Makefile.in' files
bison create `y.tab.[ch]', if possible, from existing .[ch]
flex create `lex.yy.c', if possible, from existing .c
lex create `lex.yy.c', if possible, from existing .c
makeinfo touch the output file
yacc create `y.tab.[ch]', if possible, from existing .[ch]
[asuardi@dolphin module-init-tools-0.9.3]$
Unfortunately I'm a newbie in the new module-init-tools && little time to
dig deeper, so take this as a very simple report. Thanks,
--alessandro
Hi ALESSANDRO.SUARDI!
I'd say your automake is too old or too new. Not sure.
Axel
On Tue, 10 Dec 2002, ALESSANDRO.SUARDI wrote:
> [asuardi@dolphin module-init-tools-0.9.3]$ automake --add-missing --copy
> Makefile.am: installing `./depcomp'
> [asuardi@dolphin module-init-tools-0.9.3]$ autoconf
> [asuardi@dolphin module-init-tools-0.9.3]$ ./configure --prefix=/
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking target system type... i686-pc-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /download/kernel/v2.5/module-init-tools-0.9.3/missing: Unknown `--run' option
> Try `/download/kernel/v2.5/module-init-tools-0.9.3/missing --help' for more information
> configure: WARNING: `missing' script is too old or missing
> checking for gawk... gawk
> checking whether make sets ${MAKE}... yes
> checking for gcc... gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: executing depfiles commands
>
> So - it complains about 'missing' not knowing the --run option. Indeed:
>
> [asuardi@dolphin module-init-tools-0.9.3]$ ./missing --help
> ./missing [OPTION]... PROGRAM [ARGUMENT]...
>
> Handle `PROGRAM [ARGUMENT]...' for when PROGRAM is missing, or return an
> error status if there is no known handling for PROGRAM.
>
> Options:
> -h, --help display this help and exit
> -v, --version output version information and exit
>
> Supported PROGRAM values:
> aclocal touch file `aclocal.m4'
> autoconf touch file `configure'
> autoheader touch file `config.h.in'
> automake touch all `Makefile.in' files
> bison create `y.tab.[ch]', if possible, from existing .[ch]
> flex create `lex.yy.c', if possible, from existing .c
> lex create `lex.yy.c', if possible, from existing .c
> makeinfo touch the output file
> yacc create `y.tab.[ch]', if possible, from existing .[ch]
> [asuardi@dolphin module-init-tools-0.9.3]$
>
>
> Unfortunately I'm a newbie in the new module-init-tools && little time to
> dig deeper, so take this as a very simple report. Thanks,
Axel wrote:
> Hi ALESSANDRO.SUARDI!
Yeah, make fun of me - you'll be damned to use WebMail for your next 10 lives ;)
> I'd say your automake is too old or too new. Not sure.
RedHat 8.0 comes with automake 1.5 and 1.6.3 - both yield the same result.
--alessandro
I see the same thing on my RH 8.0 box (autoconf 2.53). I can still build, I just get the warning. Although it looks like autoconf
does this by design because after running aclocal my aclocal.m4 has some extra code added to the end that causes this ==>
# AM_MISSING_HAS_RUN
# ------------------
# Define MISSING if not defined so far and test if it supports --run.
# If it does, set am_missing_run to use it, otherwise, to nothing.
AC_DEFUN([AM_MISSING_HAS_RUN],
[AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl
test x"${MISSING+set}" = xset || MISSING="\${SHELL} $am_aux_dir/missing"
# Use eval to expand $SHELL
if eval "$MISSING --run true"; then
am_missing_run="$MISSING --run "
else
am_missing_run=
AC_MSG_WARN([`missing' script is too old or missing])
fi
])
----- Original Message -----
From: "ALESSANDRO.SUARDI" <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, December 10, 2002 7:44 AM
Subject: module-init-tools 0.9.3 -- "missing" issue
> As per the README...
>
> [asuardi@dolphin module-init-tools-0.9.3]$ aclocal
> [asuardi@dolphin module-init-tools-0.9.3]$ automake --add-missing --copy
> Makefile.am: installing `./depcomp'
> [asuardi@dolphin module-init-tools-0.9.3]$ autoconf
> [asuardi@dolphin module-init-tools-0.9.3]$ ./configure --prefix=/
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking target system type... i686-pc-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /download/kernel/v2.5/module-init-tools-0.9.3/missing: Unknown `--run' option
> Try `/download/kernel/v2.5/module-init-tools-0.9.3/missing --help' for more information
> configure: WARNING: `missing' script is too old or missing
> checking for gawk... gawk
> checking whether make sets ${MAKE}... yes
> checking for gcc... gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: executing depfiles commands
>
> So - it complains about 'missing' not knowing the --run option. Indeed:
>
> [asuardi@dolphin module-init-tools-0.9.3]$ ./missing --help
> ./missing [OPTION]... PROGRAM [ARGUMENT]...
>
> Handle `PROGRAM [ARGUMENT]...' for when PROGRAM is missing, or return an
> error status if there is no known handling for PROGRAM.
>
> Options:
> -h, --help display this help and exit
> -v, --version output version information and exit
>
> Supported PROGRAM values:
> aclocal touch file `aclocal.m4'
> autoconf touch file `configure'
> autoheader touch file `config.h.in'
> automake touch all `Makefile.in' files
> bison create `y.tab.[ch]', if possible, from existing .[ch]
> flex create `lex.yy.c', if possible, from existing .c
> lex create `lex.yy.c', if possible, from existing .c
> makeinfo touch the output file
> yacc create `y.tab.[ch]', if possible, from existing .[ch]
> [asuardi@dolphin module-init-tools-0.9.3]$
>
>
> Unfortunately I'm a newbie in the new module-init-tools && little time to
> dig deeper, so take this as a very simple report. Thanks,
>
> --alessandro
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
In message <[email protected]> you writ
e:
> As per the README...
>
> [asuardi@dolphin module-init-tools-0.9.3]$ aclocal
> [asuardi@dolphin module-init-tools-0.9.3]$ automake --add-missing --copy
> Makefile.am: installing `./depcomp'
> [asuardi@dolphin module-init-tools-0.9.3]$ autoconf
> [asuardi@dolphin module-init-tools-0.9.3]$ ./configure --prefix=/
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking target system type... i686-pc-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /download/kernel/v2.5/module-init-tools-0.9.3/missing: Unknown `--run' option
> Try `/download/kernel/v2.5/module-init-tools-0.9.3/missing --help' for more i
nformation
Hmm, you don't need to run aclocal, automake and autoconf if you don't
alter the sources. I have altered the README to put that at the
bottom:
5) If you want to hack on the source:
aclocal && automake --add-missing --copy && autoconf
Thanks for the report!
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
Rusty Russell wrote:
> In message <[email protected]> you write:
>
>>As per the README...
[snip]
>
> Hmm, you don't need to run aclocal, automake and autoconf if you don't
> alter the sources. I have altered the README to put that at the
> bottom:
>
> 5) If you want to hack on the source:
> aclocal && automake --add-missing --copy && autoconf
>
> Thanks for the report!
Thanks for the clarification. Just wanted to add that following
Rusty Lynch's hint to ignore the 'missing' issue I successfully
installed 0.9.3 and they appear to work on 2.5.51 (I was able
to modprobe vfat - but not the full irda stack, I'll report this
separately to Jean) _and_ on 2.4.20 (modular IrDA and PPP are
channeling this message to you - loaded by 0.9.3 :).
--alessandro
"Seems that you can't get any more than half free"
(Bruce Springsteen, "Straight Time")
In message <[email protected]> you write:
> Rusty Russell wrote:
> > 5) If you want to hack on the source:
> > aclocal && automake --add-missing --copy && autoconf
> to modprobe vfat - but not the full irda stack, I'll report this
> separately to Jean) _and_ on 2.4.20 (modular IrDA and PPP are
I'd appreciate receiving a copy of that irda report. It's probably
not Jean's fault.
Thanks,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
Rusty Russell wrote :
> In message <[email protected]> you write:
> > to modprobe vfat - but not the full irda stack, I'll report this
> > separately to Jean) _and_ on 2.4.20 (modular IrDA and PPP are
>
> I'd appreciate receiving a copy of that irda report. It's probably
> not Jean's fault.
I've just managed to load and run Linux-IrDA on 2.5.51, and
apart from a few warning (see my other e-mail) it was working. I even
tested PPP over IrCOMM. But I didn't check smc-ircc.
So, this one might be *mine* ;-)
Have fun...
Jean
Jean Tourrhiles wrote:
>
> Rusty Russell wrote :
> > In message <[email protected]> you write:
> > > to modprobe vfat - but not the full irda stack, I'll report this
> > > separately to Jean) _and_ on 2.4.20 (modular IrDA and PPP are
> >
> > I'd appreciate receiving a copy of that irda report. It's probably
> > not Jean's fault.
> I've just managed to load and run Linux-IrDA on 2.5.51, and
> apart from a few warning (see my other e-mail) it was working. I even
> tested PPP over IrCOMM. But I didn't check smc-ircc.
> So, this one might be *mine* ;-)
Yep, it's smc-ircc :)
Dec 10 22:57:36 dolphin kernel: IrCOMM protocol (Dag Brattli)
Dec 10 22:57:36 dolphin irattach: executing: '/sbin/modprobe irda0'
Dec 10 22:57:36 dolphin kernel: found SMC SuperIO Chip (devid=0x09 rev=08 base=0x03f0): FDC37N958FR
Dec 10 22:57:36 dolphin kernel: SMC IrDA Controller found
Dec 10 22:57:36 dolphin kernel: IrCC version 1.1, firport 0x290, sirport 0x3e8 dma=3, irq=4
Dec 10 22:57:36 dolphin irattach: + FATAL: Error inserting smc_ircc
(/lib/modules/2.5.51/kernel/smc-ircc.ko): No such device
Dec 10 22:57:36 dolphin irattach: Trying to load module irda0 exited with status 1
Dec 10 22:57:36 dolphin irattach: executing: 'echo 1 >
/proc/sys/net/irda/discovery'
Dec 10 22:57:36 dolphin irattach: Starting device irda0
Dec 10 22:57:36 dolphin kernel: Module irda cannot be unloaded due to unsafe usage in net/irda/af_irda.c:1146
Should I give up on it and go for Daniele's smsc-ircc2 ? I confess I hadn't
used 2.5.xx for a couple of weeks awaiting for some form of stabilization
of the new module code (don't blame me - I can only, ahem, "test" on
my work laptop), and I had forgot about smsc-ircc2.
Since it seems someone could make some of the modular stuff work
I'm back in the game :)
--alessandro
On Wed, Dec 11, 2002 at 07:53:18AM -0800, ALESSANDRO.SUARDI wrote:
>
> Yep, it's smc-ircc :)
>
> Dec 10 22:57:36 dolphin kernel: IrCOMM protocol (Dag Brattli)
> Dec 10 22:57:36 dolphin irattach: executing: '/sbin/modprobe irda0'
> Dec 10 22:57:36 dolphin kernel: found SMC SuperIO Chip (devid=0x09 rev=08 base=0x03f0): FDC37N958FR
> Dec 10 22:57:36 dolphin kernel: SMC IrDA Controller found
> Dec 10 22:57:36 dolphin kernel: IrCC version 1.1, firport 0x290, sirport 0x3e8 dma=3, irq=4
> Dec 10 22:57:36 dolphin irattach: + FATAL: Error inserting smc_ircc
> (/lib/modules/2.5.51/kernel/smc-ircc.ko): No such device
> Dec 10 22:57:36 dolphin irattach: Trying to load module irda0 exited with status 1
> Dec 10 22:57:36 dolphin irattach: executing: 'echo 1 >
> /proc/sys/net/irda/discovery'
> Dec 10 22:57:36 dolphin irattach: Starting device irda0
> Dec 10 22:57:36 dolphin kernel: Module irda cannot be unloaded due to unsafe usage in net/irda/af_irda.c:1146
>
> Should I give up on it and go for Daniele's smsc-ircc2 ? I confess I hadn't
> used 2.5.xx for a couple of weeks awaiting for some form of stabilization
> of the new module code (don't blame me - I can only, ahem, "test" on
> my work laptop), and I had forgot about smsc-ircc2.
>
> Since it seems someone could make some of the modular stuff work
> I'm back in the game :)
>
> --alessandro
Hum... Looks like a weird interaction between smc-ircc and
irport, or allocation failure. Please activate IrDA debug, set it to
level 1 (echo 1 >> /proc/sys/net/irda/debug) and send the new kernel
log.
Thanks...
Jean