From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Standalone Application in GRUB
Date: Sun, 03 Jun 2012 21:14:43 +0200 [thread overview]
Message-ID: <4FCBB7A3.2010301@gmail.com> (raw)
In-Reply-To: <CAEcpi1+B-U-OyBsid=93z9fL8eSj_bjXAPwEWmEps54j0=27eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On 03.06.2012 21:00, Parul Aggarwal wrote:
> Hi Vladimir,
>
> I understand what you are saying and grub modules seems the right way to
> go.
>
> Other two apparoaches I can think of is:
>
> 1. Make our standalone appliaction totally independent of GRUB like
> memtest application. This way we can go with independent application
> .bin running.
You can always do this but you can't use GRUB functions this way.
>
> 2. If we statically link the grub libraries to our standalone
> application. We tried hello world program using grub_printf, and linked
> few grup static libraries. When we run the program the application got
> hanged. Seems its because of few undefined symbols used in
> grub_printf(). Now we are trying to link glibc (as grub_printf uses this
> library interally) static library which should resolve the hang issue.
>
Not going to work. GRUB is not intended to be statically linked in this
sense. GRUB doesn't use any glibc on runtime.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2012-06-03 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 6:44 Standalone Application in GRUB Parul Aggarwal
2012-05-31 9:46 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-31 10:03 ` Parul Aggarwal
2012-05-31 10:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-06-03 19:00 ` Parul Aggarwal
2012-06-03 19:14 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=4FCBB7A3.2010301@gmail.com \
--to=phcoder@gmail.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.