All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas <futur.andy@googlemail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Warnings when building svn2137
Date: Sat, 25 Apr 2009 17:22:23 +0200	[thread overview]
Message-ID: <49F32AAF.7020909@googlemail.com> (raw)
In-Reply-To: <49F31A78.1010507@earthlink.net>

BandiPat schrieb:
> Pavel Roskin wrote:
>> Quoting BandiPat <magicpage91@earthlink.net>:
>>
>>> 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.
>>
>> I didn't realize we would create empty manual pages in that case!  
>> Still, my patch will fix it.
>>
> ---------
> Yep, creates very nice empty manuals!  ;-)  Anyway, if someone hasn't 
> already, it might be a good idea to mention the help2man in your Wiki 
> and/or the Readme within the source.  Maybe something in the Wiki 
> about the programs needed to compile Grub2 the most efficiently?
>
> It works a treat though and now Zenwalk mirrors have it available!
>
> Thanks again.
>
> Oh, has anyone experienced any problems with grub-mkdevicemap when 
> installing Grub2 or updating?  I had one user complain about it 
> segfaulting on his machine, but I've not seen any problems.  This is 
> with svn2137.
I'm experiencing also problems using it, but it's not segfaulting. Using 
a svn2130 build grub-mkdevicemap --no-floppy create a device.map with 
proper content like this:
(hd0) /dev/sda
But a svn2137 build (exactly the same BandiPat uses) creates this 
content, which might not be wrong, but at least the most important part 
my HDD is missing:
(fd0) (null)

Probably this problem was introduced by revision 2133 and obviously 
wasn't fixed in rev 2134 - 2137 and in 2138 - 2140 I can see nothing 
which might fix this.
It would be great if somebody could have a look what could cause this 
problem. Maybe davem as the author of that revision.
If you need any additional information give me a yell and I'll try my 
best to provide it.

Andreas




  reply	other threads:[~2009-04-25 15:22 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
2009-04-24 22:03       ` Pavel Roskin
2009-04-25 14:13         ` BandiPat
2009-04-25 15:22           ` Andreas [this message]
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=49F32AAF.7020909@googlemail.com \
    --to=futur.andy@googlemail.com \
    --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.