From: Selwyn Tang <selwyn@hectrix.com>
To: linux-mtd@lists.infradead.org
Subject: Cannot automake after patching grub with grub-2003-01-08-doc.patch
Date: Tue, 05 Aug 2003 12:29:17 +0800 [thread overview]
Message-ID: <3F2F329D.5040204@hectrix.com> (raw)
Dear all,
I downloaded the latest snapshot of grub through cvs and applied
grub-2003-01-08-doc.patch with only one rejection in ChangeLog. I then
followed README_DiskOnChip to run aclocal successfully. But when I run
automake, a lot of "AMDEP does not appear in AM_CONDITIONAL" messages
appeared! For examples,
/usr/share/automake-1.5/am/depend2.am: AMDEP does not appear in
AM_CONDITIONAL
/usr/share/automake-1.5/am/lang-compile.am: AMDEP does not appear in
AM_CONDITIONAL
Before that, I use automake 1.4p5 and when I run automake it told me
that 1.5 was expected. Then I ln -s automake to automake-1.5 in my
RedHat 7.3, and got the above error.
Have anyone successfully applied the patch to grub, compiled it and get
the "grub_firmware" file in stage1/ ?
Yours,
Selwyn
next reply other threads:[~2003-08-05 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 4:29 Selwyn Tang [this message]
2003-08-05 9:39 ` Cannot automake after patching grub with grub-2003-01-08-doc.patch Selwyn Tang
2003-08-05 10:14 ` Selwyn Tang
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=3F2F329D.5040204@hectrix.com \
--to=selwyn@hectrix.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