Slackware :: Slackware 13.1 Build Package Net-snmp With LmSensors Support?
Nov 17, 2010
I downloaded from http://ftp.nluug.nl/os/Linux/distr/s...ce/n/net-snmp/ source and I build new package and works ok no errors. If I change net-snmp.SlackBuild and add CFLAGS --with-mib-modules=ucd-snmp/lmSensors --with-ldflags=-lsensors while I need lmsensors support in net-snmp. But the package compiling ends with error:
Work I've got 2 slackware 13.1 64 machines, and they work just fine: Basic installation, everything ' bog standard 'When in Dolphin or Konqueror, I can ' click ' on Network Services and all the other MS Window machines pop-up.
@Home I've got 2 slackware 13.1 64 machines, they don't work fine. Basic installation, everything ' bog standard '. When in Dolphin or Konqueror, I can 'click' on Network Services and 'KDE has been build without Zeroconf support' pops up in Konqueror or is displayed in Dolpin..
Is it my netwerk @ Home (with an old Windows Server in it) or is something missing in the installation? Under MS windows (from within a virtualbox, brigded network) both machines can browse the network just perfectly: I even got a XP machine 'joined' in the domain on the windows server). Clueless since a google on the error + slackware give me Zero. Zeroconf in the slackware forum give me some midly related
I'm building my slackware system from a minimal set of packages. I've got X and fluxbox up and running, and I'm trying to "slack-build" feh which depends on imlib2 to set background wallpapers. The problem is trying to "feh" any image gives the error message:
Code: feh WARNING: wall2.jpg - No Imlib2 loader for that file format feh - No loadable images specified.
I've been trying to build gCompris a childrens educational package. I got the compressed source & build from slackbuilds.org The only dependency mentioned in the readme was gnet so built and installed that ok .
With gCompris the build was progressing fine until a it hit a point at " text2html" .Looked in the 4th install disk of slackware 13.37 no sign of either.looked in slackbuild also no mention of either.
I have a small problem with lmsensors and snmp since I upgraded my small server from 9.10 to 10.04. I use cacti to monitor my servers usage, disk space as well as temps and fans. This was running very fine before the upgrade, but now I don't get data anymore from lmsensors. It seems that SNMP doesn't give this information as before. (Cacti log says: "No sensor data was returned from SNMP")
sensors give the following output:
Code:
w83627dhg-isa-0290 Adapter: ISA adapter Vcore: +1.12 V (min = +0.00 V, max = +1.74 V) AVCC: +3.41 V (min = +2.98 V, max = +3.63 V)
I am building a minimized 6.2.2 linux kernel using slackware on a dinosaur of a computer: AMD Athlon +1700 Single Core processor, 1gig of DDR SDRAM. This is my first time compiling a linux kernel, so before I make any major mistakes, I could use some help in determining which filesystems I absolutely must enable support for. Ext2 is allready in.
I tried to build several packages designed for slackware 13 at slackbuilds. Those was a simple apps like ardour, audacity for example.
[Code]...
My CPU is AMD Phenom 9550 Quad core. It supports 64 bit. My os is slackware 13_64. What do I need to change in slackbuild to create a txz package for those apps?
I have installed multilib support in my 64bit slackware 13.37 installation than I proceed it to install google earth from slackbuilds... and did ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3Now when I try to run google earth I get:[ 760.092745] googleearth-bin[3647]:segfault at 984f7d31 ip 00000000984f7d31 sp 00000000ffbfe100 error 4
We are pleased to present one of our new creations: pkgbuild, a tool written in standard C++, using libCURL, ZLib, BZip2 and libLZMA (part of XZ). It is a modern Slackware packages builder, network-transparent, multi-architecture, designed to greatly simplify the creation of a package, automatically executing the required post processing.
What does it do? Recognize and build packages for the following architectures: i386, i486, i586, i686, x86_64, IA64, IA32e, s390, s390x, sparc and sparc64.
I am very happy to announce that today I succeeded to install full Slackware ARM on the pandaboard: URL...I did the following:
* sd with 2 partitions, one (vfat) for bootloaders (MLO, u-boot.bin) and uImage and the other one (ext2) for minirootfs * copy xloader (MLO), uboot and uImage from Angstrom distro on the first partition * copy Slackware ARM minirootfs on the second partition with Angstrom modules in the usual path (/lib/modules/...) * boot in ARMedslack * install all the others packages via NFS
I had to make some changes to configuration files as indicated here:URL...The next step is to build a kernel and modules for omap4 by myself and use them instead of the Angstrom ones.One question: is there any kind of package manager, such as slap-get, sbopkg, etc. for Slackware ARM? If not, can I use the SlackBuilds from slackbuilds.org? How to modify them?
Trying to install SW 13.1 (on DVD) on the following system: M/B Intel: DX38BT Processor Intel Core 2 Quad Q6700 - 2.66GHz, 8MB Cache, 1066MHz FSB, Socket 775 Memory Corsair Dual Channel 8192MB PC10600 DDR3 1333MHz Memory (4x2048MB) Graphics Diamond Radeon HD 3850 Video Card - Viper, 512MB GDDR3, PCI Express 2.0 P/S Ultra 1000W
My goal is to install the i386 build on one partition and the 64-bit build on another. I have been away from Linux for a while and am sick to death of Win7, want to come home. :-}
Booted on i386 side of DVD, system freezes after a couple of lines that start with ATA2. Does not respond to 3 finger salute, ctrl-c, nothing. Have to press reset. I have tried both huge.s and hugesmp.s kernels
Booted on 64-bit side, comes up fine. I performed the install, selected for automatic lilo install. Lilo install hung but I was able to reboot. I booted off the 64-bit side again, entered the following: huge.s root=/dev/sde3 rdinit= ro It booted fully to the login prompt but the keyboard does not work, no input.
How much support does Slackware have for drivers?I have an Asus motherboard, and the onboard sound doesn't work with Ubuntu, and also it won't recognize my HP printer.Would I have better luck with Slackware?
I am trying to convince the "higher ups" in a small office of about 15 users about migrating from windows to Slackware, one question I have is how long after a release are security updates available? I subscribe to the security mailing list and often see updates that go as far back as Slackware 8.0. What would the safe number be? 5 years, 10 years? Longer? Any input would help me with my cause of eliminating windows all together.
I found the source, but it's missing a few header files.I tried downloading a few but it wasn't working correctly.I'd rather install this package properly.
I'm elated when I see software download pages that include a binary Slackware package.wrt KVIrc, their Slackware package is at the top of their list of binaries.They've got an rpm too, but it's SuSE, not Redhat - I found that to be pretty kewl too.I wonder if they're Slackers... hm...Well, that having been said, there's also a SlackBuild for it at the repository.I'm going to give this client a spin and see how I like it.Here's the URL: http://www.kvirc.net/?id=releases&pl...=4.0.2&lang=enUPDATE: The mirrors I checked are reporting 404 errors... bummer.
to build from either unpacked tarball or CVS source:
autoheader autoconf ./configure # (--help to see options) make # (the make from GNU, sometimes called gmake) su # Possibly required make -n install # (to see where all the files will go) make -s install # (to really install, -s to silence output) code....
I think that trouble is in autoheader. I don't now does src2pkg (2.1) support it.Is it impossible to build a package of privoxy with src2pkg?
I have been trying to build FreeCad and k-3d for Slackware......not much luck...
FreeCad has two build systems... automake and cmake, both fail despite the fact that dependencies are installed...cmake build system fails at about 80% complaining that it cannot find
Quote:
I guess the build system is broken...About K-3d, the thing builds alright..had to install libsig++ glibmm cairomm pangomm and gtkmm as dependencies...
The thing actually builds but when i try to make the installable package, I have to use trackinstall -i="make -i install", but the installable package fails to launch because it cannot find stuff in /usr/share/
I'll teach here how to build a package for Slackware64 13 This is a multiphysics Finite elements code made by the Finnish check [URL] If their Finite Elements Codes are as "user-friendly" as their gals are, we should all be fine...( Just kidding here, ppl) Now, to work : Download the sources from SVN
I've been trying to replace the KDE apps I still use in Fluxbox and I was trying to build epdfview using the Slackbuild. When it had to build its parts that depend on poppler, make crashed. The same thing happened when I tried to build evince. What is going on in my PC? I'm running an updated -current 64 bits. I made screenshots of both errors
Anybody use xemacs with slackware? If so, how did you build or install it? I've used it in the past with other distros. I briefly tried emacs but because I was used to xemacs, gave up on it.
Here are the last several lines from running the Slackbuild script.
Quote: make: *** [.obj/server.o] Error 1 make: *** Waiting for unfinished jobs.... In file included from /usr/include/libavutil/avutil.h:81:0, from engine/ffmpeg_enc.h:35, from slideshow.h:19,
I've been trying to replace the KDE apps I still use in Fluxbox and I was trying to build epdfview using the Slackbuild. When it had to build its parts that depend on poppler, make crashed. The same thing happened when I tried to build evince. What is going on in my PC? I'm running an updated -current 64 bitsI made screenshots of both errors, which can give you guys more information.