From: BandiPat <magicpage91@earthlink.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Warnings when building svn2137
Date: Fri, 24 Apr 2009 17:37:48 -0400 [thread overview]
Message-ID: <49F2312C.4060009@earthlink.net> (raw)
In-Reply-To: <1240599155.26226.14.camel@mj>
Pavel Roskin wrote:
> The manuals are generated from the output of the corresponding commands.
> I believe your version of help2man is not working. I'm going to fix the
> makefile to prevent generation of empty manuals in that case.
> -----------
Thanks Pavel. Turns out I didn't know about help2man, so did not have
it installed. Also turns out that the Zenwalk mirrors did not have it
available either, so I built a package for that. After installing it,
then recompiling the package, all is well. Wish I had known about that
little program before! I'm guessing there are other programs that use
it when building.
>> The only real warning at this point is the datetime.h, as it shouldn't
>> be showing up at all.
>
> Zero length datetime.h and datetime.c were left in the tree erroneously.
> They were supposed to be moved to different locations. I have removed
> the empty files.
>
-------
This one has never been a big problem, but I'll be glad to see the
warning go away at the end of the package build & check. Thanks for
your help with this.
Regards,
Pat
--
---Zenwalk v6.0--Linux 2.6.28---
Registered Linux User #225206
"Ever tried Zen computing?" http://www.zenwalk.org
next prev parent reply other threads:[~2009-04-24 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 13:06 Warnings when building svn2137 BandiPat
2009-04-24 17:58 ` BandiPat
2009-04-24 18:52 ` Pavel Roskin
2009-04-24 21:37 ` BandiPat [this message]
2009-04-24 22:03 ` Pavel Roskin
2009-04-25 14:13 ` BandiPat
2009-04-25 15:22 ` Andreas
2009-04-25 17:23 ` BandiPat
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=49F2312C.4060009@earthlink.net \
--to=magicpage91@earthlink.net \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.