LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-03-2018, 07:38 PM   #496
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 231

Original Poster
Rep: Reputation: 45

Quote:
regression test up to "Sun Dec 2 04:11:56 UTC 2018": everything is ok.
I'm still running behind you. Slackware64-current rsynced 2018-11-29 09:29:32 UTC and
slackware-from-scratch cloned 2018-11-28.

I did some reformating of the files (mostly indentation), but nothing that should have
caused any problems. Still, libcap built, but did not install. I tried twice with the
same result. It built and installed just fine manually. Will try again with the latest.

Everything else went fine, except snownews, as was expected.
 
Old 12-03-2018, 11:32 PM   #497
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 580

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
-libcap has been updated in slackware (no more patch needed)
-atk needed special treatment (source /root/.bashrc)
-snownews need modifying the 'fakedir' install path: done.

github project is up to date now.

Last edited by nobodino; 12-08-2018 at 03:27 AM.
 
Old 12-07-2018, 11:42 PM   #498
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 231

Original Poster
Rep: Reputation: 45
Latest slackware-from-scratch, slackware-current 2018-12-02

Built perfectly.
 
1 members found this post helpful.
Old 12-11-2018, 04:32 PM   #499
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 231

Original Poster
Rep: Reputation: 45
latest slackware-from-scratch, slackware-current dated Sat Dec 8 04:10:45 UTC 2018

All is well!
 
1 members found this post helpful.
Old 12-16-2018, 03:06 AM   #500
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 580

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
regression test up to "Fri Dec 14 18:59:34 UTC 2018": perfect score, everything builds ok.
 
Old 12-16-2018, 04:00 AM   #501
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 580

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
I will try to build plasma5 on top of slackware64-current.
Wait and see.

Last edited by nobodino; 12-16-2018 at 09:10 AM.
 
Old 12-16-2018, 07:28 AM   #502
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 580

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
failed on json-glib:
------------------------
json-glib-1.4.2/NEWS
ERROR: Command 'mesontest' not found
json-glib failed to build.

real 208m14,237s
user 1067m9,416s
sys 74m10,851s
------------------------
replaced by json-glib from slackware64-current (1.4.4 and SlackBuild) and it works.

Last edited by nobodino; 12-16-2018 at 07:29 AM.
 
Old 12-16-2018, 08:27 AM   #503
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 580

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
second failure on libindicator:
--------------------
/usr/bin/ld: cannot find -lglib-2.0-lm
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:489: libindicator.la] Error 1
make[3]*: on quitte le répertoire «*/tmp/libindicator-12.10.1/build-gtk2/libindicator*»
make[2]: *** [Makefile:417: all] Error 2
make[2]*: on quitte le répertoire «*/tmp/libindicator-12.10.1/build-gtk2/libindicator*»
make[1]: *** [Makefile:358: all-recursive] Error 1
make[1]*: on quitte le répertoire «*/tmp/libindicator-12.10.1/build-gtk2*»
make: *** [Makefile:288: all] Error 2
libindicator failed to build.
--------------------
 
Old 12-23-2018, 03:16 PM   #504
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 231

Original Poster
Rep: Reputation: 45
I'm not working on Plasma5, but am continuing with SFS.

Slackware-current, 2018-12-21, built perfectly. Tomorrow, I'll see if it works!

Merry Christmas to all and a happy New Year!
 
1 members found this post helpful.
Old 12-30-2018, 05:11 AM   #505
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 580

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
regression test up to "Fri Dec 28 00:23:43 UTC 2018": everything builds ok, once more.
It has never been so easy to build Slackware from scratch.

Last edited by nobodino; 12-30-2018 at 03:54 PM.
 
1 members found this post helpful.
Old 01-06-2019, 12:27 PM   #506
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 580

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
regression test up to "Fri Jan 4 21:44:44 UTC 2019": everything builds ok.
But the time to build increases dramatically:
------------------
on 10/08/2018: 910 mn
on 03/11/2018: 1075 mn
on 06/01/2019: 1500 mn
------------------
any idea?
 
Old 01-06-2019, 01:06 PM   #507
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,727

Rep: Reputation: 5418Reputation: 5418Reputation: 5418Reputation: 5418Reputation: 5418Reputation: 5418Reputation: 5418Reputation: 5418Reputation: 5418Reputation: 5418Reputation: 5418
NUMJOBS used to be hardcoded to 7, but in September was changed to be equal to the number of CPU threads plus one. Perhaps exporting NUMJOBS=7 would restore the previous compile times on your system?
 
Old 01-06-2019, 01:09 PM   #508
Skaendo
Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 909

Rep: Reputation: Disabled
Quote:
Originally Posted by volkerdi View Post
NUMJOBS used to be hardcoded to 7, but in September was changed to be equal to the number of CPU threads plus one. Perhaps exporting NUMJOBS=7 would restore the previous compile times on your system?
Would it make any sense to make it like this (from Idlemoor's slackrepo):
Code:
NUMJOBS="-j$(( $(nproc) * 2 )) -l$(( $(nproc) + 1 ))"
 
Old 01-11-2019, 12:58 AM   #509
worsel
Member
 
Registered: Feb 2008
Location: Washington State, USA
Distribution: Slackware 14.2, Slackware-from-Scratch
Posts: 231

Original Poster
Rep: Reputation: 45
Skaendo,

I tried your suggestion (from Idlemoor's slackrepo):

Quote:
NUMJOBS="-j$(( $(nproc) * 2 )) -l$(( $(nproc) + 1 ))"
It worked OK. Here are the times for the Slackware current builds shown for the below dates:

Date compiled: 20181223 20190110
build1_s.list 299m2.547s 320m7.329s
build2_s.list 654m1.144s 650m46.642s
build3_s.list 489m43.212s 520m19.714s
build4_s.list 944m57.083s 931m59.605s

So two of the times to process a list increased, two decreased. I liked the suggestion, though!
 
Old 01-13-2019, 02:57 AM   #510
nobodino
Member
 
Registered: Jul 2010
Location: in France
Distribution: slackware, slackware from scratch, LFS, linux Mint,Manjaro...
Posts: 580

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
strange behavior of bash-5.0 in prep-sfs-tools.sh (SFS):
-------------------------------
Code:
tools_test () {
#*****************************
	if [[ ! -f $PATDIR/$tools_dir/tools.tar.?z ]]; then
		cat <<- EndofText
	
		A copy of "tools.tar.?z" has been found.
		if you wish to untar this for your tools directory, select "old"
		otherwise select "new" to build a new tools directory.
		If you desire to quit, select "quit"

		EndofText

		PS3="Your choice: "
		select new_tools in old new quit; do
			case $new_tools in
				old  ) return 0 ;;
				new  ) return 1 ;;
				*    ) return 2 ;;
			esac
		done
	else
		return 1
	fi
}
---------------
'return 1' doesn't work anymore. It's stuck, even CRTL-c doesn't allow to kill the script?
'return 0' and 'return 2' are ok.
If I revert to bash-4.4.0023, it works again.
I've read that all functionalities of bash-5.0 are only available with readline-8.0, could it be related to this or something else?

Last edited by nobodino; 01-13-2019 at 03:01 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] /usr/bin/X11/X11/....... 10 X11 subsets & counting walter74 Linux - General 2 06-07-2015 12:36 AM
How do I get the /etc/X11/X file rebuilt from scratch rickh Debian 4 05-07-2006 11:06 PM
ali aladdin v agp stinks :scratch: :scratch: :scratch: Mr Marmmalade Linux - Hardware 1 07-08-2003 05:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:11 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration