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.
There might be no hints at all, because it was not configured with --enable-debug option
you might want to recompile with that option and see if it helps
This bug is fixed just 4 days ago. It's not yet gone into mc-4.8.4. An upgrade does not fix the bug. Need an update with a patch, or wait for mc-4.8.1.5.
This seems really an annoying bug because it's quite startling if a text editor cannot save files.
Sun Sep 9 03:00:36 UTC 2012
xap/xine-ui-0.99.5-x86_64-3.txz: Reverted.
The file open shortcut appears to be broken in the newer xine-ui. Probably
safer to just revert it at this point. The new xine-lib seems OK, though.
I am lurking on oftc #xine hoping for a solution....
yes, the current xine-ui is now 5 years old and it lack several features that are present in 0.99.7
however, strange thing is that i couldn't find any bug report about this problem in other distributions. It seems that their package is fine
I was using my custom built 3.2.28 kernel and the same blueman as that in RC4 (all other packages from a -current snapshot few months ago). My Sony MW600 headset worked flawlessly. But now in RC4 I cannot connect my headset with blueman. In dmesg I see this strange message:
Code:
input: 58:17:XX:XX:XX:XX as /devices/virtual/input/input8
Seems my headset is recognized as an input device.
When I try to use blueman to connect to the A2DP service of my headset, blueman says
but they appear to be dynamic .so only. No .a static versions.
Is there a reason for this? I wanted to statically link to libuuid while I am playing with something.
Please comment someone, or should the util-linux package be rebuilt to have static libraries added?
edit: this is probably a non-issue and I just don't know too much about libraries... i see that most libraries are only the .so kind and I think i can statically link to them... not really sure... I don't program very much
edit2: actually, yes, under /usr/lib64 you find .a static libs for most basic system libraries, just few if any are in /lib64
So anyway, I think util-linux forgot to include the static libraries
More info: The SlackBuild appears to explicitly disable-static... but why? ...
The --disable-static configure option is there for Slackware-13.37 as well, nothing new here and nothing to worry about as the libraries are available and can be linked to by other programs.
What does this setting prevent you to do?
Last edited by Didier Spaier; 09-10-2012 at 01:02 AM.
The --disable-static configure option is there for Slackware-13.37 as well, nothing new here and nothing to worry about as the libraries are available and can be linked to by other programs.
What does this setting prevent you to do?
Only dynamic .so versions are there. There are no .a static versions of those libraries. As I understand it, this means you cannot link to the libraries statically and make a statically linked program that can run by itself, for instance inside a minimal initramfs to do some things during system boot. I am trying to link statically to them to make a small utility that would run as init program inside initramfs that has basically nothing else in it.
About initramfs, you can check that the Slackware installer itself includes these three shared libraries, which are very light weight, so this shouldn't be a problem.
Anyhow you can just edit the SlackBuild to fit your needs. This is one of the features which make the Slackware packaging system so versatile: if a stock configure option is not to your liking, just change it and rebuild the package
About initramfs, you can check that the Slackware installer itself includes these three shared libraries, which are very light weight, so this shouldn't be a problem.
Anyhow you can just edit the SlackBuild to fit your needs. This is one of the features which make the Slackware packaging system so versatile: if a stock configure option is not to your liking, just change it and rebuild the package
I built util-linux to include the static libraries, but now my program has other issues trying to link statically, so I am going to just forget about this!
I just updated my slackware-current mirror and installed the new packages.
When I open this page: http://javatester.org/version.html
I can see the correct Java version: "Java Version 1.7.0_07 from Oracle Corporation"
But when I open this page: http://www.java.com/en/download/help/testvm.xml
Firefox crashes completely as long as the directory "/usr/lib/java/jre/lib/fonts/fallback/" exists in my system, no matter if this directory is empty or not.
Not sure if the problem is in Firefox or in Java. I thought Firefox should not crash even if the Java plugin crashes. Am I mistaken?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.