From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Warnings when building svn2137
Date: Fri, 24 Apr 2009 14:52:35 -0400 [thread overview]
Message-ID: <1240599155.26226.14.camel@mj> (raw)
In-Reply-To: <49F1FDC7.90104@earthlink.net>
On Fri, 2009-04-24 at 13:58 -0400, BandiPat wrote:
> BandiPat wrote:
> > Getting these errors when building the package for Zenwalk Linux!
> >
> > WARNING: zero length file usr/include/grub/lib/datetime.h
> > WARNING: usr/man/man1/grub-mkimage.1.gz is an empty gzipped file
...
I guess it's files installed in a temporary location, and the messages
are from your package manager.
> Answering my own email. Seems these files have been empty for quite
> some time, so this is nothing new. Don't understand why suddenly one of
> my computers started alerting me to them, while another still does not
> mention them. Seems though, someone still needs to fill these manuals
> up so they'll have some info for the users later. :-)
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.
> 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.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-04-24 18:52 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 [this message]
2009-04-24 21:37 ` BandiPat
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=1240599155.26226.14.camel@mj \
--to=proski@gnu.org \
--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.