From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Problems booting Linux via PXE
Date: Fri, 03 Sep 2010 01:01:43 +0200 [thread overview]
Message-ID: <4C802CD7.10800@gmail.com> (raw)
In-Reply-To: <D1A3B6E525F5F943AB9D12DED819DD5F013EAFB4@NYCMBX3.winmail.deshaw.com>
[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]
On 08/27/2010 12:55 AM, Turner, Ian wrote:
>> On 08/25/2010 09:02 PM, Turner, Ian wrote:
>>
>>> I’m having some trouble using GRUB to boot Linux via PXE.
>>>
>
>> Could you try newreloc branch which is about to be merged?
>>
> The newreloc branch solved the problem and allowed me to successfully boot Linux, but I noticed a few other problems getting the branch to compile:
>
> 1. 'make dist' is totally broken; I think this is because some files were moved around or just removed (e.g., kern/i386/loader.S) and the build scripts were never updated.
>
>
I corrected the failure of make dist but it's still broken (some files
not included)
> 2. grub-core/kern/emu/misc.c seems to assume that libdevmapper will define dm_log_with_errno_init, which it does not on my system (RHEL 5.2). Configuring with --disable-device-mapper made this go away for me, since I don't need DM functionality.
>
Fixed.
> 3. It looks like grub does not compile properly if CFLAGS or LDFLAGS contains -m64 (standard in our environment); it's probably a good idea to consider checking for these at configure time.
>
>
CFLAGS and LDFLAGS should have no such effect. Perhaps you set TARGET_*
variables as well? Those are meant for cross-compiling (and we actualy
cross-compile). Setting them to anything other than the options for
target architecture (in this case i386) would have an unpredictable
effect. And there is no way our build system can check for every
possible annoying parameter. My recomendation is GRUB to be excluded
from any default compile flags at packaging level.
> Thanks for your help,
>
> --Ian
>
>
>
> _______________________________________________
> 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: 294 bytes --]
prev parent reply other threads:[~2010-09-02 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 19:02 Problems booting Linux via PXE Turner, Ian
2010-08-26 1:12 ` Omni Flux
2010-08-26 1:14 ` Omni Flux
2010-08-26 8:02 ` Omni Flux
2010-08-26 7:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-26 8:48 ` Omni Flux
2010-08-26 15:06 ` Bruce Edge
2010-08-26 21:27 ` Omni Flux
2010-08-26 22:55 ` Turner, Ian
2010-09-02 23:01 ` 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=4C802CD7.10800@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.