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.
Hey guys, ever since upgrading to RC5 on my desktop whenever I reboot I need to run ifconfig eth0 up and dhcpcd to get the internet going again... it did it automatically prior to upgrading. Still works fine on my laptop.
Also, if you don't run make modules_install on your shiny new kernel you're going to have problems
EDIT: If I make networkmanager executable it brings it up automatically, how do I do it without having the networkmanager icon though? Being too picky maybe..
4.7.2 is worth upgrade before 14 got released. As in the release note:
Quote:
GCC versions 4.7.0 and 4.7.1 had changes to the C++ standard library which affected the ABI in C++11 mode: a data member was added to std::list changing its size and altering the definitions of some member functions, and std:: pair's move constructor was non-trivial which altered the calling convention for functions with std:: pair arguments or return types. The ABI incompatibilities have been fixed for GCC version 4.7.2 but as a result C++11 code compiled with GCC 4.7.0 or 4.7.1 may be incompatible with C++11 code compiled with different GCC versions and with C++98/C++03 code compiled with any version.
There are some binary incompatibility problem with 4.7.0,4.7.1 with the reset of gcc version.
The GNU Compiler Collection version 4.7.2 has been released.
GCC 4.7.2 is the first bug-fix release containing important fixes for regressions and serious bugs in GCC 4.7.1 with over 70 bugs fixed since the previous release.
kernel huge-3.5.4 from testing doesn't compile on RC5
Hi,
I did a fresh install of slackware64 RC5 on my homeserver. I wanted to try the 3.5.4-kernel from testing. I've used the config-huge-3.5.4.x64 script with the sources from kernel.org. Only change (with menuconfig) was processor-type=K8. But make breaks with the following message:
Code:
AS arch/x86/lib/thunk_64.o
CC arch/x86/lib/usercopy.o
CC arch/x86/lib/usercopy_64.o
AR arch/x86/lib/lib.a
LINK vmlinux
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
fs/built-in.o: In function `gfs2_lock':
file.c:(.text+0x3cb84f): undefined reference to `dlm_posix_lock'
file.c:(.text+0x3cb88c): undefined reference to `dlm_posix_unlock'
file.c:(.text+0x3cb8ad): undefined reference to `dlm_posix_get'
fs/built-in.o: In function `gdlm_cancel':
lock_dlm.c:(.text+0x3dde35): undefined reference to `dlm_unlock'
fs/built-in.o: In function `gdlm_lock':
lock_dlm.c:(.text+0x3ddffb): undefined reference to `dlm_lock'
fs/built-in.o: In function `sync_unlock':
lock_dlm.c:(.text+0x3de45d): undefined reference to `dlm_unlock'
fs/built-in.o: In function `sync_lock':
lock_dlm.c:(.text+0x3de5bb): undefined reference to `dlm_lock'
fs/built-in.o: In function `gdlm_unmount':
lock_dlm.c:(.text+0x3df1ac): undefined reference to `dlm_release_lockspace'
fs/built-in.o: In function `gdlm_put_lock':
lock_dlm.c:(.text+0x3df70a): undefined reference to `dlm_unlock'
fs/built-in.o: In function `gdlm_mount':
lock_dlm.c:(.text+0x3dfaae): undefined reference to `dlm_new_lockspace'
lock_dlm.c:(.text+0x3dfbbb): undefined reference to `dlm_release_lockspace'
make: *** [vmlinux] Error 1
srv-zuhause:/tmp/linux-3.5.4-huge/linux-3.5.4#
I had already built the generic kernel with the config-generic-3.5.4.x64 script and the same sources (in another directory), the generic kernel 3.5.4 works properly.
Does anyone know if this can be a bug in the kernel? I'll try again to build the kernel.
Hello!
I have a problem with oxygen-gtk2-1.3.0 and Opera browser, version is 12.0 build 1467. I use Xfce-4.10, this problem shows here. With all another Qt- and GTK+ based programs are all good. Any ideas? Dependencies is satisfied. Thanks.
@Markush: according to another thread and to this post it could be because as DLM is configured as module, GFS2_FS should be modularized as well. But in the -huge config it is built-in.
So please edit the config file you used like this :
Code:
sed -i s/CONFIG_GFS2_FS=y/CONFIG_GFS2_FS=m/ config-huge-3.5.4.x64
And try again. If that succeed, we could kindly request Pat to make that change in Slackware 14.
PS the same difference between -huge and -generic kernels exist in configs for 3.4.11 and 3.6-rc4. This is not surprising as usually in Slackware kernels all file systems are modularized in -generic and built-in in -huge.
PS2 Another solution would be for Pat to ship only config files for -generic kernels in /testing. This would save him some time and wouldn't be a big loss for us end users IMHO, as anyway the kernels we build from these config files aren't supposed to be used to install Slackware 14...
Last edited by Didier Spaier; 09-23-2012 at 04:48 PM.
Reason: Rephrasing
I'd be shocked if the gcc and xorg one went in. I think (though I may be wrong) that LLVM is there only for academic benefit and nothing in Slackware actually uses it, so that might just slip through. Even then, I doubt it.
In response as to why LLVM is part of Slackware 14, please see this excerpt from the slackware-current changelog from 5 May 2012:
Code:
Sat May 5 02:28:15 UTC 2012
Hey folks, here are some more updates, including the latest stuff from X.Org.
Thanks to Robby Workman for updating the X11 build tree, and B. Watson for
adding useful information to hundreds of X slack-desc files that previously
contained generic boilerplate.
a/tree-1.6.0-x86_64-1.txz: Upgraded.
d/llvm-3.0-x86_64-1.txz: Added.
This is needed to compile gallium drivers for X, and will probably
be useful for other development. Thanks to Heinz Wiesinger.
So the inclusion of LLVM is not merely "for academic benefit" but to meet the needs of Slackware users who use the Gallium Xorg drivers.
Hello!
I have a problem with oxygen-gtk2-1.3.0 and Opera browser, version is 12.0 build 1467. I use Xfce-4.10, this problem shows here. With all another Qt- and GTK+ based programs are all good. Any ideas? Dependencies is satisfied. Thanks.
Opera can use Qt/KDElibs for styling directly. I would use this rather than a Gtk theme that mimics a Qt theme. Change opera:config#FileSelector|DialogToolkit to 3, click "Save" and restart Opera.
Opera can use Qt/KDElibs for styling directly. I would use this rather than a Gtk theme that mimics a Qt theme. Change opera:config#FileSelector|DialogToolkit to 3, click "Save" and restart Opera.
Mon Sep 24 20:25:12 UTC 2012
Here are a few minor bugfixes as well as a couple more test drivers for X:
...
testing/source/config-testing-3.*: Rebuilt.
Changed CONFIG_GFS2_FS in huge kernels from y -> m to fix the compile.
...
Last edited by Didier Spaier; 09-24-2012 at 04:14 PM.
192c192
< if [ -x /etc/rc.d/rc.wicd ]; then
---
> if [ -x /etc/rc.d/rc.wicd -a -x usr/sbin/wicd ]; then
Thanks!
Read the changelog please!
Code:
a/sysvinit-scripts-2.0-noarch-12.txz: Rebuilt.
In rc.M, don't run rc.wicd if /usr/sbin/wicd does not exist. This change
prevents a leftover rc.wicd from blocking NetworkManager startup.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.