Cannot build grub for openbsd 3.7
Intel Dual Xeon EMT, SATA drives OpenBSD 3.7 GENERIC.MP#50 i386 gcc (GCC) 3.3.5 (propolice) binutils 2.15 Trying to build GRUB Legacy obtained by: $ export CVS_RSH=ssh $ cvs -z3 -d:ext:[EMAIL PROTECTED]:/cvsroot/grub co grub Attached is the config.log file. Also here is the make error: # make make all-recursive Making all in netboot Making all in stage2 if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -falign-jumps=1 -falign-loops=1 -falign-functions=1 -Wundef -Os -fno-stack-protector -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_UFS2=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DFSYS_JFS=1 -DFSYS_XFS=1 -DFSYS_ISO9660=1 -DUSE_MD5_PASSWORDS=1 -g -MT pre_stage2_exec-builtins.o -MD -MP -MF .deps/pre_stage2_exec-builtins.Tpo -c -o pre_stage2_exec-builtins.o `test -f 'builtins.c' || echo './'`builtins.c; then mv -f .deps/pre_stage2_exec-builtins.Tpo .deps/pre_stage2_exec-builtins.Po; else rm -f .deps/pre_stage2_exec-builtins.Tpo; exit 1; fi builtins.c: In function `blocklist_func': cc1: error: trampoline code generation is not allowed without -ftrampolines builtins.c: In function `install_func': cc1: error: trampoline code generation is not allowed without -ftrampolines cc1: error: trampoline code generation is not allowed without -ftrampolines cc1: error: trampoline code generation is not allowed without -ftrampolines builtins.c: In function `savedefault_func': cc1: error: trampoline code generation is not allowed without -ftrampolines *** Error code 1 Stop in /home/lvo/grub/stage2 (line 2268 of Makefile). *** Error code 1 Stop in /home/lvo/grub (line 269 of Makefile). *** Error code 1 Stop in /home/lvo/grub (line 191 of Makefile). Thank you Lu Vo [EMAIL PROTECTED] Superb Internet - Ahead of the Rest. http://www.superb.net config.log Description: Binary data ___ Bug-grub mailing list Bug-grub@gnu.org http://lists.gnu.org/mailman/listinfo/bug-grub
PXE-GRUB for OpenBSD hacks
I've updated my OpenBSD+Grub patches to be compatible to both a.out (up to 3.3) and elf (post 3.3) OpenBSD kernels. There is a few other improvements as well. Let me know about success, problems or any other feedback. Use at your own risk! http://www.berger.to/openbsd/pxegrub.html Cedric ___ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub
Re: Grub and OpenBSD?
At 14:53 09/08/00 -0500, E. Larry Lidz wrote: Pavel Roskin writes: Hello, Darren! I read on usenet that it does, you have to patch the code so it recognises A7 partition id for OpenBSD, just change whatever it expects to A7. Linux fdisk thinks that A7 is NeXTSTEP. Well, if both OpenBSD and NeXTSTEP use A7 for BSD disklabels it should be Ok to support it. Now A5, A6, A7 and A9 will be recognized as BSD disklabels. Anybody knows about A8? It would be nice to check a range. I think it's A6, not A7 for OpenBSD. At least, my (non-functional) OpenBSD partition is A6. I think that the patch he's refering to was for an older version of Grub, though I wouldn't swear to it. -Larry Yes, I meant A6 :-) Darren ---
Re: Grub and OpenBSD?
Pavel Roskin writes: What's the latest on using Grub (0.5.95) with OpenBSD (2.7)? I've tried both: root (hd0,2,a) kernel --type=openbsd /bsd and root (hd0,2,a) Also try root (hd0,2) makeactive chainloader +1 Also try chainloader --force +1 Alas, this still gives me "bad magic". It looks like that OpenBSD also expects some new interface to the bootloader. The idea of a unified bootloader doesn't seem to be popular among *BSD folks. Just what would it take for the OpenBSD to be more easily bootable from Grub? What's unclear to me is whether it won't boot natively because the OpenBSD people have a design objection to making it easier for Grub (and, presumably, other boot loaders) to boot it, or if it's just that the OpenBSD people don't know what needs to change. -Larry
Re: Grub and OpenBSD?
Hello! On Wed, 9 Aug 2000, E. Larry Lidz wrote: Also try chainloader --force +1 Alas, this still gives me "bad magic". Indeed, GRUB doesn't contain words "bad magic", so "--force" is irrelevant. It looks like that OpenBSD also expects some new interface to the bootloader. The idea of a unified bootloader doesn't seem to be popular among *BSD folks. Just what would it take for the OpenBSD to be more easily bootable from Grub? What's unclear to me is whether it won't boot natively because the OpenBSD people have a design objection to making it easier for Grub (and, presumably, other boot loaders) to boot it, or if it's just that the OpenBSD people don't know what needs to change. I'd like to hear it from OpenBSD/i386 people (architecture is important here, other architectures are not supported by GRUB). I think that the answer will be - we don't want to rely on third-party sources and standards as we have something that works well and something that we can modify at our will. I'm almost sure that the issue is a political one. Multiboot protocol doesn't have the necessary weight and recognition. GRUB is yet to deliver a stable version. For now the best way is to give every OS what it expects from its native bootloader. Then GRUB and (indirectly) the Multiboot protocol will have a chance to gain popularity and encourage OS vendors to use it. Another problem is that GRUB supports only one platform. Multiplatform support would make a huge difference for its acceptance by *BSD vendors. Regards, Pavel Roskin
Re: Grub and OpenBSD?
Pavel Roskin writes: Hello, Darren! I read on usenet that it does, you have to patch the code so it recognises A7 partition id for OpenBSD, just change whatever it expects to A7. Linux fdisk thinks that A7 is NeXTSTEP. Well, if both OpenBSD and NeXTSTEP use A7 for BSD disklabels it should be Ok to support it. Now A5, A6, A7 and A9 will be recognized as BSD disklabels. Anybody knows about A8? It would be nice to check a range. I think it's A6, not A7 for OpenBSD. At least, my (non-functional) OpenBSD partition is A6. I think that the patch he's refering to was for an older version of Grub, though I wouldn't swear to it. -Larry
Re: Grub and OpenBSD?
On Wed, Aug 09, 2000 at 02:47:02PM -0400, Pavel Roskin wrote: Just what would it take for the OpenBSD to be more easily bootable from Grub? What's unclear to me is whether it won't boot natively because the OpenBSD people have a design objection to making it easier for Grub (and, presumably, other boot loaders) to boot it, or if it's just that the OpenBSD people don't know what needs to change. I'd like to hear it from OpenBSD/i386 people (architecture is important here, other architectures are not supported by GRUB). I think that the answer will be - we don't want to rely on third-party sources and standards as we have something that works well and something that we can modify at our will. I'm quite sure the issue is, people are posting to the mailing lists who want GRUB support, but none of them have supplied workable patches yet. I looked for one in your posting, but didn't see it -- maybe you forgot to attach it? -- David Terrell | "Any sufficiently advanced technology Prime Minister, Nebcorp | is indistinguishable from a rigged demo." [EMAIL PROTECTED] | - Brian Swetland http://wwn.nebcorp.com/
Re: Grub and OpenBSD?
From: Pavel Roskin [EMAIL PROTECTED] Subject: Re: Grub and OpenBSD? Date: Mon, 7 Aug 2000 17:11:33 -0400 (EDT) It looks like that OpenBSD also expects some new interface to the bootloader. The idea of a unified bootloader doesn't seem to be popular among *BSD folks. The worst problem is that there is no substantive specification or protocol for *BSD bootstrap interface (AFAIK). I think the fact is one of the reasons why they often break the compatibility. I hope that *BSD developers will write specifications, like Linux/i386 boot protocol or the Multiboot Specification. Thanks, Okuji
Re: Grub and OpenBSD?
E. Larry Lidz writes: What's the latest on using Grub (0.5.95) with OpenBSD (2.7)? I've tried both: root (hd0,2,a) kernel --type=openbsd /bsd and root (hd0,2,a) makeactive chainloader +1 in my Grub configuration and neither seem to work. The first gives "/boot too old: upgrade" and the second gives "bad magic". You can't chainload from the `a' partition like this, try this instead, root (hd0,2) it worked for me with OpenBSD 2.7, the only problem I had was that the OpenBSD boot loader was not able to determine the root device properly, (I had chainloaded the (hd2,2) partition), so I had to use the `-a' boot time option, a real PITA, especially since grub cannot boot the OpenBSD kernel directly anymore (I am not complaining about this, just that it is the reason for your first method failing). -- Jeff Sheinberg [EMAIL PROTECTED]
Re: Grub and OpenBSD?
Hello! What's the latest on using Grub (0.5.95) with OpenBSD (2.7)? I've tried both: root (hd0,2,a) kernel --type=openbsd /bsd and root (hd0,2,a) Also try root (hd0,2) makeactive chainloader +1 Also try chainloader --force +1 in my Grub configuration and neither seem to work. The first gives "/boot too old: upgrade" and the second gives "bad magic". It looks like that OpenBSD also expects some new interface to the bootloader. The idea of a unified bootloader doesn't seem to be popular among *BSD folks. Regards, Pavel Roskin
