public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "brent@ajr-industrial.com" <brent@ajr-industrial.com>
To: linux-mtd@lists.infradead.org
Subject: Compilng GRUB with DOC patch
Date: Thu, 12 May 2005 23:50:28 -0400	[thread overview]
Message-ID: <7680-22005551335028622@M2W098.mail2web.com> (raw)

Hello all.  I have been attempting to patch grub sources with DOC pathces
to get a grub_fireware file.  Althrough one patch patches cleanly (the
grub-0.92-doc.patch on the GRUB 0.92 sources), NONE of them have produced a
grub-firmware file in the stage1 directory.

I do the following:

patch -p0 < name_of_patch.patch

At this point most of them complain about "hunks" failing, with exception
of the grub-0.92-doc.patch with grub sources, version 0.92.

aclocal && automake && autoconf

./conifgure --enable-diskonchip-2000 --enable-ext2fs --disable-ffs
--disable-xfs --disable-jfs --disable-vstafs --disable-reiserfs
--disable-minix --disable-fat

make

I have tried the above with grub sources versions 0.92, 0.93, 0.94, and
0.97 and have tried the patch I mentioned above as well as
grub-2002-10-08.patch and grub-2003-01-08-doc.patch.

The example which I am following uses the grub-2002-02-19-doc.patch, and it
is reported to function properly.  Does anyone know where I could obtain
this patch?  I am using an x86 board, I wonder if I could just get a
grub_fireware image?  If so, could someone send me one?  Or does anyone
know of a good combinatioin of sources/patch or a way to tweak one or the
other to get them to play nice together?  

Thanks in advance.

-Brent Roberts


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

                 reply	other threads:[~2005-05-13  4:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7680-22005551335028622@M2W098.mail2web.com \
    --to=brent@ajr-industrial.com \
    --cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox