public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Herman Theron" <HEtheron@csir.co.za>
To: <linux-mtd@lists.infradead.org>
Subject: Error using GRUB patch (and LILO questions)
Date: Fri, 22 Feb 2002 09:22:34 +0200	[thread overview]
Message-ID: <sc760dea.038@CS-IMO.CSIR.CO.ZA> (raw)

Hi everybody,

I downloaded the latest GRUB patch for the DOC2000 and also the latest
GRUB cvs. The patch installed perfectly. When I run 
"aclocal && automake && autoconf, I get the following errors:

stage1/Makefile.am:55: invalid variable
`nodist_pkgdata_DATA'stage2/Makefile.am: nbloader_exec_OBJECTS should
not be definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: pxeloader_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: diskless_exec_OBJECTS should not be
definedstage2/Makefile.am: pre_stage2_exec_OBJECTS should not be
definedstage2/Makefile.am: start_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: e2fs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: fat_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: ffs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: jfs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: minix_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: reiserfs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: vstafs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not
definedstage2/Makefile.am: xfs_stage1_5_exec_OBJECTS should not be
definedstage2/Makefile.am: variable `LDADD' not defineddocs/Makefile.am:
kernel_OBJECTS should not be defineddocs/Makefile.am: variable `LDADD'
not definednetboot/Makefile.am:34: bad macro name
`3c509_drivers'netboot/Makefile.am:35: bad macro name
`3c595_drivers'netboot/Makefile.am:36: bad macro name
`3c90x_drivers'netboot/Makefile.am:187: bad macro name
`3c509_o_CFLAGS'netboot/Makefile.am:188: bad macro name
`3c529_o_CFLAGS'netboot/Makefile.am:189: bad macro name
`3c595_o_CFLAGS'netboot/Makefile.am:190: bad macro name
`3c90x_o_CFLAGS'netboot/Makefile.am:198: bad macro name
`3c507_o_CFLAGS'netboot/Makefile.am:206: bad macro name
`3c503_o_CFLAGS'

(This errors are generated by automake)> Am I doing something wrong? 

Other question:

Is somebody using the latest LILO which ?supports? DOC devices? If so,
what options must I add in lilo.conf, since I get the 
following at bootup:

L 01 01 01 01 01 01

I've been using lilo-mtd for a while and it boots the DOC with linux
ok. Only thing  is, it doen't look as if the commandline is
passed to the kernel. "cat /proc/cmdline" is empty. Does the newer LILO
versions correct this?


Thanks in advance for any help/info
Herman

****************************************
Herman Theron
Hermanus Magnetic Observatory
CSIR
PO Box 32
Hermanus
7200
South Africa
E-mail: hetheron@csir.co.za
Phone: +27 28 3121196
Fax: +27 28 3122039
Cel: +27 833 206 311

             reply	other threads:[~2002-02-22  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22  7:22 Herman Theron [this message]
2002-02-22 16:57 ` Error using GRUB patch (and LILO questions) Ilguiz Latypov
  -- strict thread matches above, loose matches on Subject: below --
2002-02-25  9:22 Herman Theron
2002-02-25 20:00 ` Ilguiz Latypov

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=sc760dea.038@CS-IMO.CSIR.CO.ZA \
    --to=hetheron@csir.co.za \
    --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