Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: trouble installing grub on -current amd64



I think I will send in a PR, and use i386 for now

On Thu, Jun 19, 2008 at 5:24 AM, Michael Litchard <michael%schmong.org@localhost> wrote:
It seems some mails have been going to individuals, and not the list.




here's what I see right now
25000      1 sh       NAMI  "/usr/pkg/sbin/grub"
 25000      1 sh       NAMI  "/emul/netbsd32"
 25000      1 sh       NAMI  "/emul/netbsd32/usr/libexec/ld.elf_so"
 25000      1 sh       NAMI  "/usr/libexec/ld.elf_so"
 25000      1 sh       RET   execve -1 errno 8 Exec format error



and 
# file /emul/netbsd32/libexec/ld.elf_so    
/emul/netbsd32/libexec/ld.elf_so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), for NetBSD 4.0, not stripped
this file seems to be the problem.
what next?


On Wed, Jun 18, 2008 at 1:36 PM, Michael Litchard <michael%schmong.org@localhost> wrote:
From an earlier post


We (Liz mostly) have set up an amd64 box with current and xen3, and grub
works after installing a binary package built on i386, and the
netbsd/i386 shared libraries that it needs.

So if it works for them, how can I get it to work for me?

On Wed, Jun 18, 2008 at 8:09 PM, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
On Wed, Jun 18, 2008 at 07:46:53AM -0400, Greg Troxel wrote:
>   I am now running -current, as the Howto says you should
>   when using amd64# ktrace -f grub.out grub-install /dev/rwd0d
>   /usr/pkg/sbin/grub-install: Cannot execute ELF binary /usr/pkg/sbin/grub
>   sed: /grub/device.map: No such file or directory
>   grep: /grub/device.map: No such file or directory
>   /dev/rwd0d does not have any corresponding BIOS drive.
>
> We (Liz mostly) have set up an amd64 box with current and xen3, and grub
> works after installing a binary package built on i386, and the
> netbsd/i386 shared libraries that it needs.  The problem seems to be
> that grub builds i386 code for boot time, but doesn't use cross tools to
> do so.  I suspect that the grub setup part could be amd64 native.

From memory, there's a large part of code shared between the standalone
code and the grub setup part (it includes the standalone command line
interpreter), and this shared code is full of __asm() which isn't at all
x86_64-compatible.

--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
    NetBSD: 26 ans d'experience feront toujours la difference
--





Home | Main Index | Thread Index | Old Index