LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
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-25-2017, 09:50 PM   #1
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Debian
Posts: 528

Rep: Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866
[ANN] Spamware


Spamware is PAM+Kerberos repository for Slackware64-current.

It is slapt-get compatible. The repository is in alpha state. Local logins are OK, but AD and LDAP compatibility is not yet tested.
  • cronie replaces dcron, you have to edit rc.M and remove "-l notice".
  • sshd_config default is "UsePAM no".
  • openldap replaces openldap-client.
  • freeradius-client is split from ppp.
  • alpine is patched to build a dynamic c-client and php is compiled against it.
  • inetutils replaces inetd,telnet,netkit-ftp,netkit-ntalk,netkit-rsh.
  • kde-workspace build failed, so I repackaged a 14.2 build for now.

Constructive feedback is welcomed.

Happy Holidays,

Cheers

Last edited by ivandi; 12-25-2017 at 10:01 PM.
 
Old 12-26-2017, 12:25 AM   #2
PROBLEMCHYLD
Senior Member
 
Registered: Apr 2015
Posts: 1,201

Rep: Reputation: Disabled
Thank you my BDFL. Merry Christmas.....
 
Old 12-26-2017, 02:48 AM   #3
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 15.0 + Multilib
Posts: 2,159

Rep: Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512Reputation: 1512
Thanks ivandi.

I'll take it for a spin as soon as I get past our Year End Crush at work.

-- kjh

P.S. I like your name for Slackware64 Current + PAM + Kerberos

Last edited by kjhambrick; 12-26-2017 at 02:51 AM. Reason: P.S. nice name
 
Old 12-26-2017, 04:48 AM   #4
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
Quote:
Originally Posted by ivandi View Post
kde-workspace build failed
Do you have the build log for that?
 
Old 12-26-2017, 08:29 AM   #5
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Debian
Posts: 528

Original Poster
Rep: Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866
Quote:
Originally Posted by Alien Bob View Post
Do you have the build log for that?
First it failed here:
Code:
make -f libs/kephal/service/CMakeFiles/kded_kephal.dir/build.make libs/kephal/service/CMakeFiles/kded_kephal.dir/build
make[2]: Entering directory '/tmp/pam/kde-workspace-4.11.22/build'
cd /tmp/pam/kde-workspace-4.11.22/build/libs/kephal/service && /usr/bin/c++  -DDISABLE_NEPOMUK_LEGACY -DHAVE_CONFIG_H=1 -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=8 -DKDE_DEPRECATED_WARNINGS -DMAKE_KDED_KEPHAL_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_STL -DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 -I/tmp/pam/kde-workspace-4.11.22/build/libs/kephal/service -I/tmp/pam/kde-workspace-4.11.22/libs/kephal/service -I/tmp/pam/kde-workspace-4.11.22 -I/tmp/pam/kde-workspace-4.11.22/build -I/tmp/pam/kde-workspace-4.11.22/libs -I/tmp/pam/kde-workspace-4.11.22/libs/kephal/kephal -I/usr/include/KDE -I/usr/lib64/qt/include/QtXmlPatterns -I/usr/lib64/qt/include/QtXml -I/usr/lib64/qt/include/QtWebKit -I/usr/lib64/qt/include/QtUiTools -I/usr/lib64/qt/include/QtTest -I/usr/lib64/qt/include/QtSvg -I/usr/lib64/qt/include/QtSql -I/usr/lib64/qt/include/QtScriptTools -I/usr/lib64/qt/include/QtScript -I/usr/lib64/qt/include/QtOpenGL -I/usr/lib64/qt/include/QtNetwork -I/usr/lib64/qt/include/QtMultimedia -I/usr/lib64/qt/include/QtHelp -I/usr/lib64/qt/include/QtDesigner -I/usr/lib64/qt/include/QtDeclarative -I/usr/lib64/qt/include/QtDBus -I/usr/lib64/qt/include/Qt3Support -I/usr/lib64/qt/include/QtGui -I/usr/lib64/qt/include/QtCore -I/usr/lib64/qt/include/Qt -I/usr/lib64/qt/mkspecs/default  -O2 -fPIC -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -O2 -DNDEBUG -DQT_NO_DEBUG -fPIC   -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -o CMakeFiles/kded_kephal.dir/xrandr12/randroutput.cpp.o -c /tmp/pam/kde-workspace-4.11.22/libs/kephal/service/xrandr12/randroutput.cpp
/tmp/pam/kde-workspace-4.11.22/libs/kephal/service/xrandr12/randroutput.cpp: In member function 'RandRMode RandROutput::mode() const':
/tmp/pam/kde-workspace-4.11.22/libs/kephal/service/xrandr12/randroutput.cpp:230:16: error: invalid conversion from 'XID {aka long unsigned int}' to 'XRRModeInfo* {aka _XRRModeInfo*}' [-fpermissive]
         return None;
                ^~~~
