All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Georgi <patrick@georgi-clan.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] make grub2 compile with libc-less crosscompilers
Date: Sat, 19 May 2007 19:53:59 +0200	[thread overview]
Message-ID: <464F39B7.9080209@georgi-clan.de> (raw)
In-Reply-To: <200705191944.13081.okuji@enbug.org>

Yoshinori K. Okuji schrieb:
> On Saturday 19 May 2007 17:30, Patrick Georgi wrote:
>   
>> the target compiler that link libc (and potentially even more libs) -
>> which don't exist in my configuration.
>> As those are not necessary, I decided to modify grub2 instead of messing
>> around even more with the not-so-nice gcc build system.
>>     
>
> They are necessary. Otherwise, you cannot make a core image, for example. 
>   
uhm. where do you expect a target compiled file (ie. one that's run at 
boot time) to use libc?

I'm _not_ talking about the host compiler - here everything works fine, 
after all, there's no linker abuse going on there, just the average 
compile+link process.
> Also, without grub-emu, how do you plan to debug GRUB?
>   
qemu - the portions I work on need it anyway
> BTW I can hardly believe that it is so difficult to use gnu build tools on 
> solaris. Otherwise, how are opensolaris developers building GRUB?
>   
Compiling gcc 4.2 (or 4.1.2) with gnu as and gnu ld in the back end 
resulted in compile errors here, when I tried to do a "normal" build.

The grub (0.95 btw!) in the OpenSolaris tree features a parallel 
makefile hierarchy that uses /usr/sfw/bin/gcc (which uses Sun tools in 
the back end) and, it seems, manual invocations of gnu ld.
so here you are - they basically link by hand


Regards,
Patrick Georgi



  reply	other threads:[~2007-05-19 17:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19 15:30 [PATCH] make grub2 compile with libc-less crosscompilers Patrick Georgi
2007-05-19 17:44 ` Yoshinori K. Okuji
2007-05-19 17:53   ` Patrick Georgi [this message]
2007-05-20 17:45   ` Stefan Reinauer
2007-06-04 17:03   ` Patrick Georgi
2007-05-31 14:59 ` Patrick Georgi

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=464F39B7.9080209@georgi-clan.de \
    --to=patrick@georgi-clan.de \
    --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.