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
View 9 Replies
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.
View 7 Replies View RelatedTrying 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.
I have installed some pdf readers on my notebook, and the one I most liked was evince. But there are two available evince packages: evince and evince-gtk. What is the difference between them? Does one of them have advantages as to the other?
View 1 Replies View RelatedI 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:
[Code]...
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?
Is there a VLC build for 13.37 x64? I tried Alien's 13.1 build, but the sound was missing.
View 2 Replies View RelatedI 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
[Code]....
how to build DNS server in linux slackware...
View 4 Replies View RelatedAnybody 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.
View 2 Replies View Relatedrunning current on a Lenovo S10
the b43 driver craps out every few minutes.
so i decided to try the sta driver.
i downloaded the slackbuild but it crashes with the following see attached
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,
[Code]...
I'm getting silly stuff from this when I try compiling commoncpp2. With the SlackBuild & version 1.5.3 I get
Code:
Making all in src
make[1]: Entering directory `/tmp/build/tmp-commoncpp2/commoncpp2-1.5.3/src'
[code]....
using slakware64 13.1 modified sbo slackbuild for latest version..
View 7 Replies View RelatedHas anyone successfully build Gbrainy for Slackware x64 13.1/Current?
View 2 Replies View RelatedAny links to a guide for building a slackbuid script?[URL]SlackBuild_Script don't show nothing!
View 13 Replies View RelatedI was wondering on how to use Gnome instead of the official KDE build. I know I can go to the third party slackbuilds.org. But not sure where to look on how to install it. If someone can direct me in the right direction that would be swell.
I am looking for a install step by step guide for Gnome. I was also curious if the Gnome version would provide me the same stability and speed as the official Slackware with KDE.
My second question is regarding the Slackbook project. I know I can get the pdf file and print it out but I was hoping for a book that can get shipped to me and when I purchase it the proceeds go to the Slackware organization.
I'm trying to build/install KDE 4.5.4, but I run into problems with the bindings package. Build fails with the following:
[Code]....
I'm building using the KDE slackbuild from sources dir, with the new KDE packages. edit: Well I decided to just take the risk of a not working KDE and commented out the bindings package. All other packages build fine. After this I crossed my fingers and rebooted, KDE loaded up. I gave the bindings package another go, and to my surprise it did build now. Got KDE up to date and it seems to be running fine.
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
here is the compiler output when i try to build the slackware package
[Code]...
how to build luabind properly on slackware, or I guess any distro. I have not been able to build it for the last hour and it has really made me angry. It seems everything lua pisses me off, because they really like not to use any sane build system.So far I've tried doing what they said, and I got the boost source both from the link they provide and from the slackware source directory. The one they provide make a jam0, which looks for a Jamfile, which does not exist. The one from the slackware source directory does make a bjam, but when I run it it looks for boost, not for luabind. It's just madness. If only I could get in touch with the luabind devs so I can curse at them and send them hatemail.
View 13 Replies View Relatedhere is the output:
[code]...
NVIDIA x86-256.44 fails to build against 2.6.36
I installed slackware 13 reacentlyi was trying to build wvstreams and wvdialwhen i give the ./wvdial.Slackbild it runs for quite some time and at the end while creating the package it gives me an error cannot find gzip compression utility in $PATH. and there is no tgz or txz package in /tmp folderthen i ran pkgtool and found that gzip isnt installed. the i installed it from the slackware dvd. but still i am getting the same error
View 1 Replies View RelatedWhat's the best way to use src2pkg to build sources checked out from svn?
Src2pkg expects a source tarball. But when you check out or export a program's code from svn you don't get a tarball. You just get a source directory.
Do I tar and gzip the directory? Or is there a way to skip that step?
Just a question out of curiosity: Is there a build-queue that can be used with sbopkg to build a complete Slackware repository from scratch?Just asking, because the 32 bit version of Slackware is suited to run on older computers by compiling for i486 architecture. I want to know if it is possible to rebuild the complete repository with optimizations for newer architectures, so that the programs can make use of the features of newer processors, like MMX, SSE and so on.
View 7 Replies View RelatedI can not get gtkimageview-1.6.4 to build in current. It fails with a number of errors of type:
Code:
gtkanimview.c: In function 'gtk_anim_view_get_type':
/usr/include/glib-2.0/glib/gthread.h:339: error: dereferencing pointer 'value_location.1' does break strict-aliasing rules
/usr/include/glib-2.0/glib/gthread.h:339: note: initialized from here
Edit: Ack! Duplicate post. See my thread, What a slacker learned from building Linux from Scratch..., the build notes are in this post.
View 1 Replies View RelatedWhatever option i specify with ./configure, the summary says :
jack-audio-connection-kit 0.118.0 :
| Build with ALSA support............................... : false
i tried --enable-alsa without success.
I am using the 13.1 build scripts from slackbuilds.org. I modified the scripts to build 3.2.12 rather than 3.2.10.
In 13.1 the main VirtualBox 3.2.12 OSE package built and installed without errors. The VirtualBox GUI starts without errors.
Running the virtualbox-kernel-mksrctarball.sh script built a kernel source package without errors.
Yet the VirtualBox kernel module won't build. I receive the following error:
Code:
]*** Building 'vboxdrv' module ***
make[1]: Entering directory `/dev/shm/virtualbox-kernel-3.2.12/vboxdrv'
make KBUILD_VERBOSE= -C /lib/modules/2.6.33.11-smp-2/build SUBDIRS=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv SRCROOT=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv modules
[Code].....
