All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub-devel Digest, Vol 45, Issue 30
Date: Sun, 18 Nov 2007 07:54:45 +0100	[thread overview]
Message-ID: <20071118065445.GF20719@thorin> (raw)
In-Reply-To: <94a0ccbc0711150955r1a38cfe8jd1f26ad904da729c@mail.gmail.com>

On Thu, Nov 15, 2007 at 08:55:54PM +0300, Oleg Strikov wrote:
> Hi,
> 
> >Hi,
> 
> >On Nov 14, 2007 4:48 PM, Oleg Strikov <oleg.strikov@gmail.com> wrote:
> >> Good day!
> >> Ive created my own grub file validation module, but I can only make it by
> >> renaming to standart "hello module" :(
> >>
> >> What ive done:
> >> 1) add my module source into ./commands folder
> >> 2) add validate.mod to pkgdata_MODULES (common.rmk)
> >> 3) add some template data
> >>     # For validate.mod.
> >>     validate_mod_SOURCES = commands/validate.c
> >>     validate_mod_CFLAGS = $(COMMON_CFLAGS)
> >>     validate_mod_LDFLAGS = $(COMMON_LDFLAGS)
> >> to the same file
> >>
> >> What point ive forgotten?
> 
> >make sure you install "ruby".
> 
> >--
> >Bean
> 
> Thank you for your attention, but ive got ruby already :(
> ruby --version
> ruby 1.8.6 (2007-03-13 patchlevel 0) [i486-linux]

Did you check that your module makes its way into common.mk ?  If not, you
might need to regenerate that manually (with genmk.rb < common.rmk > common.mk).

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)



      parent reply	other threads:[~2007-11-18  6:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <473b2b28.1219360a.64b9.ffffcf33SMTPIN_ADDED@mx.google.com>
2007-11-15 17:55 ` Grub-devel Digest, Vol 45, Issue 30 Oleg Strikov
2007-11-15 19:00   ` HOWTO needed: how to add my own module to making list? adrian15
2007-11-15 20:43     ` Alexandre Boeglin
2007-11-16 18:11       ` Vincent Pelletier
2007-11-18  6:54   ` Robert Millan [this message]

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=20071118065445.GF20719@thorin \
    --to=rmh@aybabtu.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.