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.
i test scim with 14.0 rc1, found following problems
1: xfce-terminal can not input
2: program written with Lazarus/fpc, when i input some chinese word, one keyboard hit become two char input
3: use tigervnc 1.1.0 from Eric for remote management, scim does not work at all. run xfce 4.10 in vnc also
then i rebuild scim 1.4.14 from source, the problem resolved, so please update the scim packages. thanks.
I'm not sure if it's me doing something wrong or not, but the slackbuild script for Java JDK in /extra seems to be a little funny.
I built and installed a package using the slackbuild script and the jdk-7u5-linux-x64.tar.gz file from Oracle. However it seems to have installed everything (libs, bin, include) into /usr/lib64/java.
Code:
bash-4.2$ ls /usr/lib64/java/
COPYRIGHT README.html bin include lib release
LICENSE THIRDPARTYLICENSEREADME.txt db jre man src.zip
Is this the expected behavior? Things in /usr/lib64/java/bin don't show up in my path as desired..
I'm not sure if it's me doing something wrong or not, but the slackbuild script for Java JDK in /extra seems to be a little funny.
I built and installed a package using the slackbuild script and the jdk-7u5-linux-x64.tar.gz file from Oracle. However it seems to have installed everything (libs, bin, include) into /usr/lib64/java.
Code:
bash-4.2$ ls /usr/lib64/java/
COPYRIGHT README.html bin include lib release
LICENSE THIRDPARTYLICENSEREADME.txt db jre man src.zip
Is this the expected behavior? Things in /usr/lib64/java/bin don't show up in my path as desired..
You need to logout and login again to effectuate the changed environment (a file /etc/profile.d/jdk.sh was added by the package which adds the java bin directory to $PATH amongst others).
You need to logout and login again to effectuate the changed environment (a file /etc/profile.d/jdk.sh was added by the package which adds the java bin directory to $PATH amongst others).
Edit:
Never mind.. I didn't download the profile.d/ directory and it's contents into the same directory as the slackbuild and source so I was missing a few files.
It could be fixed by quoting but I tend to agree with Alien Bob:
Quote:
Originally Posted by Alien Bob View Post
Using spaces in directory names is not supported by Slackware's scripts. I also do not support it in any of my own scripts. I even have a script (massconvert32.sh) which aborts when it detects a space in the directory name.
Spaces in directory names is an abomination introduced by MS Windows and lazy-ass GUI programs. Real UNIX men avoid space.
I didn't realize that spaces in directory names was not supported in Slackware scripts...didn't see this in the Readme. Generally I don't use them myself; I usually use '_' instead and haven't run into any issues. For testing purposes, however, I love spaces (and long paths) because they can throw off some programs that haven't accounted for it.
I have used x86_64 as my main box since the initial release of SLAMD64, and then Slackware64. 32-bit lives in a Virtualbox and qemu VM for compiling and testing. I haven't noticed any liloconfig errors within these VMs.
I just dusted off an old P3 Compaq Armada E500 and ugraded from Slackware 13.1 to 14 RC2. No issues here either.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.