On Wednesday 2013-01-09 22:27, Stefano Lattarini wrote:
>>
>> Now I just have to figure out why someone thought that openSUSE
>> should create the manpages directly...
>>
>Good question
>
>What happens if you do this instead?
>
>help2man -S FSF ./t/wr
On 01/09/2013 10:13 PM, Jan Engelhardt wrote:
> On Wednesday 2013-01-09 19:11, Stefano Lattarini wrote:
>
>> On 01/09/2013 05:05 PM, Jan Engelhardt wrote:
>>>
>>> The
>>>
>>> help2man: can't get `--help' info from ./aclocal
>>
On Wednesday 2013-01-09 19:11, Stefano Lattarini wrote:
>On 01/09/2013 05:05 PM, Jan Engelhardt wrote:
>>
>> The
>>
>> help2man: can't get `--help' info from ./aclocal
>>
>> error seems to have reappeared in automake-1.13.1 (judging fr
On 01/09/2013 05:05 PM, Jan Engelhardt wrote:
>
> The
>
> help2man: can't get `--help' info from ./aclocal
>
> error seems to have reappeared in automake-1.13.1 (judging from
> http://gnu-automake.7480.n7.nabble.com/Man-pages-for-automake-and-aclocal-td1
The
help2man: can't get `--help' info from ./aclocal
error seems to have reappeared in automake-1.13.1 (judging from
http://gnu-automake.7480.n7.nabble.com/Man-pages-for-automake-and-aclocal-td11966.html)
help2man is of version 1.40.12.
---
Executing(%build): /bin/sh -
ould always be regenerated when the binaries are built and the
cross-compiled binaries would not run on the build machine.
We decided we didn't wanted to ship (or require help2man), so when we
converted to non-recursive Makefile, we solved this problem by added
dependency
foo.1: foo$(EXEEXT)
but
e.
> Assuming GNU make, a good solution would be to use order-only
> dependencies:
>
> foo.1: foo.c | foo$(EXEEXT)
>help2man ...
>
> The above ensures that foo$(EXEEXT) is built before foo.1, but doesn't
> cause foo.1 to be rebuilt just because foo$(EXEEX
On 11/19/2012 08:55 PM, Neil T. Dantam wrote:
>
> Hi,
>
> I'm using help2man to build manpages that I'd like to distribute with
> the source tarball. I followed the instructions/example in the
> automake manual, which has manpage foo.1 depend on foo.c and
> conf
Hi,
I'm using help2man to build manpages that I'd like to distribute with
the source tarball. I followed the instructions/example in the
automake manual, which has manpage foo.1 depend on foo.c and
configure.ac, then does a recursive make to build foo$(EXEEXT):
<http://www.gnu
On 9/30/12 8:27 PM, Peter Johansson wrote:
Any thoughts?
I should read the manual before making noise. Sorry.
http://www.gnu.org/software/automake/manual/automake.html#Errors-with-distclean
--
Peter Johansson
_deps=$(top_srcdir)/configure $(srcdir)/Makefile.in \
$(srcdir)/man/svndigest.x $(top_srcdir)/.revision
$(srcdir)/man/svndigest.1: $(man_deps)
@$(HELP2MAN) --no-info -o $@ \
--include $(srcdir)/man/svndigest.x \
--version-option="--no-verbose --version" \
$(top_builddir
For
> > instance, in GNU Hello (well, except that has only one man page) or
> > coreutils.
>
> Well, if `make' called by the user has to generate man pages with the
> use of help2man, there *must* be a configure check for it. I don't
> see a problem.
The poin
.ac
$(MAKE) $(AM_MAKEFLAGS)cgdb/src/cgdb$(EXEEXT)
help2man ...
See http://sourceware.org/automake/automake.html#distcleancheck
Have a nice day,
Stepan
Hi Stepan,
* Stepan Kasal wrote on Mon, Feb 06, 2006 at 06:54:20PM CET:
>
> > If you instead ever go to use a nonrecursive Makefile structure, you
> > could just add `../cgdb/src/cgdb$(EXEEXT)' to the prerequisites of this
> > rule. Much nicer. ;-)
>
> Recall that cgdb.1 was listed in dist_man
* Ralf Wildenhues wrote on Mon, Feb 06, 2006 at 01:35:24PM CET:
> * Bob Rossi wrote on Mon, Feb 06, 2006 at 12:54:09PM CET:
> >
> > > $(MAKE) $(AM_MAKEFLAGS) -C $(top_builddir)/cgdb/src cgdb$(EXEEXT)
>
> `make -C' is not totally portable; I'd write
>
> cd ../cgdb/src && $(MAKE) $(AM_MAK
* Bob Rossi wrote on Mon, Feb 06, 2006 at 12:54:09PM CET:
>
> > cgdb.1: $(top_srcdir)/cgdb/src/usage.c $(top_srcdir)/configure.in
> > $(MAKE) $(AM_MAKEFLAGS) -C $(top_builddir)/cgdb/src cgdb$(EXEEXT)
`make -C' is not totally portable; I'd write
cd ../cgdb/src && $(MAKE) $(AM_MAKEFLAGS
> On Sun, Feb 05, 2006 at 08:39:44AM -0500, Bob Rossi wrote:
> > dist_man_MANS = cgdb.1
> > # Autogenerate the man page using help2man. This happens whenever the
> > # user modifies either configure.in or usage.c, which contains CGDB's
> > usage.
> >
Hello,
On Sun, Feb 05, 2006 at 08:39:44AM -0500, Bob Rossi wrote:
> dist_man_MANS = cgdb.1
> # Autogenerate the man page using help2man. This happens whenever the
> # user modifies either configure.in or usage.c, which contains CGDB's usage.
> cgdb.1: $(top_srcdir)
Thanks for the vote of confidence, Harlan. The question
unanswered, tho, is, "Why bother?"
Just so this can be documented, this did work for me.
dist_man_MANS = cgdb.1
# Autogenerate the man page using help2man. This happens whenever the
# user modifies either configure.in
On Sun, Feb 05, 2006 at 06:53:28AM +0100, Alexandre Duret-Lutz wrote:
> >>> "BR" == Bob Rossi <[EMAIL PROTECTED]> writes:
>
> BR> My doc directory is built after all others. I was thinking I could have
> BR> a rule in the doc directory that would
I'll suggest GNU AutoGen as another way to deal with help text -> man
pages.
H
>>> "BR" == Bob Rossi <[EMAIL PROTECTED]> writes:
BR> My doc directory is built after all others. I was thinking I could have
BR> a rule in the doc directory that would run help2man if usage.c has
BR> changed. However, if usage.c was changed, by this point,
Hi all,
This is my first attempt at modifying the Makefile.am, to have some
extra work done for me automatically.
I've been working on my documentation for CGDB lately, and found a nifty
program called help2man which generates a simple man page. It looks at the
output of both 'cgdb
Hi Alexandre et al.,
automake supports the installation manual pages. Man pages for programs
are nowadays frequently generated through GNU help2man, documenting the
command line options but leaving the rest to the doc in texinfo format.
Here's a suggestion for rules that would support
Could someone apply this patch?
.[ch]', if possible, from existing .[ch]
flex create \`lex.yy.c', if possible, from existing .c
+ help2man touch the output file
lex create \`lex.yy.c', if possible, from existing .c
makeinfo touch the output file
yacc create \`y.tab
26 matches
Mail list logo