In file included from /tmp/pam/kde-workspace-4.11.22/libs/kephal/service/xrandr12/randroutput.h:29:0,
                 from /tmp/pam/kde-workspace-4.11.22/libs/kephal/service/xrandr12/randroutput.cpp:20:
/tmp/pam/kde-workspace-4.11.22/libs/kephal/service/xrandr12/randrmode.h:28:5: note:   initializing argument 1 of 'RandRMode::RandRMode(XRRModeInfo*)'
     RandRMode(XRRModeInfo *info = 0);
     ^~~~~~~~~
make[2]: *** [libs/kephal/service/CMakeFiles/kded_kephal.dir/build.make:430: libs/kephal/service/CMakeFiles/kded_kephal.dir/xrandr12/randroutput.cpp.o] Error 1
make[2]: Leaving directory '/tmp/pam/kde-workspace-4.11.22/build'
make[1]: *** [CMakeFiles/Makefile2:1208: libs/kephal/service/CMakeFiles/kded_kephal.dir/all] Error 2
make[1]: Leaving directory '/tmp/pam/kde-workspace-4.11.22/build'
make: *** [Makefile:144: all] Error 2
Adding -fpermissive to CXXFLAGS fixed it.
Next it failed here:
Code:
make -f kdm/backend/CMakeFiles/kdm.dir/build.make kdm/backend/CMakeFiles/kdm.dir/build
make[2]: Entering directory '/tmp/pam/kde-workspace-4.11.22/build'
cd /tmp/pam/kde-workspace-4.11.22/build/kdm/backend && /usr/bin/cc -DDISABLE_NEPOMUK_LEGACY -DHAVE_CONFIG_H=1 -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=8 -DKDE_DEPRECATED_WARNINGS -DQT_NO_CAST_TO_ASCII -DQT_NO_STL -DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 -I/tmp/pam/kde-workspace-4.11.22/build/kdm/backend -I/tmp/pam/kde-workspace-4.11.22/kdm/backend -I/tmp/pam/kde-workspace-4.11.22/build/kdm -I/tmp/pam/kde-workspace-4.11.22 -I/tmp/pam/kde-workspace-4.11.22/build -I/tmp/pam/kde-workspace-4.11.22/libs -I/usr/include/KDE -I/usr/lib64/qt/include/QtXmlPatterns -I/usr/lib64/qt/include/QtXml -I/usr/lib64/qt/include/QtWebKit -I/usr/lib64/qt/include/QtUiTools -I/usr/lib64/qt/include/QtTest -I/usr/lib64/qt/include/QtSvg -I/usr/lib64/qt/include/QtSql -I/usr/lib64/qt/include/QtScriptTools -I/usr/lib64/qt/include/QtScript -I/usr/lib64/qt/include/QtOpenGL -I/usr/lib64/qt/include/QtNetwork -I/usr/lib64/qt/include/QtMultimedia -I/usr/lib64/qt/include/QtHelp -I/usr/lib64/qt/include/QtDesigner -I/usr/lib64/qt/include/QtDeclarative -I/usr/lib64/qt/include/QtDBus -I/usr/lib64/qt/include/Qt3Support -I/usr/lib64/qt/include/QtGui -I/usr/lib64/qt/include/QtCore -I/usr/lib64/qt/include/Qt -I/usr/lib64/qt/mkspecs/default -I/usr/lib64/qt/include -I/usr/include/ConsoleKit/ck-connector -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include  -O2 -fPIC -Wno-long-long -std=iso9899:1990 -Wundef -Wcast-align -Werror-implicit-function-declaration -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -Wformat-security -Wmissing-format-attribute -fno-common -O2 -DNDEBUG -DQT_NO_DEBUG   -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -U_REENTRANT -o CMakeFiles/kdm.dir/client.c.o   -c /tmp/pam/kde-workspace-4.11.22/kdm/backend/client.c
In file included from /usr/include/dbus-1.0/dbus/dbus.h:30:0,
                 from /usr/include/ConsoleKit/ck-connector/ck-connector.h:34,
                 from /tmp/pam/kde-workspace-4.11.22/kdm/backend/client.c:83:
