Grub Development Archive on 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>
Subject: Re: RTL Languages support
Date: Fri, 14 May 2010 10:52:51 +0200	[thread overview]
Message-ID: <4BED0F63.6030307@gmail.com> (raw)
In-Reply-To: <AANLkTinP8l363y8zESL8otSu3vdEb5xFfeih0SpWgvvf@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]

Yaron Shahrabani wrote:
>
>     Be sure to use gfxterm (insmod vbe; loadfont /unifont.pf2) because VGA
>     doesn't support any non-ASCII characters.
>
This should have been insmod vbe; loadfont /unifont.pf2; terminal_output
gfxterm
> I got into some building problems
> I installed flex and bison becuase I didn't have them and tried to
> build using "make"
> I got the following error:
> make: *** No rule to make target `grub_script.tab.h', needed by
> `all-local'.  Stop.
I've just successfully compiled it. Procedure is:
Cleaning:
bzr clean-tree --ignored
bzr clean-tree
Building:
./autogen.sh
./configure
make

Installing:
sudo make install
sudo grub-install /dev/sda

Be sure to have a LiveCD under the hand when booting experimental grub.
If it still fails can you tell your autotools versions and post complete
build log?
> There were some warning before but I guess they weren't so critical
> Do you have any idea what I should do next?
> I branched the 1603 revision from savannah
>  
>
>     http://lists.gnu.org/archive/html/grub-devel/2010-01/msg00092.html
>
>     >
>     > If nobody is familiar with that issue I will need some help with
>     > checking this out myself, what should I do?
>     >
>
>     > Kind regards,
>     > Yaron Shahrabani
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Grub-devel mailing list
>     > Grub-devel@gnu.org <mailto:Grub-devel@gnu.org>
>     > http://lists.gnu.org/mailman/listinfo/grub-devel
>     >
>
>
>     --
>     Regards
>     Vladimir 'φ-coder/phcoder' Serbinenko
>
>
>
>     _______________________________________________
>     Grub-devel mailing list
>     Grub-devel@gnu.org <mailto:Grub-devel@gnu.org>
>     http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>   


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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  reply	other threads:[~2010-05-14  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 23:59 RTL Languages support Yaron Shahrabani
2010-05-14  0:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-14  7:35   ` Yaron Shahrabani
2010-05-14  8:52     ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-06-14 13:33       ` Yaron Shahrabani
2010-06-14 13:41         ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-07-03 20:45           ` Yaron Shahrabani
2010-06-09 20:35 ` 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=4BED0F63.6030307@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox