Slackware :: Slackware64 /usr/lib /usr/lib64 / Continue Patching All These Makefiles That Have Libdir=/usr/lib Hard Coded To Keep A Sane System?
May 21, 2009
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
While 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'
I have a 2010 model laptop running slackware 13.1, and after setting up a udev rule for my epson rx700 printer/scanner, this laptop can print to the rx700 without problems, and I can scan straight into gimp with xsane... I can even share the printer and scanner over my local lan.however when I pack up my laptop and hit the road, the other folks in the house cannot print or scan over the network anymore, so I tried to get an older desktop we have laying about to be the cups / sane server instead of my laptop.I tried a Dell Dimension 8300, and a Dell Optiplex GX 260. Both have USB 2.0 however, on fresh slackware 13.37 installs, even after the udev rule, neither old computer is successful finding the scanner with sane-find-scanner, although it is listed in output of lsusb.
does anyone know if there is a workaround on these older machines, or have there been some hardware changes in the last 8 years that the machines haven't undergone, and I should give up trying to get one to be cups/sane server for rx700..
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:
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:
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?
what system variables should I set to what and what options do I pass to ./configure so it builds and install libraries in */lib64 come on a 64bit system should be native 64bit not guest 64bit the guest should be 32bit as in /lib32 for multilib
I'm trying to setup an Epson perfection 4490 photo scanner in Slack 13.1. I've got the appropriate iscan and epkowa driver and firmware. However it is not working: sane-find-scanner produces:Code:found USB scanner (vendor=0x04b8 [EPSON], product=0x0119 [EPSON Scanner]) at libusb:001:004but scanimage -L finds nothing. After battling a lot with dll.conf and epkowa.conf I decided to run strace scanimage -L and to my shock it never tries to read dll.conf, instead it goes straight to read xerox_mfp.conf and does not try to read any other conf file in /etc/sane.dHas anyone come across problems with sane in 13.1 (or 13.0 as I tried this before upgrading with the same results)?
I have a Samsung SCX-4200. It was working pretty good with sane 1.0.21. I'm using slackware current, keeping updated (almost) every day. On the Mon Feb 28 update sane was updated to sane-1.0.22-i486-1. After that update xsane (as user) cannot find my scanner. I was able to find it running sane-find-scanner as root, but scanimage -L (as root) wasn't able to find the scanner. Now I have updated to the last sane package, named sane-1.0.22-i486-2 . In the changelog I can see that this rebuild should add libusb support.
In fact, now there's no way to find the scanner. And now also sane-find-scanner (as root) is no more able to detect the scanner, also running the command as root. I've tried running sane-find-scanner -v -v and scanimage -v -v -L but I can't get no useful hints. I have checked the sane configuration files but always seems good (the row with USB IDs is not commented in the backend file, which is xerox_mfp, and the backend is listed in dll.conf).
I have been given an Epson CX5000 3-in-1 that I only want to use the scanner part of (I have a laser and hate buying ink). The scanner works, tested under windoze, but xsane and scanimage -L fail to find it. But, lsusb does: $ /sbin/lsusb Bus 001 Device 003: ID 04b8:082b Seiko Epson Corp. Stylus DX5050
I saw a post about it under ubuntu that you had to modify /etc/udev/rules.d/45-libsane.rules Which doesn't exist on my Slackware 13 install. I hope this Epson runs faster than my Canon FB630U, which takes almost a four minutes to scan a 5x6 photo and forget scanning an 8.5x11 page (go take a nap).
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
Is 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.
after 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.
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:
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
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.
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
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 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
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.
Does anybody know where to find an rpm of sane-frontends?I want to use my auto-document-feed functionality on my scanner using scanadf, which is part of sane-frontends.Otherwise I'd also welcome alternative suggestions for scanadf.
I'm running Suse 11.2 and using a Brother DCP7065DN scanner/printer, which actually comes with stunning drivers and support for Linux.
I'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).
There 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 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.