/usr/include/dbus-1.0/dbus/dbus-address.h:74:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
 static inline void
               ^~~~
In file included from /usr/include/dbus-1.0/dbus/dbus-connection.h:33:0,
                 from /usr/include/dbus-1.0/dbus/dbus-bus.h:30,
                 from /usr/include/dbus-1.0/dbus/dbus.h:31,
                 from /usr/include/ConsoleKit/ck-connector/ck-connector.h:34,
                 from /tmp/pam/kde-workspace-4.11.22/kdm/backend/client.c:83:
/usr/include/dbus-1.0/dbus/dbus-message.h:366:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
 static inline void
               ^~~~
In file included from /usr/include/dbus-1.0/dbus/dbus-bus.h:30:0,
                 from /usr/include/dbus-1.0/dbus/dbus.h:31,
                 from /usr/include/ConsoleKit/ck-connector/ck-connector.h:34,
                 from /tmp/pam/kde-workspace-4.11.22/kdm/backend/client.c:83:
/usr/include/dbus-1.0/dbus/dbus-connection.h:464:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
 static inline void
               ^~~~
In file included from /usr/include/dbus-1.0/dbus/dbus.h:37:0,
                 from /usr/include/ConsoleKit/ck-connector/ck-connector.h:34,
                 from /tmp/pam/kde-workspace-4.11.22/kdm/backend/client.c:83:
/usr/include/dbus-1.0/dbus/dbus-pending-call.h:87:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
 static inline void
               ^~~~
In file included from /usr/include/dbus-1.0/dbus/dbus.h:39:0,
                 from /usr/include/ConsoleKit/ck-connector/ck-connector.h:34,
                 from /tmp/pam/kde-workspace-4.11.22/kdm/backend/client.c:83:
/usr/include/dbus-1.0/dbus/dbus-server.h:115:15: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'void'
 static inline void
               ^~~~
make[2]: *** [kdm/backend/CMakeFiles/kdm.dir/build.make:108: kdm/backend/CMakeFiles/kdm.dir/client.c.o] Error 1
make[2]: Leaving directory '/tmp/pam/kde-workspace-4.11.22/build'
make[1]: *** [CMakeFiles/Makefile2:20770: kdm/backend/CMakeFiles/kdm.dir/all] Error 2
make[1]: Leaving directory '/tmp/pam/kde-workspace-4.11.22/build'
make: *** [Makefile:144: all] Error 2
dbus-address.h:74:15
Code:
static inline void
dbus_clear_address_entries (DBusAddressEntry ***pointer_to_entries)
{
  _dbus_clear_pointer_impl (DBusAddressEntry *, pointer_to_entries,
                            dbus_address_entries_free);
}
I guess it has something to do with -std=iso9899:1990 that is added to CFLAGS.

Any easy fix ?!?
That thing is abandoned since 2015. Spending a lot of time fixing it doesn't worth it.


Cheers
 
Old 12-26-2017, 08:46 AM   #6
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
You're probably right that fixing this KDE4 compile issue is not going to be fruitful.
 
Old 12-26-2017, 09:00 AM   #7
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Quote:
Originally Posted by ivandi View Post

dbus-address.h:74:15
Code:
static inline void
dbus_clear_address_entries (DBusAddressEntry ***pointer_to_entries)
{
  _dbus_clear_pointer_impl (DBusAddressEntry *, pointer_to_entries,
                            dbus_address_entries_free);
}
I guess it has something to do with -std=iso9899:1990 that is added to CFLAGS.

Any easy fix ?!?
That thing is abandoned since 2015. Spending a lot of time fixing it doesn't worth it.


Cheers
IF they fraked up the "static inline void" into GCC7, which is a perfectly valid language construct even in VC++, then half of the C++ code around the World is essentially broken for the GCC7.

Let's rewrite all the software around, just because Stallman waked up, looked down, seen a nice election* and exclaimed: "that's a nice day to frak** their code!"

* Intentionally misspelled word.
** Watch whatever episode of the Batlestar Galactica to figure out the sense of this word.

