module-init-tools 0.9.3 -- "missing" issue

DISCUSSION ALESSANDRO.SUARDI 4 participants 6 messages Dec 10, 2002 – Dec 11, 2002

Share & tools

ALESSANDRO.SUARDI

author

2002-12-10 15:41 UTC #0 lore raw

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

[email protected]

2002-12-10 16:17 UTC #1 lore raw

Hi ALESSANDRO.SUARDI!

I'd say your automake is too old or too new. Not sure.

Axel

Quoted 55 lines · ALESSANDRO.SUARDI

[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,

Rusty Lynch

2002-12-10 17:12 UTC #2 lore raw

In reply to ALESSANDRO.SUARDI

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

Quoted 65 lines

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/

Rusty Russell

2002-12-10 23:05 UTC #3 lore raw

In reply to ALESSANDRO.SUARDI

In message <[email protected]> you writ e:

Quoted 14 lines

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.

Alessandro Suardi

author

2002-12-10 23:23 UTC #4 lore raw

Quoted 3 lines · Rusty Russell

In message <[email protected]> you write:
Quoted 1 line
As per the README...

[snip]

Quoted 9 lines

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")

Rusty Russell

2002-12-11 00:28 UTC #5 lore raw

In message <[email protected]> you write:

Quoted 6 lines

Quoted 2 lines · Rusty Russell
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.