All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Robert Schumann <schumann@informatik.hu-berlin.de>
Subject: Re: grub 1.99 add own module / dep problem
Date: Thu, 09 Feb 2012 12:13:48 +0100	[thread overview]
Message-ID: <4F33AA6C.8060101@gmail.com> (raw)
In-Reply-To: <4F33963E.1070406@informatik.hu-berlin.de>

On 09.02.2012 10:47, Robert Schumann wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Heyho guys!
>
> I'm sorry if I didn't RTFM somewhere but I just couldn't find _any_
> information on how to correctly add/patch own modules into the grub
> 1.99. The problem:
>
> 1. mymod.c depends on a function in biosdisk.c
Avoid this as much as possible. Biosdisk is arch-specific, use generic 
disk functions.
> 2. mymod.c includes the biosdisk.h header correctly I suppose
> 3. I patched grub-core/Makefile.core.def with
>
> module = {
>    name = mymod;
>    common = mymod/mymod.c;
>    enable = biosdisk;
enable=i386_pc; not biosdisk
> };
>
> 4. I patched grub-core/Makefile.core.am with basically a copy from the
> hello.c module stuff (although I should probably take the arch
> dependend definitions from biosdisk mod? but I'm building i386 so it
> should work any way?)
Don't touch this file. Just rerun ./autogen.sh
>
> 5. ./configure&&  make works as expected for another module which
> doesn't include a foreign function.
>
> 6. For mymod.c I receive
> mymod/mymod.c:68: error: implicit declaration of function
> 'grub_biosdisk_get_diskinfo_standard'
This function is static ("private"). Moreover it's for very old C/H/S 
addressing.
Looks like you're going the wrong way. Can you detail what's your end goal?
> which is of course in biosdisk.c. Now my question: How do I solve this
> mystery on a code/patch base? ;) I know that I can add the biosdisk.c
> to the common code functions, but that shouldn't be necessary, huh? I
> thought that enable = biosdisk would do the trick with linked
> functions, but well... maybe you could shed some light on it.
Dependencies are tracked automatically.
>
> Cheers
> Robert
>
> - -- 
>
> |-------------------------------------------------address-+
> | work:  jacob-und-wilhelm-grimm-zentrum
> |        geschwister-scholl-str. 1, 10117 berlin
> | mail:  humboldt-universität zu berlin
> |        computer- und medienservice
> |        unter den linden 6, 10099 berlin
> |-------------------------------------------------contact-+
> | mail:  schumann@informatik.hu-berlin.de
> | icq:   93163687  |  xmpp:  betulichergutmensch@gmail.com
> | fb: 	 fb.com/rschumann  |  phone:  +49(0)30-2093-70133
> |-------------------------------------------------gpg/pgp-+
> | key:   remembrance.de/gpg/0xA5A5FAA2.asc
> | fprnt: 9220-9732-7390-7A0C-5623-3336-4233-FDF8-A5A5-FAA2
> |---------------------------------------------------------+
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk8zljkACgkQQjP9+KWl+qLypgCfb6Hbwo8YwvjTbGg7h9BVKZJd
> QNQAoLSsg7RhpsZ/ovACGkuO42JpZozI
> =oLeZ
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



  reply	other threads:[~2012-02-09 11:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  9:47 grub 1.99 add own module / dep problem Robert Schumann
2012-02-09 11:13 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-02-09 11:59   ` Robert Schumann
2012-02-09 12:11     ` Vladimir 'φ-coder/phcoder' Serbinenko

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=4F33AA6C.8060101@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=schumann@informatik.hu-berlin.de \
    /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.