Ralf Wildenhues writes:
> * Russ Allbery wrote on Wed, Dec 16, 2009 at 05:08:14AM CET:
>> Do you really want to generate separate copies of the man page for each
>> function documented by the same source POD file? It's more normal to
>> generate one copy of the man page and then, during make ins
* Monty Taylor wrote on Wed, Dec 16, 2009 at 05:01:15AM CET:
> I have several document source files, each ending in pod, which will
> each produce one more more man pages when run through pod2man. Simply,
> something like this:
>
> function1.3: source.pod
> function2.3: source.pod
>
> %.3: %.pod
* Russ Allbery wrote on Wed, Dec 16, 2009 at 05:08:14AM CET:
> Do you really want to generate separate copies of the man page for each
> function documented by the same source POD file? It's more normal to
> generate one copy of the man page and then, during make install, symlink
> the other ones
Monty Taylor writes:
> I have several document source files, each ending in pod, which will
> each produce one more more man pages when run through pod2man. Simply,
> something like this:
> function1.3: source.pod
> function2.3: source.pod
Do you really want to generate separate copies of the m
Hey all,
I have a build thing that I cannot for the life of me figure out a
_good_ way to express. (I can express it with lots of copy and paste)
I have several document source files, each ending in pod, which will
each produce one more more man pages when run through pod2man. Simply,
something l
Hi Jim,
* Jim Meyering wrote on Tue, Dec 15, 2009 at 07:48:21AM CET:
> Ralf Wildenhues wrote:
> > Adding LIBTOOL here is wrong; you meant LIBTOOLIZE.
>
> I've removed it.
> I don't see anything except bootstrap that runs $(LIBTOOLIZE). Do you?
No, adding LIBTOOLIZE should be fine.
> > There ar