Last edited by Darth Vader; 12-26-2017 at 09:13 AM.
 
1 members found this post helpful.
Old 12-26-2017, 10:23 AM   #8
chrisVV
Member
 
Registered: Aug 2010
Posts: 548

Rep: Reputation: 370Reputation: 370Reputation: 370Reputation: 370
Quote:
Originally Posted by ivandi View Post
I guess it has something to do with -std=iso9899:1990 that is added to CFLAGS.
Quite so. The authors should not have explicitly required C89/90 (and so excluded relevant gcc C extensions) for a feature - inline functions - first introduced in C99. I guess the easiest solution would be to doctor the CFLAGS to exclude the requirement for strict C90 compliance, or trump it with a later -std=c99 flag.
 
Old 12-26-2017, 11:02 AM   #9
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Debian
Posts: 528

Original Poster
Rep: Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866
Quote:
Originally Posted by chrisVV View Post
I guess the easiest solution would be to doctor the CFLAGS to exclude the requirement for strict C90 compliance, or trump it with a later -std=c99 flag.
I already tried that with CFLAGS and CMAKE_C_FLAGS, but -std=iso9899:1990 is added after, so we have "cc -std=c99 -std=iso9899:1990'.



Cheers
 
Old 12-26-2017, 11:25 AM   #10
a4z
Senior Member
 
Registered: Feb 2009
Posts: 1,727

Rep: Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742
is this a cmake project?

make edit_cache
t to toggle to advanced options, check if this -std=iso9899:1990 is there, somewhere at the compile options, remove it

note that there are also CMAKE_C_FLAGS_DEBUG for debug, CMAKE_C_FLAGS_RELEASE for Release and CMAKE_C_FLAGS_RelDebug for releasedebug builds, these are usually added from cmake to the CMAKE_C_FLAGS, afterwards
 
Old 12-27-2017, 11:13 AM   #11
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Debian
Posts: 528

Original Poster
Rep: Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866
These cmake options fixed the kde-workspace build:
Code:
-DCMAKE_C_STANDARD=99 \
-DCMAKE_CXX_FLAGS="-fpermissive -Wno-cpp"


Cheers
 
3 members found this post helpful.
Old 12-27-2017, 11:06 PM   #12
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Debian
Posts: 528

Original Poster
Rep: Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866
OK, setting up a domain controller and a domain member works fine (see NOTES). At last, samba can be compiled against the system krb5. It is a simple setup using the rid backend and it works out of the box. That's basically all that I need. The rest will be tested in the time to come. So for me the repository is upgraded to early beta state.



Cheers
 
5 members found this post helpful.
Old 12-28-2017, 08:00 AM   #13
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 2,011

Rep: Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619
Quote:
Originally Posted by Alien Bob View Post
You're probably right that fixing this KDE4 compile issue is not going to be fruitful.
I'm going to take this as a hint that Plasma 5 will make its way into -current soon, though obviously it's quite possible you didn't mean it that way.
 
Old 12-28-2017, 08:08 AM   #14
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
Quote:
Originally Posted by montagdude View Post
I'm going to take this as a hint that Plasma 5 will make its way into -current soon, though obviously it's quite possible you didn't mean it that way.
I did not mean it that way. Yes, Plasma 5 hopefully ends up in Slackware before its 15.0 release, but in the meantime I do not expect that a re-compilation of Slackware's kde-workspace is needed. The package in -current is from June 2016. That is why I said it is probably not worth finding a way to make the recompilation succeed.
But ivandi found a fix anyway, so all is good.
 
Old 12-28-2017, 08:16 AM   #15
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 2,011

Rep: Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619Reputation: 1619
Ah, it was worth a try anyway. I'll stop distracting from the original topic now.
 
  


Reply



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
[ANN] Soma 2.13.0 dive Slackware 12 12-17-2017 07:06 PM
[ANN] mkslack 4.8 dive Slackware 0 05-05-2015 06:45 AM
[ANN] Soma 2.10.0 dive Slackware 2 04-16-2015 04:32 AM
[ANN] mkslack 4.7 dive Slackware 1 04-12-2015 12:34 PM
[ANN] Soma 2.7.1 dive Slackware 8 08-27-2011 03:04 AM

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

All times are GMT -5. The time now is 09:56 AM.

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
Open Source Consulting | Domain Registration