Grub on Slack64

rvdboom · 06-09-2009, 05:10 AM

Hi!

Is there any particular technical reason why grub is not currently included in Slackware64?
Or is just because the devs don't see the point right now? In this case, is there any particular danger in compiling the slackware-current Slackbuild in 64bits?

Thanks for any answer!

rvdboom · 06-09-2009, 07:32 AM

OK, I just saw that it's available in extra/source.
Don't know why there's no package though. Any issue with that?

ringwraith · 06-09-2009, 04:50 PM

Probably not included because lilo works. Most long time Slack users still write their lilo.conf by hand and we wouldn't want to be confused with something else.

Alien Bob · 06-09-2009, 04:51 PM

Just try to build the source in slackware64-current/extra/source/grub

Eric

rvdboom · 06-10-2009, 12:43 AM

Hi, Eric.
Configure fails for me. config.log file says this :

Code:

his file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by GRUB configure 0.97, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ ./configure --prefix=/usr --infodir=/usr/info --mandir=/usr/man

## --------- ##
## Platform. ##
## --------- ##

hostname = coyote
uname -m = x86_64
uname -r = 2.6.30-rc8-vdb
uname -s = Linux
uname -v = #3 SMP PREEMPT Sat Jun 6 01:40:00 CEST 2009

/usr/bin/uname -p = AMD Phenom(tm) II X4 810 Processor
/bin/uname -X     = unknown

/bin/arch              = x86_64
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
hostinfo               = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /usr/sbin
PATH: /sbin
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/games
PATH: /usr/lib64/java/bin
PATH: /usr/share/texmf/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1434: checking for a BSD-compatible install
configure:1489: result: /usr/bin/ginstall -c
configure:1500: checking whether build environment is sane
configure:1543: result: yes
configure:1608: checking for gawk
configure:1624: found /usr/bin/gawk
configure:1634: result: gawk
configure:1644: checking whether make sets $(MAKE)
configure:1664: result: yes
configure:1839: checking build system type
configure:1857: result: x86_64-unknown-linux-gnu
configure:1865: checking host system type
configure:1879: result: x86_64-unknown-linux-gnu
configure:1903: checking whether to enable maintainer-specific portions of Makefiles
configure:1912: result: no
configure:2028: checking for gcc
configure:2044: found /usr/bin/gcc
configure:2054: result: gcc
configure:2112: checking for gcc
configure:2138: result: gcc
configure:2382: checking for C compiler version
configure:2385: gcc --version </dev/null >&5
gcc (GCC) 4.3.3
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2388: $? = 0
configure:2390: gcc -v </dev/null >&5
Reading specs from /usr/lib64/gcc/x86_64-slackware-linux/4.3.3/specs
Target: x86_64-slackware-linux
Configured with: ../gcc-4.3.3/configure --prefix=/usr --libdir=/usr/lib64 --enable-shared --enable-bootstrap --enable-languages=ada,
c,c++,fortran,java,objc --enable-threads=posix --enable-checking=release --with-system-zlib --disable-libunwind-exceptions --enable-
__cxa_atexit --enable-libssp --with-gnu-ld --verbose --disable-multilib --target=x86_64-slackware-linux --build=x86_64-slackware-lin
ux --host=x86_64-slackware-linux
Thread model: posix
gcc version 4.3.3 (GCC)
configure:2393: $? = 0
configure:2395: gcc -V </dev/null >&5
gcc: '-V' option must have argument
configure:2398: $? = 1
configure:2421: checking for C compiler default output file name
configure:2424: gcc -m32 -O2   conftest.c  >&5
/usr/lib64/gcc/x86_64-slackware-linux/4.3.3/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/lib64/gcc/x86_64-s
lackware-linux/4.3.3/libgcc.a when searching for -lgcc
/usr/lib64/gcc/x86_64-slackware-linux/4.3.3/../../../../x86_64-slackware-linux/bin/ld: cannot find -lgcc
collect2: ld returned 1 exit status
configure:2427: $? = 1

I guess the -m32 option in the gcc compiling test is causing it.
Does this mean one should only compile grub in 32bits?

EDIT : OK, after some looking around, it indeed seems like grub must be compiled in 32bits right now.
Well, never mind, I'll wait for 32bits support or keep on using Lilo.

sahko · 06-10-2009, 10:06 AM

GRUB doesnt build on x86_64. It needs to be statically built on x86.
PS. GRUB2 is in the same state.

lumak · 06-10-2009, 02:32 PM

can't one install the compatibility libs from slamd64's slackware64-current repository? I believe this is why -m32 would be included in the configure flags. It forces it to build 32 bit binaries... I haven't tested it personally but you may also need to export PKG_CONFIG_PATH to be /usr/lib. Otherwise it still may try to use the 64 bit libs.

Alien Bob · 06-10-2009, 02:56 PM

Remember that there is a grub in slackware-current that you can use. It is all still Slackware - it's just that there are two ports.

Eric

rvdboom · 06-11-2009, 12:57 AM

Yes but it is dynamically linked to some 32bits libs and thus requires 32-bits compatibility packages..... Ahem ahem... :-D
Well, I've done that and copied manually the required libs, I'll see how it turns out tonight.
Thanks for the answers, guys!

slackass · 06-11-2009, 07:00 AM

I've been using the grub from -Current to boot SW64-C on a ext4 partition with no problems.