SBo scripts not building on current (read 1st post, pls)
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.
Did you build the new dependency of atlas?
it worked fine here
Code:
lapack-atlas:
MD5SUM check for lapack-3.6.1.tgz ... OK
Building package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK
Installing package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK
atlas:
MD5SUM check for atlas3.10.3.tar.bz2 ... OK
Building package atlas-3.10.3-x86_64-1_SBo.tgz ... OK
Installing package atlas-3.10.3-x86_64-1_SBo.tgz ... OK
Did you build the new dependency of atlas?
it worked fine here
Code:
lapack-atlas:
MD5SUM check for lapack-3.6.1.tgz ... OK
Building package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK
Installing package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK
atlas:
MD5SUM check for atlas3.10.3.tar.bz2 ... OK
Building package atlas-3.10.3-x86_64-1_SBo.tgz ... OK
Installing package atlas-3.10.3-x86_64-1_SBo.tgz ... OK
atlas 3.10.3 compiling error on both Current and 14.2.
See error:
the part you quoted doesn't contain the actual error: you should add also the lines above where the real error should be...
FYI, it builds fine here too.
the part you quoted doesn't contain the actual error: you should add also the lines above where the real error should be...
FYI, it builds fine here too.
well, looking at that log it doesn't seem to be any error outputted by the build system.
reading its README the only mandatory thing that the maintainer note is to turn off cpu throttling (instructions are in that file).
if it doesn't work I suggest you to get in touch with the maintainer.
I tried this now on three different computers with no success on compiling atlas.
First, I tried to disable CPU throttling with "/etc/rc.d/rc.cpufreq performance" but atlas still comply that CPU throttling is enabled. I even tried to disable it via BIOS, but atlas still comply, this on all three different computers (Slackware 14.2 64-bit and 32-bit).
So, I recompiled a new kernel with CPU frequency scaling disabled. Then I passed that check but getting the error in previous section.
What kind of supercomputer with super Slackware 14.2 do you use to make atlas compile without issues?
(I have mailed the maintainer, waiting for response)
Last edited by Bindestreck; 09-30-2016 at 06:56 AM.
So, it might depend on what processor/bios/startup pogram runs your box that will let compilation of atlas happen.
For me is the question, how to disable intel_pstate on Slackware not using GRUB to get started...do I add "intel_pstate=disable" to the append-line in my elilo config?
EDIT: tried this (plus activating the line "modprobe acpi-cpufreq" in /etc/rc.d/rc.cpufreq) , but this did not inactivate the intel_pstate. Would this be because of having a intel cpu (i7-3632QM CPU @ 2.20GHz) in this box? Or does it depend on kernel or on Slackware 14.2/current? On this same computer I did manage to compile atlas, but that was in the days of 14.1; in 2013. Anyway, setting compilation to 1 core in the atlas.SlackBuild did not bypass the throttle error in my case.
EDIT2: managed to inactivate intel_pstate (needed to pass on =disable kernel instruction also to refind.conf), got it on performance but atlas still does not compile; first some weird error with setting up build directory; then suddenly, there's throttling again; probably because my cpufreq is down from its max.....for some odd reason...no idea why,...giving up.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.