Arch Linux User Repository

Nice to see. Though, I can't promise that it will stay this way. The old GRUB code base is getting more and more incompatible with newer versions of GCC and binutils, and it may finally just build non-working binaries in the future.

Yes! I wasn't able to get this to compile under the address link error, but your PKGBUILD did the trick. God bless!

Does anyone still even use this?

I suspect the problem here is a gcc update. I would remove i686 from $arch, add lib32-glibc to depends, and see if other distros have released patches to work with newer gcc.

==> ERROR: A failure occurred in build().

=============================================================

$ sudo arch-nspawn $CHROOT/cody pacman -Syu

:: Synchronizing package databases...

core 130.2 KiB 256K/s 00:01 [#######################################] 100%

extra 1603.6 KiB 280K/s 00:06 [#######################################] 100%

community 4.2 MiB 398K/s 00:11 [#######################################] 100%

multilib 170.7 KiB 365K/s 00:00 [#######################################] 100%

:: Starting full system upgrade...

........

=============================================================

$ makechrootpkg -c -r $CHROOT

........

checking whether build environment is sane... yes

/build/grub-legacy/src/grub-0.97/missing: Unknown `--is-lightweight' option

Try `/build/grub-legacy/src/grub-0.97/missing --help' for more information

configure: WARNING: 'missing' script is too old or missing

checking for a thread-safe mkdir -p... /usr/bin/mkdir -p

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking whether make supports nested variables... yes

checking build system type... x86_64-unknown-linux-gnu

checking host system type... x86_64-unknown-linux-gnu

checking whether to enable maintainer-specific portions of Makefiles... no

checking for gcc... gcc

checking for gcc... (cached) gcc

checking whether the C compiler works... no

configure: error: in `/build/grub-legacy/src/grub-0.97':

configure: error: C compiler cannot create executables

See `config.log' for more details

==> ERROR: A failure occurred in build().

Aborting...

==> ERROR: Build failed, check /home/cody/chroot/cody/build

I am getting undefined reference to `__stack_chk_fail' on current Arch which I could fix with adding " -fno-stack-protector" to CFLAGs in the PKGBUILD

I need to have grub2 and grub-legacy installed side-by-side. Due to file conflicts, I assume the easiest way is to have grub-legacy installed in separate directory, say /usr/share/grub-legacy (which would serve as a / for this package). Could somebody please advise me how to do it with minimal effort, i.e. so that scripts, configurations, etc. would still work relative to new root? Specifically, I was looking into using "PREFIX", but I do not understand how the entire build chain works.

oh. I found what the problem was, had to do with using the SOL (serial over lan) from a Supermicro-board .. for the menu.lst, that means you should NOT specify terminal serial .. because that apparently doesn't work. after removing that line, it now works. yay!

mhellwig, I was in same situation some time ago during previous update of grub-legacy package. Spent some time trying to fix it and gave up finally - migrated to grub2. Actually I planned this migration earlier, because going to upgrade my laptop to something modern, which will came with EFI I suspect. So, maybe go with grub2 too?

so I've (re)installed this _after_ doing the filesystem switch, figuring then the symlinks for /bin and /sbin already exist and so installing there wouldn't be so bad since then it'd just get written to /usr/bin anyway. First attempt to boot: imagine my surprise when the system wouldn't come up because grub-legacy upon installation uses its own menu.lst and moved mine to menu.lst.pacsave. So wrong root, no cryptdevices and so forth. After fixing that manually (hitting "e" in the grub menu, typing in what I had written down somewhere) the system came up. Then I figured I want this to boot by itself (obviously) so I moved my old menu.lst.pacsave to menu.lst and hit reboot. And now this thing won't boot. Like, at all. It hangs at "GRUB loading stage 1.5 GRUB loading, please wait... <blinking cursor>" And that's it. So next step I got myself a grml iso (live-CD) and powercycled and used my ipmi console to mount that virtually and boot from it (yeah, it's a remote server ..) Mounted my ARCH system, chrooted to it, re-ran grub-install to /dev/sda, that went through without error. Reboot, system still won't come up, same error as above. Hangs at the "loading grub..." stage, no error code. What could be wrong? This system needs to be up half an hour ago ...