Tiny Core Linux
Tiny Core Base => CorePlus => Topic started by: Richard Cranium on July 25, 2024, 01:56:46 PM
-
Boinc isn't available in the package manager? Is there any other way to install it???
-
The source code is available on GitHub.
-
The source code is available on GitHub.
Unfortunatly, That dosen't really do me any good. about a thousand files there. and not really a good way to get the ones i need (if i even knew what i needed ) onto the machine that would be running Boinc...
-
had a free minute and browsed this webpage. interesting.
https://boinc.berkeley.edu/wiki/Installing_on_Linux
-
had a free minute and browsed this webpage. interesting.
https://boinc.berkeley.edu/wiki/Installing_on_Linux
Yeah , But no way to download it.
-
But no way to download it.
it appears the whey is
"The Berkeley Installer is available directly from the BOINC project. " ---> .boinc.berkeley.edu/download.php ---> · All versions ---> .boinc.berkeley.edu/download_all.php
so you mist be low on will ?
(where there's a will there's a whay) ;D
-
But no way to download it.
it appears the whey is
"The Berkeley Installer is available directly from the BOINC project. " ---> .boinc.berkeley.edu/download.php ---> · All versions ---> .boinc.berkeley.edu/download_all.php
so you mist be low on will ?
(where there's a will there's a way) ;D
Try to download a package, i can't , the files are corrupt. just shows up as a bunch of garbled nonsense.
so you mist be low on will ?
not sure what this means .
-
Hi Richard Cranium
I downloaded the x86 version 7.4.22 from here:
https://boinc.berkeley.edu/download_all.php
After placing it in my home directory I ran:
tc@E310:~$ sh boinc_7.4.22_i686-pc-linux-gnu.sh
use /home/tc/BOINC/run_manager to start BOINC
tc@E310:~$When I tried to start it, I got this:
tc@E310:~$ /home/tc/BOINC/run_manager
./boincmgr: error while loading shared libraries: libwebkitgtk-1.0.so.0: cannot open shared object file: No such file or directory
tc@E310:~$webkitgtk-1.0-0.tcz is not available in TC10. It was last available in TC4, but has so
many dependencies I doubt it would work if copied over. So that's where I stopped.
-
I tried compiling boinc-8.0.4, but it requires wxwidgets >= 3.1.3, whereas we have wxwidgets-3.0.4 in the x86 repo and wxwidgets-3.2.4 in the x86_64 repo.
You could try one of the pre-compiled packages available here: https://github.com/BOINC/boinc/releases, but I'm not sure they'd work.
If you are really desperate for boinc, I can try updating wxwidgets to, say, 3.1.7 in the x86 repo.
-
Hi Juanito
... You could try one of the pre-compiled packages available here: https://github.com/BOINC/boinc/releases, but I'm not sure they'd work. ...
There was also a thread in 2012 where BOINC wouldn't run because
it was compiled against too new a version of libc.so:
https://forum.tinycorelinux.net/index.php/topic,6994.msg80376.html#msg80376
-
boinc posted to tc-15.x x86 repo
-
boinc posted to tc-15.x x86 repo
Sorry for the late reply , OK so here's what's happened . booted newest version of TC same as before . Live , It's not installed yet (because i wanted to make sure boinc would work ) Found boinc in the TC repo , Set it to install , it installed , Clicked on the "boinc" icon on the bottom panel (what is the panel called?) , it didn't launch , so i rebooted and tried reinstall.
boinc won't show up in the repo now. did i screw up something???
-
The boinc extension is definately still in the repo..
As you found out, when you reboot a live install, everything you had is lost - you might want to install to a usb stick or similar using tc-install from thr CorePlus iso.
If something does not start by clicking on an icon, you can open a terminal window and start it from there to check for errors - enter "boincmgr <cr>" in this case.
The window bar is called wbar.
-
The boinc extension is definately still in the repo..
As you found out, when you reboot a live install, everything you had is lost - you might want to install to a usb stick or similar using tc-install from thr CorePlus iso.
If something does not start by clicking on an icon, you can open a terminal window and start it from there to check for errors - enter "boincmgr <cr>" in this case.
The window bar is called wbar.
Thank You , I will reply back soon.
-
The boinc extension is definately still in the repo..
Ok , I'm Either doing this completely the wrong way OR Boinc isn't available . ???
I've installed TC 15.0 to sda1 and it boots. Ethernet is working . I checked my router settings for traffic coming from that machine (TC) and the router sees it.
i search for Boinc in the repo and it dosen't show up. but it's wierd that other things show up , i typed random words and had search results. so that makes me think that I AM actually connected to the repo and that i have correctly used the package manager search function. :)
So got to thinking that I'd boot up an older version of TC and give it go (version 10.1), Oddly enough it dosen't find the Boinc package either.
???
-
Hi Richard Cranium
What response do you get from this command:
tce-load -wi boinc
-
@Richard Cranium Please run the following command and return its response:
uname -rIF it returns anything that ends in tinycore64 you simply have the wrong platform installed; @Juanito built the boinc extension for x86, not x86_64 (however 86_64 should be available in the somewhat near future IF everything compiles correctly.)
versionIf it returns anything other than 15.## we're running the wrong version of TCL
tce-load -wi wxwidgets31.tczThis is a dependency of boinc; if this also returns a Not Found error, you're very likely running x64 instead of x86
If it downloads and installs, we may have a different issue.
-
Hi Richard Cranium
What response do you get from this command:
tce-load -wi boinc
Since i don't have a browser installed i can't log into the forum from that machine , so i wrote i down...
downloading boinc.tcz
connecting to distro.ibiblio.org 152.19.134:80
wget server returned error
404 not found
no such file or directory
-
@Richard Cranium Please run the following command and return its response:
uname -rIF it returns anything that ends in tinycore64 you simply have the wrong platform installed; @Juanito built the boinc extension for x86, not x86_64 (however 86_64 should be available in the somewhat near future IF everything compiles correctly.)
no i'm running on 32 bit.
-
/opt/tcemirror needs to be changed back to its default
http://repo.tinycorelinux.net/
Ibiblio does not yet have the updates that were created specifically for you.
-
/opt/tcemirror needs to be changed back to its default
http://repo.tinycorelinux.net/
Ibiblio does not yet have the updates that were created specifically for you.
So i'm using the wrong mirror???
-
Not "wrong" necessarily... they just don't have Boinc yet since it was custom created for you specifically.
Additionally, as soon as you have Boinc installed, you can revert back to Ibiblio if you'd like.
-
/opt/tcemirror needs to be changed back to its default
http://repo.tinycorelinux.net/
Ibiblio does not yet have the updates that were created specifically for you.
OH MY GOSH , it worked that time.! it's installed , but it won't launch..!
terminal output ==> "illegal instruction"
The boinc extension is definately still in the repo..
If something does not start by clicking on an icon, you can open a terminal window and start it from there to check for errors - enter "boincmgr <cr>" in this case.{/quote]
-
@Richard: I have no history with the extension so I could be way off with assumptions; just for giggles, try to launch the manager app with root privileges:
sudo boincmgrIt probably is unrelated due to the type of error reported, but there's always that 0.0003% of a chance.
Normally, IOp Errors happen when they're trying to do something they're not allowed to do or the direction they're trying to take doesn't exist. (Laymen's terms at least!) As such, there's a good chance one or more of the many, many, many dependencies may in fact be too "new" where functions that used to exist simply don't exist or they have been changed and now act differently, or, with that fraction of a percent chance, they may now have elevated privileges today where they didn't back then, so the "sudo" above should cross that option off.
-
Hi Richard Cranium
Illegal instruction means the program contains an instruction that
your CPU does not support. For instance, if your CPU is an i486 and
it encounters an instruction meant for an i686 CPU, you will receive
that error.
That can occur if the compiler let's an unsupported instruction slip
through. It can also happen if the program being compiled requires
a later CPU that supports certain instructions.
-
It would help if you could paste the illegal instruction text from the terminal here as well as any relevant text from dmesg (dmesg | grep illegal).
The above would help determine whether the illegal instruction is due to boinc, wxwidgets or something else.
Could you also let us know what kind of cpu you have.
-
It would help if you could paste the illegal instruction text from the terminal here as well as any relevant text from dmesg (dmesg | grep illegal).
The above would help determine whether the illegal instruction is due to boinc, wxwidgets or something else.
working on that right now.
Could you also let us know what kind of cpu you have.
pentium 3 , 700 mhz
yeah i realize that's fairly old and slow., but like i said before , i'm just trying to give this old machine something to do...
Hi Richard Cranium
Illegal instruction means the program contains an instruction that
your CPU does not support. For instance, if your CPU is an i486 and
it encounters an instruction meant for an i686 CPU, you will receive
that error.
That can occur if the compiler let's an unsupported instruction slip
through. It can also happen if the program being compiled requires
a later CPU that supports certain instructions.
see above.. but isn't P3 a 686 cpu????
-
screenshots..
-
Hi Richard Cranium
... see above.. but isn't P3 a 686 cpu????
OK, I'l try this again.
For instance For example, if your CPU is a P3 and it
encounters an instruction a P4 CPU supports (SSE2 for example),
you will receive that error.
-
Hi Richard Cranium
... see above.. but isn't P3 a 686 cpu????
OK, I'l try this again.
For instance For example, if your CPU is a P3 and it
encounters an instruction a P4 CPU supports (SSE2 for example),
you will receive that error.
Yes I read that before.
But what are you really trying to say?? Because , I didn't think we've established that I'm running the wrong architecture.
@Juanito built the boinc extension for x86, not x86_64
and that's what i'm running..
-
Hi Richard Cranium
... But what are you really trying to say?? ...
I'm trying to explain to you what it means when you try
to run a program and you get an illegal instruction
message.
... Because , I didn't think we've established that I'm running the wrong architecture. ...
Getting an illegal instruction message has nothing to do with architecture. Trying to run
an executable for the wrong architecture does not produce that message.
-
@Richard: I'm not seeing an illegal instruction, I'm seeing a missing library (a bit of a different monster.)
What this basically means is that one of Bionic's many dependencies is either not being found, not installed, does not have appropriate links (for newer libraries, usually), etc.
Try this for the time being:
tce-load -wi libXss.tcz
-
Hi CentralWare
I don't see an illegal instruction either. I only commented on
it because the OP claimed it occurred.
-
i just got the dmesg error.
webkit2gtk-4.0.so
sorry , i tried several times to post the screenshot , it just wouldn't go through...
-
@Richard: I'm not seeing an illegal instruction, I'm seeing a missing library (a bit of a different monster.)
What this basically means is that one of Bionic's many dependencies is either not being found, not installed, does not have appropriate links (for newer libraries, usually), etc.
Try this for the time being:
tce-load -wi libXss.tcz
i'll try .
-
@Richard: I'm not seeing an illegal instruction, I'm seeing a missing library (a bit of a different monster.)
What this basically means is that one of Bionic's many dependencies is either not being found, not installed, does not have appropriate links (for newer libraries, usually), etc.
Try this for the time being:
tce-load -wi libXss.tcz
I run that command and the terminal says it's already installed.
I'm really confused here as to why it won't run.. it's installed...
-
Thank you for your results.
tce-load -i libXssPlease note whether or not it says it's already installed with just -i
If it says "OK" try your app again. If not, please enter the following:
cd /; sudo find -name libXss*.*...and post your results, if any.
The file listing page for the library says the file you're looking for should be located at /usr/local/lib/libXss.so along with two of its siblings, so.1 and so.1.0.0
If you're still having troubles with this specific library, please confirm its existence there.
I'm preparing a test machine for this situation in a few minutes, but I leave in about an hour and will be gone for a couple days out of the area and cannot assume I'll have time for volunteering while I'm gone. If you're still having troubles with your extension when I return I'll get it installed on the test machine and dig through the situation if one of the staff hasn't already found a solution.
-
libXss was missing from the boinc dep file - added.
-
Trip got delayed until 7am... things happen for a reason!?
Fresh install of 15.x86
This is my software extension list (onboot.lst)
Xvesa.tcz
aterm.tcz
flwm_topside.tcz
flwm.tcz
wbar.tcz
icewm.tcz
jwm.tcz
fluxbox.tcz
hackedbox.tcz
openbox.tcz
tc-install-GUI.tcz
kmaps.tcz
wifi.tcz
iw.tcz
boinc.tcz
boincmgr opens and runs as expected up to the point of it asking for a project URL, which I do not have, so I cannot test further.
REMOVE boinc from your machine and reinstall it - you should be operational now.
-
alright , I reinstalled Boinc and now i'm getting the "illegal instruction" error again, but only after about 15 -20 seconds goes by and the hard drive is clicking like mad. so that's different than last time...
I'll post the results of CentralWare suggested , shortly.
-
It would help if you could post the full text of the illegal instruction error.
-
@Richard: Before you continue any further, you should really run a scan on your hard drive to make sure it's healthy.
tce-load -wi smartmontools.tczOnce SMART is installed, do a quick scan of the drive (which I am assuming is /dev/sda, correct the command if I am assuming incorrectly)
sudo smartctl -H /dev/sdaThis is a very generic self-test and takes all of a second to complete.
-
It would help if you could post the full text of the illegal instruction error.
That's literally all it says.
Terminal output.
tc@box:~$ sudo boincmgr
illegal instruction
tc@box:~$
-
@Richard: Before you continue any further, you should really run a scan on your hard drive to make sure it's healthy.
tce-load -wi smartmontools.tczOnce SMART is installed, do a quick scan of the drive (which I am assuming is /dev/sda, correct the command if I am assuming incorrectly)
sudo smartctl -H /dev/sdaThis is a very generic self-test and takes all of a second to complete.
installed and ran ... test result says "PASSED"
PS... I do appreciate all the help so far...
-
PS... I do appreciate all the help so far...
I know... that's why we're trying to help. :)
Okay, the "knocking" of the hard drive is puzzling, but we'll leave that alone for a moment (but still... be mentally prepared for a hard drive replacement "just in case" as the main culprits of knocking drives are bad drives or bad power supplies.)
@Juanito: I was looking at the build scripts and noticed what MIGHT be an unintended file naming: 15.x/x86/tcz/gudev-gir.tcz ~~ was this intended to be gudev-lib-gir.tcz?
compile_webkitgtk4 is calling for gudev-lib-dev (not found) which is what led me into this direction; not that it has anything to do with this issue, but software wise it's on the list.
@Richard Cranium: In the meantime, please take a photo of the screen from the command below and post the results here.
cat /proc/cpuinfoWe need the lines processor through flags at the very least. (Processor line should contain "processor : 0")
If you need more than one photo to accomplish this
cat /proc/cpuinfo | more...and press the ENTER key to show the next line or SPACE bar to show the next full screen of information.
Specifically, on the flags line, you want to see whether the letters "smt" or "ht" exist.
IF SO, you need to go into BIOS and disable Hyper-Threading (HT/SMT did not exist yet with the Pentium 3 processor generation, but some motherboards which operated with EITHER P3 or P4 Socket 37x processors would have the option to enable HT/SMT with the assumption you had a P4 chip installed. Some laptops, especially ThinkPads of the age, used this "feature" as a potential "upgrade" in their sales pitch in a special line of motherboards which had removable processors... it was rare anyone actually DID the upgrade, though, considering the amount of work/time it takes to dismantle the machine, switch processors, and put it back together.)
-
Immediately after you enter “boincmgr” and get the illegal instruction message enter “dmesg | tail-10” and see if that gives any clue to the problem.
-
Okay, the "knocking" of the hard drive is puzzling, but we'll leave that alone for a moment (but still... be mentally prepared for a hard drive replacement "just in case" as the main culprits of knocking drives are bad drives or bad power supplies.)
no no , you misunderstand, it's seemingly normal for this machine to sound like that, it's not really "banging" , it's just noticeable..
@Richard Cranium: In the meantime, please take a photo of the screen from the command below and post the results here.
cat /proc/cpuinfoWe need the lines processor through flags at the very least. (Processor line should contain "processor : 0")
If you need more than one photo to accomplish this
cat /proc/cpuinfo | more...and press the ENTER key to show the next line or SPACE bar to show the next full screen of information.
Specifically, on the flags line, you want to see whether the letters "smt" or "ht" exist.
IF SO, you need to go into BIOS and disable Hyper-Threading (HT/SMT did not exist yet with the Pentium 3 processor generation, but some motherboards which operated with EITHER P3 or P4 Socket 37x processors would have the option to enable HT/SMT with the assumption you had a P4 chip installed. Some laptops, especially ThinkPads of the age, used this "feature" as a potential "upgrade" in their sales pitch in a special line of motherboards which had removable processors... it was rare anyone actually DID the upgrade, though, considering the amount of work/time it takes to dismantle the machine, switch processors, and put it back together.)
screenshots....
sorry for the late reply... :P
-
Immediately after you enter “boincmgr” and get the illegal instruction message enter “dmesg | tail-10” and see if that gives any clue to the problem.
it just says :
sh: tail-10 : not found
-
Hi Richard Cranium
... sh: tail-10 : not found
There's a space missing in the command. It should be:
dmesg | tail -10
-
Hi Richard Cranium
... sh: tail-10 : not found
There's a space missing in the command. It should be:
dmesg | tail -10
tried it again...
-
From this:
traps: boincmgr[6395] trap invalid opcode ip:b406acbc sp:bf984190 error:0 in libwebkit2gtk-4.0.so.37.55.8[b3b4f000+14de000]..the problem appears to be in the webkitgtk4 extension.
-
From this: traps: boincmgr[6395] trap invalid opcode ip:b406acbc sp:bf984190 error:0 in libwebkit2gtk-4.0.so.37.55.8[b3b4f000+14de000]..the problem appears to be in the webkitgtk4 extension.
So then... I it's safe to assume that my cpu architecture (or to say cpu related) isn't the problem , nor ram or even the installed OS version???
This has me more confused because , in a previous post someone said they got it working.. (EDIT- I know a saw a post here where someone said they got it working , but -It was deleted????? , I can't find it now.)
-
Boinc works for me - the problem is that webkitgtk throws an illegal instruction on your old cpu.
I’m currently recompiling webkitgtk to see if I can force it to respect the i486 instruction set.
-
Boinc works for me - the problem is that webkitgtk throws an illegal instruction on your old cpu.
I’m currently recompiling webkitgtk to see if I can force it to respect the i486 instruction set.
Ah ok , I'll wait a while .
And Thank You .. 8)
-
Recompiled webkitgtk4 posted - I don't have an i486 to test, please update your version of webkitgtk4 and try boincmgr again.
-
Recompiled webkitgtk4 posted - I don't have an i486 to test, please update your version of webkitgtk4 and try boincmgr again.
I removed boinc all together thru the package manager, restarted and re-installed boinc , I still get the same error .
illegal instruction
I checked and the recompiled version is installed...
-
It was webkitgtk4 you needed to reinstall, not boinc.
-
It was webkitgtk4 you needed to reinstall, not boinc.
That's what I did.... Boinc dosen't launch...
-
It was webkitgtk4 you needed to reinstall, not boinc.
new screenshot.
-
I tried one more time.
Please use the apps gui to update webkitgtk4, reboot and test boincmgr.
If anybody knows how best to configure cmake to force i486, suggestions welcome.
I tried this using -DCMAKE_TOOLCHAIN_FILE: # the name of the target operating system
set(CMAKE_SYSTEM_NAME Linux)
# Which compilers to use for C and C++
set(CMAKE_C_COMPILER /usr/local/bin/i486-linux-gnu-gcc)
set(CMAKE_CXX_COMPILER /usr/local/bin/i486-linux-gnu-g++)..but webkitgtk wouldn't configure
-
Hi Juanito
I found one maybe for you. It's from 2017:
https://gitlab.kitware.com/cmake/cmake/-/issues/17580#note_356805
-
I tried one more time.
Please use the apps gui to update webkitgtk4, reboot and test boincmgr.
I did all that and still got the same errors. So I tried something as a little experiment, I pulled out this older (gaming) machine that a friend gave me around ten years ago. And booted TC on that ,installed everything same as the Old laptop (the one that is being used for this thread) and tried to launch boinc..... NOTHING... it doesn't launch on that (gaming) machine either ... I'm including screenshots from that machine , hopefully this will tell you something...
If I may ask, What system specs are your machine?? 32 bit?? you said that you had boinc running on your end , i find it strange that I can't...
-
and 2 more , since the forum has a limit..
again , these are from the "tower" or Gaming machine...
-
Hi Juanito
A little more information on using a toolchain file mentioned
in the previous link:
https://stackoverflow.com/a/28047073
-
This may help: 86Box (https://86box.net/)
I haven't tried nor researched the concept, but my theory consists of an x86 old-school emulator
which should be able to maintain a proper TinyCore "install" and may allow testing in a more
accurate environment closer to the OP's hardware.
-
FWIW, if you search the TCL forum you can find info about earlier struggles in the BOINC saga. I don't know if anything there will still be of use though...
-
So it;s been a few days and no more replies , any ideas or anything I can try??
-
So it;s been a few days and no more replies , any ideas or anything I can try??
IF IT WERE ME... I'd compile the lot from scratch ON the hardware we're having issues with which should help ensure the processor being used is forcefully supported. Being that it's old hardware, expect it to take a while to complete. If there are issues the compiler can't figure out, it'll point you in a close direction of why. Start with the library that's throwing the Illegal Operation (webkit and/or wxwidgets) and use extensions for everything else for the beginning. For each package you compile yourself, create your own extension (filename.tcz) and replace the one in /etc/sysconfig/tcedir/optional with your new one.
Content for creating extensions is readily available both on the forum and wiki.
If compiling isn't in the cards for you, I'd recommend trying Debian out and see if their existing, though old version of boinc functions on your machine "at all." Yes, it'll likely be slow... but if the Manager screen comes up, it indicates potential that it "can" be done on your hardware, but how efficiently is another story.
-
Hi Juanito
I'm wondering if the real culprit is boinc, and webkitgtk4 is just
a red herring. When I was searching for info about this a week
ago I found a similar error that pointed at libc. Turned out the
culprit was the calling program, not libc.
-
It could well be, the trouble is that without i486 hardware it’s difficult to make much progress.
-
So it;s been a few days and no more replies , any ideas or anything I can try??
IF IT WERE ME... I'd compile the lot from scratch ON the hardware we're having issues with which
Yeah, I'm not quite sure how to do all that , I mean I've compiled a few things in Ubuntu in the past , but Ubuntu took care of a lot of the guesswork for me,,
-
See http://www.tinycorelinux.net/15.x/x86/tcz/src/boinc/compile_boinc
-
See http://www.tinycorelinux.net/15.x/x86/tcz/src/boinc/compile_boinc
----------------------------------------------------------
tce-load -i compiletc automake intltool libtool-dev gettext-dev curl-dev Xorg-7.7-3d-dev freeglut-dev glu-dev wxwidgets31-dev
wget https://github.com/BOINC/boinc/archive/refs/tags/client_release/8.0/8.0.4.tar.gz
cd boinc-client_release-8.0-8.0.4
./_autosetup
CC="gcc -flto -march=i486 -mtune=i686 -Os -pipe" CXX="g++ -flto -march=i486 -mtune=i686 -Os -pipe" ./configure --prefix=/usr/local --disable-static --localstatedir=/var --disable-server
[-fno-exceptions -fno-rtti fails]
find . -name Makefile -type f -exec sed -i 's/-g -O2//g' {} \;
make [7m 54.65s]
sudo make install
--- Configuring BOINC 8.0.4 (Release) ---
--- Build Components: (client manager libraries libraries_graphics manager_clientscr) ---
So, I type out all that??
-
Hi Richard Cranium
Yes. This version is a bit more literal:
tce-load -i compiletc automake intltool libtool-dev gettext-dev curl-dev Xorg-7.7-3d-dev freeglut-dev glu-dev wxwidgets31-dev
wget https://github.com/BOINC/boinc/archive/refs/tags/client_release/8.0/8.0.4.tar.gz
tar -xf 8.0.4.tar.gz
cd boinc-client_release-8.0-8.0.4
./_autosetup
CC="gcc -flto -march=i486 -mtune=i686 -Os -pipe" CXX="g++ -flto -march=i486 -mtune=i686 -Os -pipe" ./configure --prefix=/usr/local --disable-static --localstatedir=/var --disable-server
find . -name Makefile -type f -exec sed -i 's/-g -O2//g' {} \;
make
sudo make install
-
@Rich: I am pretty sure I read somewhere at the start of this boinc adventure there's a GTK (3 vs. 4) issue that was a pain once upon a time, but the real fun here is going to be the general environment - potentials for different X engines, drivers, libraries, etc. that on my kinda-old test hardware works without issue, but yes... red herring is always possible.
MY thought... run a find:binary on all files in /tmp/tcloop and -exec ldd {} > logfile
If things work as expected, LDD will flag Invalid Instruction(s) when attempting to run a dependency scan.
This would be without the "calling chain" (boinc > gtk > widgets > etc) so "should" help isolate the offender(s).
@Richard Cranium: Instead of typing all of the content in the Juanito pasted above, just download the source script onto your test machine
See http://www.tinycorelinux.net/15.x/x86/tcz/src/boinc/compile_boinc
Instead, on the test machine,
wget http://www.tinycorelinux.net/15.x/x86/tcz/src/boinc/compile_boinc
-
Hi CentralWare
... @Richard Cranium: Instead of typing all of the content in the Juanito pasted above, just download the source script onto your test machine ...
It's not really a script. It's more a mix of commands and notes. I got the
impression the OP was not very experienced compiling from scratch.
So I posted the instructions with comments removed and the missing
tar command inserted. I figured the OP might not recognize where
the comments are.
... MY thought... run a find:binary on all files in /tmp/tcloop and -exec ldd {} > logfile
If things work as expected, LDD will flag Invalid Instruction(s) when attempting to run a dependency scan. ...
I wasn't aware ldd could do that. But I guess whether ldd encounters an
illegal instruction depends on where in the binary being examined it's located.
-
I wasn't aware ldd could do that. But I guess whether ldd encounters an
illegal instruction depends on where in the binary being examined it's located.
LDD doesn't really "do that" - it's more like an unintended convenience.
This is somewhat of what I had in mind:
#!/bin/sh
. /etc/init.d/tc-functions
tce-load -i file
clear
cd /tmp/tcloop
sudo grep -r -I -L . > /tmp/binaries.lst
sudo file -f /tmp/binaries.lst | grep ELF | awk -F: '{print $1}' > /tmp/binaries.elf
while read -r file
do
res=$(sudo ldd "${file}" | grep -e "invalid " -e "error " -e "not found" )
[ ! "${res}" == "" ] && echo -e "${YELLOW}${file}${NORMAL}\n${res}\n\n"
done < /tmp/binaries.elf
Assuming BOINC was fully installed, it would scan through all of the binaries of everything installed at that moment (hopefully catching the herring if he's out there)
Again --- "in theory!" :)
-
Hi Richard Cranium
Yes. This version is a bit more literal:
tce-load -i compiletc automake intltool libtool-dev gettext-dev curl-dev Xorg-7.7-3d-dev freeglut-dev glu-dev wxwidgets31-dev
wget https://github.com/BOINC/boinc/archive/refs/tags/client_release/8.0/8.0.4.tar.gz
tar -xf 8.0.4.tar.gz
cd boinc-client_release-8.0-8.0.4
./_autosetup
CC="gcc -flto -march=i486 -mtune=i686 -Os -pipe" CXX="g++ -flto -march=i486 -mtune=i686 -Os -pipe" ./configure --prefix=/usr/local --disable-static --localstatedir=/var --disable-server
find . -name Makefile -type f -exec sed -i 's/-g -O2//g' {} \;
make
sudo make install
I think I'm going to put my little project on hold for a while , I've tried to compile and it just runs (compiles) so slow and then the system seemingly locks up , maybe a future version of TC will get the job done and the required packages will be fixed up...
But I DO VERY MUCH want to thank everyone here that offered help and advice . THANK YOU.... I'm starting another thread on a different subject tomorrow....
-
as of this post, one month has transpired since the start of this thread and it has been viewed 2874 times.
(which probably just means that interested people have read and reread the thread multiple times, i know i have)
with respect to aged hardware, you aren't the only one who finds it hard to say goodbye/goodnight to yesteryear:
https://forum.tinycorelinux.net/index.php/topic,25098.msg165728.html#msg165728