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 02-07-2014, 06:58 AM   #196
bartgymnast
Member
 
Registered: Feb 2003
Location: Lelystad, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 258

Original Poster
Rep: Reputation: 87

TobiSGD, I haven't had any error messages before.

Which ones are you facing ?
are you building with pam support, or without etc.
 
Old 02-07-2014, 07:33 AM   #197
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046
I am building without PAM. The errors I get are about missing libraries, issued by libtool. Example:
Code:
libtool: link: cannot find the library `libsystemd-shared.la' or unhandled argument `libsystemd-shared.la'
Building with -j1 however works, now I only have to figure out how to actually use systemd.
 
Old 02-07-2014, 10:22 AM   #198
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 2,205

Rep: Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569
I think it is a missing dependency in the Makefile.

Especially since it works with -j1.
 
Old 02-07-2014, 02:48 PM   #199
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,217
Blog Entries: 15

Rep: Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832
Are you building with or without python support?
 
Old 02-07-2014, 02:53 PM   #200
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046
I use the Slackbuild as is, except of course switching out -j7 with -j1.
 
Old 02-07-2014, 03:53 PM   #201
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,217
Blog Entries: 15

Rep: Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832
Systemd should build with -j2 or higher MAKEOPTS flags. If it's not then I'd do a query of any dependencies in the system and double or triple check everything before continuing. Check your compiler as well.

One minimal build I've seen (LFS-systemd experimental) disables gudev and python support from the main build.

As an option try testing flags...

--disable-gudev

And...

--without-python

These flags are for entirely optional features according to the documentation. Maybe it's something else though if this isn't it.

Has anyone checked the configure script to see if a flag for

--disable-shared

Exists?
 
Old 02-08-2014, 04:52 PM   #202
bartgymnast
Member
 
Registered: Feb 2003
Location: Lelystad, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 258

Original Poster
Rep: Reputation: 87
Tobi, I was able to reproduce the same error with an AMD CPU only.

libsystemd-shared.la is being build by systemd itself, so either amd cpu's are doing some different things in parallel, or there is something different wrong.
 
Old 02-08-2014, 05:03 PM   #203
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046
Quote:
Originally Posted by bartgymnast View Post
Tobi, I was able to reproduce the same error with an AMD CPU only.

libsystemd-shared.la is being build by systemd itself, so either amd cpu's are doing some different things in parallel, or there is something different wrong.
I have currently no Intel systems available, the building was done on an Athlon QL-66 (dual-core) and a Phenom II X6 (six cores), both had that problem. Might be reasonable to add the information to your Wiki that in case of errors on AMD CPUs compiling with -j1 is recommended.
 
Old 02-09-2014, 02:10 AM   #204
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 2,205

Rep: Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569
It has nothing to do with the processor type.

It only has to do with a missing dependency in the Makefile.
 
1 members found this post helpful.
Old 02-09-2014, 04:04 AM   #205
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,217
Blog Entries: 15

Rep: Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832
Quote:
Originally Posted by jpollard View Post
It has nothing to do with the processor type.

It only has to do with a missing dependency in the Makefile.
Which?
 
Old 02-09-2014, 06:53 AM   #206
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 2,205

Rep: Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569
Quote:
Originally Posted by ReaperX7 View Post
Which?
I assume you are meaning which Makefile... Can't help there.

Systemd has tentacles in so many places. But I would guess it is missing from the core systemd Makefile.
 
Old 02-09-2014, 07:34 AM   #207
Darth Vader
Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 611

Rep: Reputation: 111Reputation: 111
Like I said in this thread, I run that SystemD build in two of my machines. Nothing spectacular, two desktop systems, on somewhat old hardware (think about P4 w. socket 478, with 1G RAM & Co.)...

Also, both runs fine that "disgusting bloated and resurce hog" called KDE(4).

I like to say that everything works fine, from all that time, feeling it as stable solution.

Congratulation, bartgymnast! Looks like you successfully ported that (so hatred) SystemD into Slackware!

Then, we have SystemD. Beyond of that, is just a question of taste (or religious beliefs) on using it or not.

Last edited by Darth Vader; 02-09-2014 at 07:35 AM.
 
Old 02-09-2014, 08:42 AM   #208
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 2,205

Rep: Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569Reputation: 569
Quote:
Originally Posted by Darth Vader View Post
...
Congratulation, bartgymnast! Looks like you successfully ported that (so hatred) SystemD into Slackware!
Agree. It looks like it is compiled. Now to actually make it work takes a good bit of changes to the startup scripts, and in some cases, changes to the services themselves.
Quote:

Then, we have SystemD. Beyond of that, is just a question of taste (or religious beliefs) on using it or not.
Not exactly. It is a question of reliability. Network analysis for dependencies is an NP hard problem. It can be done for small environments such as desktops. But then, the time it takes is better put to use in actually starting them than in computing which comes first. Systemd attempts to do that with a "preprocessed network state"... Unfortunately, it can't be reliable as some things depend on outside operation before they can be started. Also systemd has trouble with timing issues - look at NetworkManager. Systemd has to depend on NetworkManager to tell it when things are ready, unfortunately, NetworkManager also depends on external things (like DHCP, DNS...) to be ready, and some of them aren't. By default systemd assumes the network is ready when NetworkManager is started... or (if directed) when NetworkManager tells systemd the network is ready. Then systemd starts things that depend on the network... like apache, which has been known to fail because the network isn't quite ready (dhcp took a little too long), or DNS isn't quite ready (after all it takes time to load tables...). Sometimes it works - if other services cause these to delay a bit while they get started. But it is now a VERY hard problem to solve when it doesn't work. And then there are services that SOMETIMES have additional dependencies - like apache needing a database (is it local... or remote? or both?)

It used to be trivial to handle...
 
1 members found this post helpful.
Old 02-09-2014, 08:54 AM   #209
JackHair
Member
 
Registered: Aug 2009
Location: Netherlands
Distribution: OpenSuse 13.1
Posts: 80

Rep: Reputation: 16
I've just compiled the systemd package on a freshly installed Virtualbox Slackware64 14.1 with an AMD Phenom II X4, with -j7, it did error on the readme while copying stuff over to the package. Tried to build it again with the "install readme" line commented out and it build successfully.
 
Old 02-09-2014, 11:43 PM   #210
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,217
Blog Entries: 15

Rep: Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832Reputation: 832
Getting the network up and running has been a long running argument for server usage of systemd and parallel loading of daemons compared to traditional linear loading methods used by sysvinit.

Here's a good question, could systemd be scripted to load network related services without using parallel loading?
 
  


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



All times are GMT -5. The time now is 01:45 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration