From: axel@pearbough.net
To: "ALESSANDRO.SUARDI" <ALESSANDRO.SUARDI@oracle.com>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: module-init-tools 0.9.3 -- "missing" issue
Date: Tue, 10 Dec 2002 17:24:06 +0100 [thread overview]
Message-ID: <20021210162406.GA24309@neon.pearbough.net> (raw)
In-Reply-To: <2105495.1039535073217.JavaMail.nobody@web55.us.oracle.com>
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,
next prev parent reply other threads:[~2002-12-10 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 15:44 ALESSANDRO.SUARDI
2002-12-10 16:24 ` axel [this message]
2002-12-10 17:19 ` Rusty Lynch
2002-12-10 22:59 ` Rusty Russell
2002-12-10 23:27 ` Alessandro Suardi
2002-12-11 0:35 ` Rusty Russell
2002-12-10 17:07 ALESSANDRO.SUARDI
2002-12-11 1:22 Jean Tourrilhes
2002-12-11 15:53 ALESSANDRO.SUARDI
2002-12-11 23:37 ` Jean Tourrilhes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021210162406.GA24309@neon.pearbough.net \
--to=axel@pearbough.net \
--cc=ALESSANDRO.SUARDI@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®