SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Next I tried to compile in 32bit-mode, following alienbob instructions:
move lib64 to lib in openmotif.Slackbuild
linking stops with error-message
/usr/lib64/gcc/x86_64-slackware-linux/4.4.4/../../../../lib/crt1.o: In function `_start':
/glibc-tmp-88b9835d8519e3638ef4d116a6932cb2/glibc-2.11.1/csu/../sysdeps/i386/elf/start.S:115: undefined reference to `main'
collect2: ld returned 1 exit status
Where is my mistake?
Specifically, where does /usr/lib64/gcc/ come from?
Porblem still not solved.
Any suggestions from the group?
I have a general solution, not just for your case but for all those cases where there are some problems in making a 32-bit build on a multilib system. Just build openmotif on a 32-bit system! For example, use chroot to run a 32-bit userspace under your 64-bit slackware just to build that package.
First, select a directory to install the 32-bit slackware, e.g. /home/yourname/slack32_13.1
Then put the 32-bit packages somewhere, for example /tmp/source (directories a, ap etc are in there)
Then, as root:
# make dir for new OS
# install the basic packages from 'a'
installpkg --root /home/yourname/slack32_13.1 /tmp/source/a/*.t?z
# make the package tree visible also inside the new OS
mount --bind /tmp/source /home/yourname/slack32_13.1/source
# go to the new basic 32-bit system
linux32 chroot /home/yourname/slack32_13.1 su - root
# now we are in the new OS. install "a" again, and all others
# now we are back in the parent system. clean up
Now you can go to the 32-bit system and back. For example:
# in the 64-bit parent os
cp openmotif-2.3.2.tar.gz openmotif.SlackBuild slack-desc /home/yourname/slack32_13.1/tmp
su -c 'linux32 chroot /home/yourname/slack32_13.1 su - root'
# in the 32-bit OS now
# now back in the 64-bit OS
cp /home/yourname/slack32_13.1/tmp/openmotif-2.3.2-i486-1alien.tgz .
# use convertpkg next if needed
Last edited by Petri Kaukasoina; 07-10-2010 at 11:52 AM.
Reason: Added "removepkg lesstif", c.f. Alien Bob's message #3