`./configure --help`. In other words,
the user has no chance to find out that there exists a `--srcdir`
option to override `AC_CONFIG_SRCDIR`.
I thus suggest to either make `./configure --help` always work, or at
least change the above error message to something like
```
configure: error: cannot find
I was curious whether there was a way to add some documentation to the
configure --help output. An extra paragraph perhaps, near the bottom. Yes, a
README could do just as well, but I have my reasons. Thanks.
__
Jeff Daily
Scientist
Pacific
Hello Jeff,
* Daily, Jeff A wrote on Mon, Jan 25, 2010 at 08:27:54PM CET:
I was curious whether there was a way to add some documentation to the
configure --help output. An extra paragraph perhaps, near the bottom.
Yes there is, but not in a documented way (so it might break with a
future
Eric Blake wrote:
Furthermore, your patch still has some portability problems. For example,
... you cannot rely on the existence of mktemp.
I don't want to consume a lot of your time answering ignorant
questions from a newbie, but why is it that AS_TMPDIR is
able to use mktemp?
--
William
Hi William,
* William Pursell wrote on Sun, Oct 12, 2008 at 08:57:50AM CEST:
Eric Blake wrote:
Furthermore, your patch still has some portability problems. For example,
... you cannot rely on the existence of mktemp.
I don't want to consume a lot of your time answering ignorant
questions
This may be a controversial patch, but I think that
of all the times I have ever run configure --help
without appending |less it was either because I
piped the output through more or because I forgot
to paginate completely.
--
William Pursell
diff --git a/lib/autoconf/general.m4 b/lib/autoconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to William Pursell on 10/11/2008 10:27 AM:
This may be a controversial patch, but I think that
of all the times I have ever run configure --help
without appending |less it was either because I
piped the output through more or because I
Hello Stepan,
* Stepan Kasal wrote on Tue, Jul 17, 2007 at 02:45:46PM CEST:
[...]
Near the top of m4sh initialization, we'd do:
case $1 in
--help | --help=* | --version ) as_skip_wr_tests=yes ;;
esac
And then put the test which write to cwd inside an
if test -z
Hello Stepan,
* Stepan Kasal wrote on Tue, Jul 17, 2007 at 02:45:46PM CEST:
[...]
Near the top of m4sh initialization, we'd do:
case $1 in
--help | --help=* | --version ) as_skip_wr_tests=yes ;;
esac
And then put the test which write to cwd inside an
if test -z
Hello,
On Sun, Jul 01, 2007 at 05:18:18PM +0200, Hans Ulrich Niedermann wrote:
[...] The user expectation is that running a program with --help or
--version just prints the help text or version and then exits without
causing *any* side effects.
right.
If I remember correctly, configure
Hello,
On Sun, Jul 01, 2007 at 05:18:18PM +0200, Hans Ulrich Niedermann wrote:
[...] The user expectation is that running a program with --help or
--version just prints the help text or version and then exits without
causing *any* side effects.
right.
If I remember correctly, configure
Hello Hans Ulrich,
* Hans Ulrich Niedermann wrote on Mon, Jun 25, 2007 at 06:20:53PM CEST:
configure --help=recursive does not run the --help parts of the
directories included via AC_CONFIG_SUBDIR when called as
$ /path/to/top_srcdir/configure --help=recursive
Ralf Wildenhues wrote:
* Hans Ulrich Niedermann wrote on Mon, Jun 25, 2007 at 06:20:53PM CEST:
configure --help=recursive does not run the --help parts of the
directories included via AC_CONFIG_SUBDIR when called as
$ /path/to/top_srcdir/configure --help=recursive
Hello Hans Ulrich,
* Hans Ulrich Niedermann wrote on Mon, Jun 25, 2007 at 06:20:53PM CEST:
configure --help=recursive does not run the --help parts of the
directories included via AC_CONFIG_SUBDIR when called as
$ /path/to/top_srcdir/configure --help=recursive
Ralf Wildenhues wrote:
* Hans Ulrich Niedermann wrote on Mon, Jun 25, 2007 at 06:20:53PM CEST:
configure --help=recursive does not run the --help parts of the
directories included via AC_CONFIG_SUBDIR when called as
$ /path/to/top_srcdir/configure --help=recursive
Synopsis:
configure --help=recursive does not run the --help parts of the
directories included via AC_CONFIG_SUBDIR when called as
$ /path/to/top_srcdir/configure --help=recursive
or
$ ../configure --help=recursive
Versions affected:
autoconf (GNU Autoconf) 2.61
Vincent Torri [EMAIL PROTECTED] writes:
I've written an m4 macro (see attached file).
ENOENT.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
On Sat, 31 Mar 2007, Andreas Schwab wrote:
I've written an m4 macro (see attached file).
ENOENT.
Oups, here it is :)
Vincent Torridnl use: AC_CHECK_ECORE_MODULE(Foo, default-enabled[, dependancy[,
ACTION-IF-FOUND[, ACTION-IF-NOT-FOUND]]])
AC_DEFUN([AC_CHECK_ECORE_MODULE],
[
Vincent Torri [EMAIL PROTECTED] writes:
if test x$2 = xno ; then
AC_ARG_ENABLE(ecore-[]DOWN,
AS_HELP_STRING(
[--enable-ecore-[]DOWN],
[enable the ecore_[]DOWN module. [[default=disabled]]]
),
[ want_ecore_[]DOWN=$enableval ],
[ want_ecore_[]DOWN=no ])
else
On Sat, 31 Mar 2007, Andreas Schwab wrote:
Vincent Torri [EMAIL PROTECTED] writes:
if test x$2 = xno ; then
AC_ARG_ENABLE(ecore-[]DOWN,
AS_HELP_STRING(
[--enable-ecore-[]DOWN],
[enable the ecore_[]DOWN module. [[default=disabled]]]
),
[ want_ecore_[]DOWN=$enableval
:
AC_CHECK_ECORE_MODULE([Job],
[yes])
configure --help displays:
--enable-ecore-job enable the ecore_job module. [default=disabled]
--disable-ecore-job disable the ecore_job module. [default=enabled]
If I do not use the macro, the following code:
AC_ARG_ENABLE(ecore-job,
AC_HELP_STRING
* Paul Eggert wrote on Wed, Sep 20, 2006 at 06:55:59PM CEST:
Ralf Wildenhues [EMAIL PROTECTED] writes:
* lib/autoconf/c.m4 (_AC_ARG_VAR_LDFLAGS): Update comment.
(_AC_ARG_VAR_LIBS): New macro: let LIBS be precious.
(AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC): Call
Hello Olly,
* Olly Betts wrote on Tue, Sep 19, 2006 at 01:21:58AM CEST:
After mail from a user who'd tried to specify -llibrary in LDFLAGS
I was suprised to realise that the output of ./configure --help
doesn't mention LIBS at all. I think it should
[...]
Digging deeper, I noticed LIBS
Ralf Wildenhues [EMAIL PROTECTED] writes:
* lib/autoconf/c.m4 (_AC_ARG_VAR_LDFLAGS): Update comment.
(_AC_ARG_VAR_LIBS): New macro: let LIBS be precious.
(AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC): Call _AC_ARG_VAR_LIBS.
* lib/autoconf/fortran.m4 (AC_PROG_F77,
Hello Olly,
* Olly Betts wrote on Tue, Sep 19, 2006 at 01:21:58AM CEST:
After mail from a user who'd tried to specify -llibrary in LDFLAGS
I was suprised to realise that the output of ./configure --help
doesn't mention LIBS at all. I think it should
[...]
Digging deeper, I noticed LIBS
Ralf Wildenhues [EMAIL PROTECTED] writes:
* lib/autoconf/c.m4 (_AC_ARG_VAR_LDFLAGS): Update comment.
(_AC_ARG_VAR_LIBS): New macro: let LIBS be precious.
(AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC): Call _AC_ARG_VAR_LIBS.
* lib/autoconf/fortran.m4 (AC_PROG_F77,
This is with autoconf 2.60.
After mail from a user who'd tried to specify -llibrary in LDFLAGS
I was suprised to realise that the output of ./configure --help
doesn't mention LIBS at all. I think it should - while the autoconf
info manual documents both LDFLAGS and LIBS and the distinction
Thanks for the general philosophy on how to accomplish this task, it's
much needed. I have several questions though,
I understand how to set the libs flag,
LIBS=$LIBS -lreadline -lhistory
Nope. Most likely, you want
LIBS=-lreadline -lhistory $LIBS
instead. New libraries go
Something like a
--with-readline[=included]
might be useful, although I don't know of an established convention for
the optional `=included' part.
Also, AC_CHECK_LIB can not even look for libreadline.a until after the
make is done. Is there a way to ./configure make make install
Hi Bob,
* Bob Rossi wrote on Thu, Jul 07, 2005 at 04:34:25PM CEST:
Something like a
--with-readline[=included]
might be useful, although I don't know of an established convention for
the optional `=included' part.
Also, AC_CHECK_LIB can not even look for libreadline.a until after
Hi Bob,
* Bob Rossi wrote on Tue, Jul 05, 2005 at 05:25:21PM CEST:
I am having a little trouble using autoconf to configure my package.
Currently, I am tring to build a package that depends on another
package. Basically CGDB (main package) depends on Readline (second
package).
I am using
On Wed, Jul 06, 2005 at 06:07:36PM +0200, Ralf Wildenhues wrote:
Hi Bob,
* Bob Rossi wrote on Tue, Jul 05, 2005 at 05:25:21PM CEST:
I am having a little trouble using autoconf to configure my package.
Currently, I am tring to build a package that depends on another
package. Basically
Hi,
I am having a little trouble using autoconf to configure my package.
Currently, I am tring to build a package that depends on another
package. Basically CGDB (main package) depends on Readline (second
package).
I am using
AC_CONFIG_SUBDIRS(readline-5.0)
to configure readline. This
Hello Claudio.
On Mon, Jun 13, 2005 at 11:13:24PM -0700, Claudio Fontana wrote:
track it myself but got lost somewhere between 2.13 or
so and 2.49 (are there in-between versions at all? the
gnu ftp repository shown none).
Actually, I'm surprised to hear about 2.49.
I think you can safely
On Wed, 22 Jun 2005, Stepan Kasal wrote:
Hello Claudio.
On Mon, Jun 13, 2005 at 11:13:24PM -0700, Claudio Fontana wrote:
track it myself but got lost somewhere between 2.13 or
so and 2.49 (are there in-between versions at all? the
gnu ftp repository shown none).
Actually, I'm surprised to
Hello,
I have some questions about ./configure --help output.
I am using expect to automate detection of supported
configure options, and this works well with configure
scripts produced with recent versions of autoconf.
To be able to know what to expect, I need to know when
current output format
Claudio Fontana [EMAIL PROTECTED] writes:
To be able to know what to expect, I need to know when
current output format (categories, options and
comments) was first introduced in autoconf.
That is not the Autoconf Way. Instead, I would inspect the
output of autoconf --help to see whether it's
inspect the
output of autoconf --help to see whether it's the
format you like.
Surely you mean 'configure --help' above?
I wrote regular expressions that successfully capture
configure --help options when they are created using
AC_HELP_STRING (or not, if the output if somewhat
similar), so yes
Claudio Fontana [EMAIL PROTECTED] writes:
Surely you mean 'configure --help' above?
Yes, sorry.
I'd like to know when current option categories (Optional
packages:, Optional Features:, Some influential environment
variables, X features:, ..) have first been introduced.
Sorry, I still don't
can find out by
running configure
--help.
Coming to think about it again, it is not strictly
necessary; I was thinking that if I can determine the
associations between autoconf versions and ./configure
--help output formats, I can more cleanly support
different versions and different formats
have is that calling ./configure --help=recursive in
the root directory does not pass --srcdir to the various configure.gnu in the
subdirectories, but only --help=recursive . Therefore, in this particular case,
configure.gnu fails to find its configure when builddir != srcdir .
The patch
Paul == Paul Eggert [EMAIL PROTECTED] writes:
Are you actually using non fixed fonts for programming/terms?
Paul Sure. I've been doing it for twenty years in some contexts.
Paul It's long been the tradition in the Smalltalk world, for
Paul example.
OK. I never tried actually, but I'm so
From: Akim Demaille [EMAIL PROTECTED]
Date: 25 Oct 2001 12:29:12 +0200
Paul C is older and (like Cobol and Fortran) the tradition is
Paul fixed-width. I have used C with varying-width fonts with some
Paul success, though never with the GNU indenting style (which isn't
Paul quite right
Not a bug!
This is meant. Tell me how to align the other options, and help us
fixing bugs.
~/src/am % ./configure --helpnostromo 12:09
`configure' configures GNU Automake 1.5a to adapt to many kinds of systems.
Usage: ./configure [OPTION]... [VAR=VALUE
From: Akim Demaille [EMAIL PROTECTED]
Date: 24 Oct 2001 12:09:59 +0200
Tell me how to align the other options, and help us fixing bugs.
Well, you asked, so here's my opinion: don't align at all.
I long ago gave up on aligning options.
For example, here's what I do in my --help output:
Paul == Paul Eggert [EMAIL PROTECTED] writes:
From: Akim Demaille [EMAIL PROTECTED] Date: 24 Oct 2001 12:09:59
+0200
Tell me how to align the other options, and help us fixing bugs.
Paul Well, you asked, so here's my opinion: don't align at all.
:) :) :)
Paul I long ago gave up on
From: Akim Demaille [EMAIL PROTECTED]
Date: 24 Oct 2001 14:09:49 +0200
Paul * It looks equally nice with varying-width fonts. This is
Paul becoming more important with time (e.g. GNU Emacs 21).
Hm, I would not use `nice' in the sentence, but I agree on `equally' :)
Are you actually
The bug below was reported against version 2.50 of the Debian
GNU/Linux package for autoconf. It appears to be in version 2.52
as well.
Start of forwarded message
Subject: Bug#116744: configure --help has incorrectly formatted help
Date: Tue, 23 Oct
The subject says it all. I consider it a bug.
Is this easy to fix?
Lars J
"Lars J. Aas" [EMAIL PROTECTED] writes:
The subject says it all. I consider it a bug.
Is this easy to fix?
Nope :( Quite hard. The easiest would be backup/restore :(
"Lars J. Aas" [EMAIL PROTECTED] writes:
The subject says it all. I consider it a bug.
Is this easy to fix?
Hm, on a second thought, now that AS_MESSAGE tests whether the LOG fd
is set to output the message or not, it might be just as easy as
moving the set up of the LOG fd :)
#
On Fri, Feb 02, 2001 at 07:07:57PM +0100, Akim Demaille wrote:
: "Lars J. Aas" [EMAIL PROTECTED] writes:
: The subject says it all. I consider it a bug.
: Is this easy to fix?
:
: Hm, on a second thought, now that AS_MESSAGE tests whether the LOG fd
: is set to output the message or not, it
in EPREFIX
[same as prefix]
This is part of what comes out of
configure --help
But it's ambiguous for -exec-prefix. When they say [same as prefix],
they mean [same as PREFIX], no?
Thanks,
Kathy
53 matches
Mail list logo
