[SOLVED] odd problem at building qt5 on slackware64 current
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:
The trick doesn't say what is the root cause, I suspect a new comer (glibc is my favorite):
What program can detect an AMD or an INTEL processor?
- kernel: changed twice a week
- glibc: changed
- binutils: changed since the introduction of glibc
- llvm: hasn't changed since the introduction of glibc
- gcc : hasn't changed since the introduction of glibc
- qt5: changed
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Original Poster
Rep:
qt5 builds without errors in SFS with glibc-2.33, all the cores are active.
That's the only package I've changed wrt slackware64 -current.
The problem lies in the presence of glibc-2.35 or the way it interacts with a package which causes the failure of qt5 building with the standard qt5.SlackBuild.
PS: to avoid memory problem, since I have "only" 16G, and swap exceeds 30G during the build
I added 30G of zram swap,in addition to the initial swap (16G)
Code:
blackstar :: ~ » free -m
total used free shared buff/cache available
Mem: 15419 5565 6355 2395 3497 7131
Swap: 47512 8796 38716
PS: to avoid memory problem, since I have "only" 16G, and swap exceeds 30G during the build
I added 30G of zram swap,in addition to the initial swap (16G)
Ahhh, I guess that explains my error messages and failed compile:
Code:
g++: fatal error: Killed signal terminated program cc1plus
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,564
Original Poster
Rep:
error message:
Code:
root@darkstar64-2:/etc/rc.d# ./rc.local start
/etc/rc.d/rc.swapinzram: ligne 25 : echo: erreur d'écriture : Ne peut allouer de la mémoire
mkswap: erreur*: la zone d'échange (swap) doit être d'au moins 40*Kio
swapon: /dev/zram2*: échec de lecture d'en-tête d'espace d'échange
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.