Tiny Core Base > CorePlus
My last (I promise) tantrum: is it possible to run gcc on a Pentium 166?
Rich:
Hi t18
--- Quote from: t18 on May 26, 2025, 10:44:39 AM --- ... They seems to get ignored: no change in the Makefile. ...
--- End quote ---
What you posted ended with:
--- Code: ---#### End of system configuration section. ####
--- End code ---
which suggests there was more to the Makefile. Without seeing
the actual commands, we don't know which variables are being
used or how they are being used.
CNK:
It looks like you're not compiling Xterm in Tiny Core since the paths to libs in that Makefile aren't in /usr/local.
Even though you're using dynamic linking GCC will still use object files like crtbeginS.o which are compiled with GCC using the build settings of your distro (probably for later CPUs than P166). If you boot your i5 PC to x86 Tiny Core and compile there, it should work. Or if you're really adventurous you could try copying the Tiny Core GCC extension's begin/end object files (crtbegin.o, crtbeginS.o, crtend.o, crtendS.o) over to your other distro and make the compiler link to them there, but that's likely to anger the gods.
To confirm, change to the GCC lib directory in the distro where you're building Xterm (eg. /usr/lib/gcc or /usr/lib/gcc-lib) and run this command to show the build settings for the crtbeginS.o file for installed GCC versions:
--- Code: ---find -name crtbeginS.o -exec file '{}' \;
--- End code ---
I'm guessing it will be for a later architecture than i586 (Pentium 1).
t18:
--- Quote from: Rich on May 26, 2025, 08:09:11 PM ---Hi t18
--- Quote from: t18 on May 26, 2025, 10:44:39 AM --- ... They seems to get ignored: no change in the Makefile. ...
--- End quote ---
What you posted ended with:
--- Code: ---#### End of system configuration section. ####
--- End code ---
which suggests there was more to the Makefile. Without seeing
the actual commands, we don't know which variables are being
used or how they are being used.
--- End quote ---
Yes it's quite long. Please find it attached.
t18:
--- Quote from: CNK on May 26, 2025, 08:30:18 PM ---It looks like you're not compiling Xterm in Tiny Core since the paths to libs in that Makefile aren't in /usr/local.
--- End quote ---
Yes, indeed I've compiled it on Slackware 15 (it hosts Virtualbox with TC on it).
Sometimes compiling succeeds on Slackware (gcc 11.2.0) and not on TC 15, or viceversa.
Libptytty-2.0 is an example. Although I've found the Juanito's direction: https://forum.tinycorelinux.net/index.php/topic,26669.msg172032.html#msg172032 it hasn't worked for me on TC.
Elsewhere, on Slackware I had problems with the -march option some time ago, while it worked great on TC.
--- Quote ---Even though you're using dynamic linking GCC will still use object files like crtbeginS.o which are compiled with GCC using the build settings of your distro (probably for later CPUs than P166). If you boot your i5 PC to x86 Tiny Core and compile there, it should work. Or if you're really adventurous you could try copying the Tiny Core GCC extension's begin/end object files (crtbegin.o, crtbeginS.o, crtend.o, crtendS.o) over to your other distro and make the compiler link to them there, but that's likely to anger the gods.
--- End quote ---
That's way beyond my capabilities (and my available time).
--- Quote ---To confirm, change to the GCC lib directory in the distro where you're building Xterm (eg. /usr/lib/gcc or /usr/lib/gcc-lib) and run this command to show the build settings for the crtbeginS.o file for installed GCC versions:
--- Code: ---find -name crtbeginS.o -exec file '{}' \;
--- End code ---
I'm guessing it will be for a later architecture than i586 (Pentium 1).
--- End quote ---
Here you are:
--- Code: ---bash-5.1$ find -name crtbeginS.o -exec file '{}' \;
./crtbeginS.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped
./32/crtbeginS.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV), not stripped
--- End code ---
t18:
--- Quote from: CNK on May 26, 2025, 08:30:18 PM ---If you boot your i5 PC to x86 Tiny Core and compile there, it should work.
--- End quote ---
Anyway:
Xterm compiled on Slackware (just for my convenience) for 32 bit and put on Virtualbox-TC works great. I just had to link libtinfo to libncursesw.
The same binary put on P166 shows the above errors.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version