[SOLVED] regression with elilo on slackware -current (x86 version)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Original Poster
Rep:
My system is a pure slackware system with:
RAM: 16 Go
Swap: 8 Go
doesn't exhaust qt5, and when I looked at the memory situation with htop, no saturation.
the line that fails is in Make.rules (34):
--------------
$(CC) $(INCDIR) $(CFLAGS) $(CPPFLAGS) -c $< -o $@
--------------
Distribution: Slackware64 {15.0,-current}, FreeBSD, stuff on QEMU
Posts: 457
Rep:
Just a thought: the elilo package ships with pre-built binary .efi files from 2018. The only thing that's actually compiled and packaged is eliloalt. Replacing the "make || exit 1" line in the SlackBuild with
Code:
cd tools
make || exit 1
cd ..
just builds eliloalt and leaves the rest alone. Would that compile successfully on a 32-bit machine?
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Original Poster
Rep:
In the SFS build tree I made this change in the SlackBuild:
Code:
# We will build this from source.
# However, we will package the pre-built EFI binaries, since we would
# like to include both 32-bit and 64-bit x86 EFI loaders in the
# finished package.
# modification to allow the package to be built on slackware version x86
case "$( uname -m )" in
x86_64)
make || exit 1 ;;
i686)
cd tools
make || exit 1
cd .. ;;
esac
It doesn't change anything for x86_64, and solves the x86 build version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.