Im having problem building xorg-xserver 1.8 with src2pkg
Heres src2pkg build script:
Code:
error that im getting is :
Code:
What am i doing wrong? sysconfdir=/etc directive is inside the script.
In INSTALL I can see:
Quote:
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 know this is probably simple, but I have been trying to upgrade to the latest release of Opera, downloaded the Bz2 file, and when running source to package it fails with this error. Opera seems to be the only app this fails with. I got the same error on the previous release as well, so I just gave up and waited until Slackpackage.org finally got that release.
I searched here and the net, and did in fact find a previous post about this, but, truthfully, I didn't understand the explanation at all.
Anyone have any idea how to handle this error?
I am wondering if there is a way to use src2pkg on source directories I have checked out from git? I can't see any such option in the manpage. At the moment it works if I tar it up, but I can't find a way to just use the directory directly.
View 1 Replies View RelatedHad 1.9.9 installed and upgraded using 2.1 but 'src2pkg --setup' throws an error. So I removed any existing packages and re-downloaded/reinstalled.
Same issue:
What's strange is that there is a src2pkg-helpers-1.0-x86_64-1.tgz package in the directory from which src2pkg was installed, but the setup procedure is trying to install using src2pkg-helpers-1.0.tar.bz2. So it's as if 'src2pkg --setup' is trying to install using the wrong src package ...
I can download the helpers install package which has the correct name, but I'd prefer to sort this out first.
What'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?
Im trying to make a sort of slackware using LFS.In the first chapter I have to make the kernel-headers this way :
make mrproper
make headers_check
make INSTALL_HDR_PATH=dest headers_install
cp -rv dest/include/* /usr/include
Can I do these steps also with using a the source and src2pkg ?
auto generated doinst.sh files when using the -A switch.
The file will contain link removal and generation for libraries in the package eg.
When upgrading to a new version of the app, the library name might change eg.
So the links that doinst.sh creates is now incorrect. ie. the link is now dead because it points to a file that does not exist. Does one have to regenerate .src2pkg and resulting doinst.sh when using a new version of the package or is there another way to have doinst.sh regenerated without redoing .src2pkg?
I have a little problem installing src2pkg on my linux from stratch system.
I downloaded the package and saved it on /
After that I did cd /usr/libexec/src2pkg/src2pkg-helpers
There I did a sh src2pkg.setup
But now I'm getting this error message :
/usr/libexec/src2pkg/13-make-description: line 438: 'read_pkg_info_desc : not a valid identifier.
Do anyone have any idea what went wrong ?
when i upgraded to slackware-current few days ago i tried to create packages with src2pkg and i get this:
Checking for Makefile rule: 'install' Okay
Checking support for DESTDIR (or similar) - Found DESTDIR
Installing using DESTDIR - Using:
make DESTDIR=/tmp/xf86-video-intel-2.10.901-i486-1 install
Notice - Possible error running 'make install'
FATAL! Running make install has failed with error: 1
Try using INSTALL_LINE 'make -i install' Exiting...
is it because of i have slackware 32bits i installed src2pkg successfully on slackware 13 but on slackware-current if i remove it and do src2pkg --setup i get error something like cannot live without it every time. when wanting to create src2pkg-helpers.
but i want to know what im doing wrong ?
before i created packages successfully. i execute src2pkg as root
I'm currently trying to install unRaid on Slackware following this tutorial :[URL].. I'm new to Linux and after many hours, i finally managed to build the new kernel for unRAID (2.6.32.9). But audio on HDMI port doesn't work I tried alsaconf without success. HDMI sound works when i boot into the old kernel.
My codecs are :
Code:
root@unraid:~# cat /proc/asound/Intel/code* | grep Codec
Codec: Realtek ALC888
Codec: Intel G45 DEVIBX
Code:
lspci -v:
[Code]...
I'm very keen on getting Mumble installed on my slackware -current 64 bit install. I found a slackbuild script for 12.2 here, but changing the version number resulted in failure. I also tried following the build instructions on the Mumble website, which failed with the following.
Code:
neil@slackbox:~/Downloads/mumble/mumble-1.2.2$ qmake -recursive main.pro
Reading /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro
WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead.
WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead.
[Code]...
I'm trying to build erlang-otp using slackbuild script from http://slackbuilds.org/. I've got these errors while building:
Code:
checking lex output file root... configure: error: cannot find output from flex; giving up
configure: error: /bin/sh '/tmp/SBo/otp_src_R14B01/lib/megaco/./configure' failed for megaco/.
configure: error: /bin/sh '/tmp/SBo/otp_src_R14B01/lib/configure' failed for lib
GNU flex is in system, so I have no idea what has goes wrong. Maybe someone know the issue?
I would request for a step by step procedure for building a slackware 13 guest OS in xenserver 5.6
View 3 Replies View RelatedI did some research and located a nice packaging script "nspluginwrapper.SlackBuild" so I decided to go that route and build a Slackware package for nspluginwrapper. The error I get is the inability to find /usr/include/gnu-32.h when it is building the nspluginviewer. Not realizing that the viewer is what is used by the Browser I edited the configure script to not build that piece and it worked fine after that but of course that defeated what I was trying to do. What it looks like is that I need to have 32 bit headers or both headers and libraries installed to be able to build the viewer. I just want to use the acrobat reader plugin in Firefox. Would someone please provide an explanation of what I need to do to build nsplguinwrapper viewer?
View 1 Replies View RelatedI tried building but got errors at the end.
make: *** No targets specified and no makefile found. Stop.
I've just tried to compile lilypond using a fresh SlackBuild from slacky.eu site.
I have all deps and I use current Slackware that was gradually upgraded using all current packages since version 12.2. So I call it "version 13".
After a minute or so I got this ugly sentence:
I'm using Slackware 13.1, just messing around with some stuff before I upgrade to 13.37. I really want to get a decent build of Desmume working, but the 3D engine for it requires OSMesa to be enabled. I've removed the initial Mesa package that I installed from the Slackware DVD and I'm trying to recompile mesa-7.8.1 so that OSMesa is available for the system. However, I keep running into problems.
Code:
./configure --enable-gl-osmesa
When I run those options for the configure command and compile it, Mesa builds alright and gives me a working libGL just fine. It also gives me libOSMesa. Yet, when I compile Desmume to specifically use OSMesa, its configure script says that it can't find OSMesa at all. But running ldconfig -p, the output shows libOSMesa.so in /usr/lib. The symlink is up to date too, and I've recreated it several times.
Code:
./configure --with-driver=osmesa
When I build Mesa using these configure options, I don't get libGL (well, that's expected, the manual says as much will happen). But apparently libOSMesa is installed just fine. When I went to compile Desmume, no gripes about OSMesa, but Desmume needs both libGL and OSMesa to work properly.
So my question is, how can I install Mesa so that I have OpenGL and OSMesa working together? I've been able to get one working, but not both. I don't know how to get OpenGL on Slackware without using the Mesa package, but the package isn't cooperating. I'm on Intel graphics too.
Since there was a lot of talk about virtualization I thought I try kvm -- before I used VirtualBox. I took the SlackBuild from SlackBuilds.org and got an error with u8 as type in /usr/include/scsi/scsi.h. (sorry, I don't have the exact error message anymore..) I searched for its definition and I only found __u8 in /usr/include/linux/types.h. Then I searched the web and found a "fix" which says I have to change u8 from /usr/include/scsi/scsi.h to __u8. This problem was solved, but when I run the SlackBuild now it stops at some point and I don't know why. These are the last few lines of output:
CC arm-softmmu/translate.o
CC arm-softmmu/tcg/tcg.o
CC arm-softmmu/tcg/tcg-runtime.o
CC arm-softmmu/fpu/softfloat.o .....
LINK i386-softmmu/qemu
AR arm-softmmu/libqemu.a
LINK arm-softmmu/qemu-system-arm
root@tux:/home/christian/Downloads/kvm#
I put an echo after the make for building kvm and I put an echo after "make install". None of them are printed.
I've been trying to install Compiz 0.8.4 from the source code provided by the Compiz people.
However, when I run make on the first set of code (compiz-0.8.4 tar package), it halts with the following error:
Code:
As well as --disable-gconf and --disable-gnome since gnome isn't install on Slackware (I've also tried it without those, but it picks up on it anyway and throws them out). The folder I'm running this from is /root/Desktop/Compiz Fusion/compiz-0.8.4.
Im trying to build the glade3 slackbuild on slackware x64 -current, but everytime i try to build it, i get the same error:
Code:
There are no dependencies listed in the slackbuild, so i'm confused as to what could be causing this error.
I am trying to make a slackbuild for the bigforth package (source:[URL]However when I run make I get the following error messages:
Code:
bash-4.1# make
env LIBDIR=/usr/local/lib/bigforth SRC=/usr/local/lib/bigforth/src ./forthker -e " include startup.fb ' .blk
[code]....
I have tried building a couple of packages like gst-plugins-bad, Qtcurve-Gtk2, but I get make error at this line:
Code:
For gparted I'm getting:
Code:
Using Slackware64 - current
I'm building a NAS, based on the Intel SS4200. There are 4 drive bays in the machine for use with SATA disks, two of which I plan on filling now, the other two which I plan on filling later. The box also includes an IDE connector to which I will connect an 8GB Disk on Module onto which I will install Slackware. I wish to have all drives in the box show up as one contiguous volume. What partitioning/LVM/RAID configuration can I use which will allow me to:
1. Add a disk and transparently grow the available space of the volume?
2. Replace a disk with a larger disk and transparently grow the available space of the volume?
3. Lose a disk to hardware failure and replace it with a new one with no data loss?
If I use RAID 5, I'm pretty certain I can get numbers 1 and 3 above, but I'm not sure about number 2. The downside is that I'd have to start with 3 disks in the machine, and I'm unsure if adding a 4th disk whose size is larger than each of the 3 starting disks would lead to wasted space. For instance, if I start with three 1TB drives in RAID 5, and then add a 2TB 4th drive, would my available size go from 2TB to 3TB? Or from 2TB to 3.xTB?
Is it important in a RAID 5 setup to have all disks the same size? With LVM, I can certainly get number 1 above, but what about 2 and 3? I know you can use LVM to present many disks or partitions as one contiguous volume, but if I have two 1TB drives in one volume, and only have 300GB of data, then would the second drive remain empty until I broke the 1TB barrier? In this case, it's wasted space from the get go. I suppose another option would be to start with RAID 1 until I can afford a third disk.
When adding the new disk, could I switch to RAID 5 without data loss? I'm planning on maintaining a full mirror of the NAS on some USB disks as a backup, so if configuration changes to the NAS require wiping the disks and restoring from backup, it's not a total loss. However, it certainly makes me nervous to be in a state where only one copy of the data exists, so I'd rather find a solution where I can add and upgrade disks in the NAS without relying on the backup copies.
I've done a clean install of Slackware 13.37 64-bit and am having trouble with building the Perl modules for Bugzilla 4.x.x (downloaded yesterday with bzr). This same problem exists with both Bugzilla stable and 4.1.2+.Executing checksetup.pl results in
Code:
checksetup.pl
* This is Bugzilla 4.1.2+ on perl 5.12.3
[code]....
Trying to get Midori browser from SBOpkg's and one of the dependencies is libsoup.configure: error: GLIB 2.21.3 or later is required to build libsoup.Anyone able to give me a pointer in the right direction to overcome this.
View 2 Replies View RelatedI use Slackware 13.0 with the 2.6.33.2 kernel, and I use GnomeSlackbuild.I tried to get help on their discussion group, but I didn't get any.I'm trying to build gnome-power-manager 2.30, because it uses the new upower interface (so it seems). I have GTK+ 2.18.9.
View 3 Replies View RelatedI have a brand new installation of 13.37 but I can't seem to get the nvidia-kernel (64 bit only) Slackbuild from slackbuilds.org to build. I have the nvidia driver installed and working on 13.1 so I am not desperate yet: although I thought that it could just be something with the older Nvidia driver so I waited for the updated release but it fails in the same way.I have uninstalled xf86-video-nouveau and installed xf86-video-nouveau-blacklist-noarch-1.txz from /extra.I have also installed libvdpau from SBo. The nvidia-driver Slackbuild builds fine.I am using the stock 2.6.37.6 huge kernel but have also tried the 2.6.38.4 kernel from /extra and the 2.6.38.7 kernel from Slackware-current.Here is the error message I am seeing:
Code:
root@DarkStar:/home/server/Utils/Packages/Slackware/13.37/64/nvidia-kernel# SRCSUFFIX="-no-compat32" ./nvidia-kernel.SlackBuild
[code]....
So I've wanting to try out the new development branch of compiz (0.9). I made some slackbuilds a while back and installed all of the necessary packages for the compiz window manager. However when ever I tried to launch the program using "compiz --replace ccp &" I would get a segmentation fault. I forgot about it but today I decided to give it another go and after a few hours I decided to try and see what would happen if I just built compiz-core from source with out using a slackbuild, and sure enough it now works. I have hacked the script trying different combinations to try and make it work but no matter what I try unless I install from scratch (directly into the tree) it will not work. If anyone has any ideas on how to fix this so I can make an actual slack package please let me know. Also I used the main developers forum post as a referencem you can view his instructions here [URL]..
View 1 Replies View RelatedI've been trying to build mjpegtools 1.9.0 on multilib current and it fails everytime with: PHP Code:
[Code]....
I've searched for maybe a newer version than 1.9.0 and it doesn't seem to exist. I'm not sure what direction to go with this.
