All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Georgi <patrick@georgi-clan.de>
To: grub-devel@gnu.org
Subject: Re: Next release?
Date: Tue, 15 Jul 2008 17:07:34 +0200	[thread overview]
Message-ID: <g5iefb$g0k$1@ger.gmane.org> (raw)
In-Reply-To: <20080715134913.GB24537@thorin>

Robert Millan schrieb:
> On Mon, Jul 14, 2008 at 06:55:24PM +0200, Christian Franke wrote:
>> The first (and last) grub package released in the Cygwin distribution 
>> was based on grub codebase from 2008-03-26. My latest reasonably tested 
>> merge is ~2 month old. If desired, I can merge & test all remaining 
>> changes to current HEAD and post the patches for review soon.
> 
> Great!
> 
> As for the loader issue, did you find a way to generate images in ELF format
> from the Cygwin system?
I do all the time with an i386-elf cross compiler. the easiest way to 
generate one (in my experience) is to create a directory with symlinks to:
- gcc/*
- binutils/* (ignore duplicates)
- gcc/include/* (into include/, after removing the symlink to 
gcc/include and creating a directory in its place)
- binutils/include/* (again, ignore duplicates)

then configure --enable-languages=c --disable-bootstrap from that 
directory of symlinks, and you'll get a full binutils+gcc build (if you 
want gdb, it should be enough to create symlinks to its files, but I 
didn't test that)

at least for coreboot, binutils must be of version 2.18.50.* (eg. as 
found with mingw), gnu's 2.18 isn't enough. no idea if that applies to 
grub2 or not.

as for the start/_start tests, I merely let configure default to _start 
if no other symbol was found, which might break grub-emu, but builds the 
target system grub just fine here. with i386-elf, the target compiler 
has no crt*.o anyway.


Regards,
Patrick Georgi




  reply	other threads:[~2008-07-15 15:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 13:03 Next release? Pavel Roskin
2008-07-14 16:55 ` Christian Franke
2008-07-14 20:27   ` Pavel Roskin
2008-07-15  5:40     ` Christian Franke
2008-07-20 21:10     ` Christian Franke
2008-07-15 13:49   ` Robert Millan
2008-07-15 15:07     ` Patrick Georgi [this message]
2008-07-15 18:39       ` Christian Franke
2008-07-15 18:32     ` Christian Franke
2008-07-15 21:04 ` Yoshinori K. Okuji
2008-07-15 22:31   ` Pavel Roskin
2008-07-15 23:15     ` Yoshinori K. Okuji
2008-07-15 23:21       ` Pavel Roskin
2008-07-15 23:32         ` Yoshinori K. Okuji
2008-07-15 23:52           ` Pavel Roskin
2008-07-16 14:11             ` Colin D Bennett
2008-07-16 14:17               ` Javier Martín
2008-07-16 16:17                 ` Pavel Roskin
2008-07-16 16:28                   ` Javier Martín
2008-07-16 16:08               ` Pavel Roskin
2008-07-19 15:14                 ` device.map (Re: Next release?) Robert Millan
2008-07-21 21:26                   ` Pavel Roskin
2008-07-22 21:36                     ` Robert Millan
2008-07-22 21:57                       ` Pavel Roskin
2008-07-22 22:08                         ` Robert Millan
2008-07-22 22:46                           ` Pavel Roskin
2008-07-19 15:06           ` Next release? Robert Millan
2008-07-19 20:16             ` Yoshinori K. Okuji
2008-07-19 20:59               ` Robert Millan
2008-07-21 20:48               ` Pavel Roskin
2008-07-22 21:37                 ` Robert Millan
2008-07-22 22:01                   ` Pavel Roskin
2008-07-22 22:09                     ` Robert Millan
2008-07-22 22:41                       ` Pavel Roskin
2008-07-24 17:02 ` Marco Gerards
2008-07-24 17:18   ` Pavel Roskin
2008-07-24 21:47     ` Christian Franke
  -- strict thread matches above, loose matches on Subject: below --
2008-07-16  0:22 chaac

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='g5iefb$g0k$1@ger.gmane.org' \
    --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.