I am having a problem trying to compile rrdtool on slackware64-13. The problem is that the configure script keeps failing when it gets to the third party checks:
Quote:
configure:30114: WARNING: * I found a copy of pkgconfig, but there is no pangocairo.pc file around. You may want to set the PKG_CONFIG_PATH variable to point to its
[Code]...
I have a need to recompile mesa. The --enable-32-bit option falls over every header and basic 32 bit lib, and won't compile. But if I try to install 32 bit packages, I could slap a 32 bit binary straight on top of my 64 bit one. What's the accepted way of doing this? I can't seem to find a package in Slackware 13.0
View 9 Replies View RelatedI am having a hard time compiling libmp4v2-1.5.0.2 in slackware64-current. It always fails with:
PHP Code:
make[2]: *** [rtphint.lo] Error 1make[2]: Leaving directory `/home/Downloads/libmp4v2-1.5.0.1'make[1]: *** [all-recursive] Error 1make[1]: Leaving directory `/home/Downloads/libmp4v2-1.5.0.1make: *** [all] Error 2
Anyone knows a slackbuild for netbeans 6.8 for slackware64?
View 5 Replies View RelatedIs it just me or does the font rendering in Slackware64 13.37 look bad? It reminds me of the bad old days of having to recompile freetype with the then-patent-encumbered option to make the fonts look decent. When I print, everything looks normal. On screen it doesn't look right. I don't really know how to describe it other than it how things used to change after a freetype recompile. Is there anything major that changed between 13.1 and 13.37 WRT fonts in KDE, X, or freetype for that matter? FWIW, I did a clean install with a new .kde instead of using the old one.
View 14 Replies View Relatedafter this bug update, my laptop loose the sound, I have run alsaconf and nothing.If I run rc.alsa I get:Quote:Loading ALSA mixer settings: /usr/sbin/alsactl restore
/usr/sbin/alsactl: load_state:1608: No soundcards found...
I've tried reinstalling Slackware64 13.1 to my PC a number of times over the past couple of days and I still have not been able to get it to boot.
Once it's installed I reboot and it tells me it can't find the operating system.
I've tried fdisk, cfdisk and GParted to set up the disk by deleting partitions and recreating them.
When I install and get to the section about installing LILO it says I have an OS/2 or Partition Magic boot manager on the drive, but there isn't. It asks if I want to install LILO in a compatible way with the boot manager and I say no, and install to the MBR. When I reboot it says it can't find the OS.
When I try to boot from the install DVD and get to the boot: prompt, I'll enter /dev/sda1 and it says there is no kernel.
Is there something else I'm missing?
Regarding the latest update to -current, I decided to test installing it on a laptop from a usb stick (as I've done may times before). However this time the usb stick fails to boot as usual, hanging with the message "Could not find kernel image: linux". This isn't a problem with the usb stick, since if you mount the usbboot.img file as a loop device there is only 1 file on there, "ldlinux.sys", where you would usually find huge.s, initrd.img etc.
Have tried the 64-bit usbboot.img file from a couple of different mirrors and the result is the same. Have also looked in the usbboot.img from the 32-bit -current... this shows the usual set of files so looks to be OK.
I'm trying to compile tolua++ so that i can use lua in conky 1.7.2, however I am running into a problem. tolua++ defaults to looking for lua 5.0 libraries and I have lua 5.1 installed since that is what conky requires. According to the README tolua++ can use lua-5.1 but I not sure how to configure tulua++ to use those libraries since it uses scons. Here is a what the README says...
Compiling for lua 5.1
Starting from version 1.0.8pre1, tolua++ can be compiled with both lua 5.0 and
5.1. Both versions will output the same code, and the C API (tolua++.h) is the
same.
The build system is not yet ready to detect/decide when to compile for 5.1,
the easiest way right now is to add a file called 'custom.py' on the root of
the package, with the following:
## BEGIN custom.py
CCFLAGS = ['-I/usr/local/include/lua5.1', '-O2', '-ansi']
LIBPATH = ['/usr/local/lib']
LIBS = ['lua5.1', 'dl', 'm']
tolua_bin = 'tolua++5.1'
[Code]....
I tried to recompile php with support for oracle extensions oci8.so. Got the source and slackbuild script from slackware repo and just add the following line to the slackbuild script. "--with-oci8=shared,instantclient,/opt/instantclient_11_2". I use instant client from oracle Version 11.2.0.2.0 from this page
After I run the script I got this error message
Code:
/bin/sh /tmp/php-5.3.6/libtool --silent --preserve-dup-deps --mode=compile gcc -I/tmp/php-5.3.6/ext/fileinfo/libmagic -Iext/fileinfo/ -I/tmp/php-5.3.6/ext/fileinfo/ -DPHP_ATOM_INC -I/tmp/php-5.3.6/include -I/tmp/php-5.3.6/main -I/tmp/php-5.3.6 -I/tmp/php-5.3.6/ext/date/lib -I/tmp/php-5.3.6/ext/ereg/regex -I/usr/include/libxml2 -I/usr/include/enchant -I/usr/include/freetype2 -
code....
I'm going to install Slackware 13.1 soon and I may also install the 32-bit compatibility libraries from Eric (Alien BoB).I'd like confirmation on the process of updating multilib Slackware when there's a security patch. I'm talking about running the -stable branch, by the way.Under the normal methods of updating (e.g. 'slackpkg upgrade-all' or using the script I developed to download a local mirror of the patches directory and install from there, or even doing it by hand), the regular 64-bit packages will get updated.However, the 32-bit compatibility versions of those files won't get updated. Right?So I'll need to download the new 32-bit patches, run the convertpkg-compat32 script on them, and then upgradepkg the new files.
View 8 Replies View RelatedWhile trying to compile itcl, one of the error messages caused me to look inside /usr/lib64/tclConfig.sh. I found many paths that were in /tmp, such as...
Code:
# String to pass to linker to pick up the Tcl library from its
# build directory.
TCL_BUILD_LIB_SPEC='-L/tmp/tcl8.5.8/unix -ltcl8.5'
[code]....
after search and look at in vcar/log/pm-suspend.log I changed and quoted line to /usr/lib64/pm-utils/sleep.d/00logging who are reference to command free
[Code].....
Just got a new toy!
Quote:
Compaq/HP CQ60-615DX Notebook @Best Buy $369.00
Intel Celeron 900 (2.2Ghz)
250GB(7200rpm) HDD
2GB DDR2 SDRAM
8x DVD +/- R/RW Double layer
Win7 Home Premium (for the time being)
[Code]...
I will keep Win7 for clients as this will be another laptop for that usage plus wanting to have a decent laptop for the rec room to do that style of work. Cheap way to service M$ clients without buying more personal license(s). So far no big deal with M$ Win7 but I need to have that pathway available to me.
My reason to buy this notebook rather then a netbook should be obvious, big enough for me to do what is necessary. I've got test beds to do the real work, netbooks just won't meet the needs as describe above. I purchased a Netbook for my wife. That one will be used while she's away to aid with the new Grandchild, a lot easier to carry than her old HP Laptop. If the Netbook is lost then no worry since it's cheaper than her HP.
I am running Slackware64-13.1 on my laptop. I need to install skype on it. Searching this forum suggests that I install Alien Bob's multilib [URL] However, skype is the only 32-bit package I need and I will not need to compile any 32-bit software. So what is the minimal multilib install (the minimal set of 32-bit libraries) that make it possible for the 32-bit Skype to run on a 64-bit system? Will running
Code:
ldd /usr/bin/skype
on my 32-bit desktop machine provide me that minimal list of 32-bit packages? Also, will the installation of these libraries somehow interefere with the original 64-bit system?
I've got an older HP Pavilion dv8000 laptop with ATI Radeon XPRESS 200M 5955 video. This worked fine out-of-the-box with 13.1. With 13.37 I can't get KDE desktop effects to work, glxgears reports about 50 fps, and the system can suspend but not resume. I have no xorg.conf at all. Here is the glxinfo and current Xorg log. Just to note, this is with Slackware64 13.37 with the multilib stuff installed.
View 4 Replies View RelatedI've just synchronized my slackware64-current mirror, iso burned, booting, starting cfdisk, creating a partition, and I'm not able to set the partition type to `Linux Raid Autodetect` (FD) or any other, that needs 2 characters to be entered in cfdisk -> Type.Cfdisk alows only one character to be entered ("F" or any other).
View 3 Replies View RelatedThere is this slackbuild in which I have changed the part in bold.
Code:
#!/bin/sh
# Packager GioPower, luca.gio.85~at~gmail~dot~com
# VTK (Visualization Toolkit)
#
# The Visualization Toolkit (VTK) is an open-source, freely available
[Code]...
This will still drop stuff into /usr/lib, which is clearly anti Slackware64... I do not know enough of cmake builds, which flag do I have to pass in the slackbuild for cmake to drop stuff in /usr/lib64...?
I am trying to get Kmymoney working with HBCI support on my Slackware64-13.37 system. My understanding is, that there are three dependencies for Kmymoney 4.5.3:
AqBanking 5.0.5
Gwenhyfwar 4.0.9
KMyMoney Plugin (kmm_kbanking) 1.0
I used to believe, that the plugin wasn't needed anymore in recent version of KMyMoney, but it seems, that I was wrong. With src2pkg I was able to compile AqBanking and Gwenhyfwar:
Code:
# src2pkg -e
'--with-openssl-includes=/usr/include
--with-openssl-libs=/usr/lib64
--with-qt4-includes=/usr/lib64/qt/include
--with-qt4-libs=/usr/lib64/qt/lib'
Then I used the SlackBuild script from SlackBuilds.org, modified the version to 4.5.3 and started it with ARCH=x86_64. Compilation ran through smooth, and I installed the package. However, HBCI support is disabled.
After some web research I came to the conclusion, that the KBanking module is still needed. So I grabbed it from the original source. Unfortunately I can't properly compile this one. Although I installed KDE3 and Qt3 compatibility packages from Slackware64-13.1 I get:
Code:
checking for Qt... configure:
error: Qt (>= Qt 3.2 and < 4.0)
(headers and libraries) not found.
check your installation!
Has anyone managed to get through the whole process and to activate HBCI support in KMyMoney?
I used qemu (qemu-0.9.1-i386-2_SBo) with Windows98SE as a guest, but since the last Slackware-current update of this version of qemu no longer works ...more precisely after "Mon Apr 8 06:58:48 UTC 2011" Update
Then installed the version "qemu-0.12.5.tar.gz" of Slackbuils, but this If the mouse is not detected in Windows 98 I also installed the version of the Alien "qemu-0.10.0-i486-1alien" without success Windows 98SE worked very well with the version of qemu-0.9.1-i386-2_SBo!I know the mouse is not detectable in Windows 98SE is a Bug [URL].. ps: I also have not had success in Slack 32. I use on a daily 64-bit version of Slackware .
I've just installed a Slackware64-13.0 test machine with alienBOB's multilib packages. I'm running the stock kernel generic-2.6.29.6 with an initrd set up using mkinitrd.confEverything is fine except that I cannot build a right initrd for kernels 2.6.30, both the /testing one or a custom build: if I try, it will panic at boot with the "couldn't find a valid RAM disk image" error.On the same hardware, without multilib support, I was able to correctly build and boot 2.6.30 initrds.
View 11 Replies View RelatedIs the future Slackware release 13.1 going to be default multilib...?
View 14 Replies View RelatedBeen thinking about changing over to 64 bit, but I was just curious about whether or not I'll have to worry about incompatibility with a few 32bit-only applications I use, once I've set up multilib. I'll test it out in vbox when I get home but I wanted to check here to see if I could maybe get a solid yes/no/maybe answer.
View 14 Replies View RelatedI'm getting ready to install Slackware64_13.1 (finally), and I may then install Eric's multilib packages. The slackbuild for Wine at Slackbuilds.org states:
[code]...
has anyone built WINE with the 32-bit compatibility packages? Does it work?
I've been trying to get some kind of virtualisation solution for my Slackware64, and I'd been having an absolute nightmare trying to get virtualbox to work on my Slackware64 install, so I decided to ditch it and move to KVM instead, as a type 1 hypervisor, having had success with QEMU in the past. I installed qemu-kvm along with all the dependencies using sbopkg, and I didn't have any problems building it, nor creating a user for kvm, or anything of that sort. However, now if I try to open a .iso on a disk image I created using qemu:
Code:
qemu-img create -f qcow2 ubuntu.qcow 4G
Which I am then easily able to access with qemu using the following command:
Code:
qemu ubuntu.qcow -cdrom /ISO/ubuntu-8.10-dvd-i386.iso -m 256 &
(I have an old ubuntu 8.10.iso on my PC that I used just to see if the thing would work) This works just as expected. However, if I try to launch the same .iso using kvm
Code:
kvm -hda ubuntu.qcow -cdrom /ISO/ubuntu-8.10-dvd-i386.iso -m 256 -boot -d &
all I get is "bash: command not found: kvm" I have already loaded the following modules: kvm, kvm-intel, tun. Could I be missing something?
[edit] Also just noticed that though I have created a group for kvm and added myself to libvirt, but when I issue the command "groups" neither of them are there, though I did use:
Code:
groupadd -g 221 kvm
And I was under the impression that I just needed to add my user to libvirt, without needing to manually create the group itself.I may have misunderstood the procedure for installing this properly, but I'm not sure what I've done wrong.
I've never used a 64bit system set up this way. They've been pure 64bit with everything simply in /usr/lib with no /usr/lib64. IIRC That's how Arch used to do it.
My question is, should I continue patching all these makefiles that have libdir=/usr/lib hard coded to keep a sane system? What are the side effects of not putting all the libs in /usr/lib64? These are for the sources that don't use or follow --libdir= and LDFLAGS="-L/usr/lib64".
Can I rm -rf /usr/lib then ln -s /usr/lib64 /usr/lib and still have things work. There are a couple of files in /usr/lib now {codecs/ crda/ libsyslinux.a rpm/ sendmail siconv/ syslinux/ terminfo/ trn/} which came from a stock install.
There are not any 32bit programs I need to run. If I did, that's what KVM is for
PS. I want some Slackware64 Swag!
Is there any way to install "VirtualBox-3.2.12-68302" in the "slackware64-current" (Kernel 2.6.38.7) ?
I have problems with the 4.0.x version of VB!
The version "VirtualBox-3.2.12-68302" works fine with my hardware!
I tested using "VB 3.2.12" and Slackware64-13.37 (kernel 2.6.37.6).
I get the warning when I try to install a guest OS in "VB 3.2.12" running slackware64-current ...
Quote:
There is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
As root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first.
This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary"
And still
Quote:
Failed to open a session for the virtual machine Slackware12.0.
The virtual machine 'Slackware12.0' has terminated unexpectedly during startup with exit code 1.
Result Code:
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code:
# Linux bootable partition config begins
image = /other/spare4/boot/vmlinuz
[code]....
I need to dowload the RRDTool package for CentOS 5.3. I will use it on a Beowulf cluster with Ganglia. where I can to download the package RRDTool?
View 3 Replies View RelatedI trying to install rrdtool 1.4.4 in my Linux CentOS 5.5 distribution, but it requests a perl platform for rrd:
In other forums I found that I shall install this platform and I did that:
But how can you see, it requests librrd.so.4 library, but I can't find it.
Where can I find this library (librrd.so.4) ?