Slackware :: NVIDIA X86-256.44 Fails To Build Against 2.6.36
Oct 22, 2010here is the output:
[code]...
NVIDIA x86-256.44 fails to build against 2.6.36
here is the output:
[code]...
NVIDIA x86-256.44 fails to build against 2.6.36
using slakware64 13.1 modified sbo slackbuild for latest version..
View 7 Replies View RelatedI'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.
I 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
I had an issue with the module build for vbox 3.1.2 breaking on the latest kernel ( /etc/rc.d/rc.vboxdrv setup ). Apparently the issue is that a kernel header (autoconf.h ) has changed its location in the module tree and hence the issue.
2 options:
1. upgrade to 3.1.4
2. create a symlink as follows
cd /usr/src/linux/include/linux
ln -s ../generated/autoconf.h autoconf.h
I started slax in cli mode and tried to install nvidia driver before running X but it won't install. My log:
Code:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Sun Jan 10 04:21:14 2010
option status:
license pre-accepted : false
Update : false
Force update : false
Expert : false
uninstall : false
Driver info : false ....
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details.
as I'm advancing in building some nice rpm I finally wanted to install on of my gems also the build was successful the actual install fails with missing dependencies.
Code:
$ rpm --root /home/sascha/rpmbuild/ -i ./RPMS/x86_64/memcached-1.4.1-2.x86_64.rpm
error: Failed dependencies:
libc.so.6()(64bit) is needed by memcached-1.4.1-2.x86_64
libc.so.6(GLIBC_2.2.5)(64bit) is needed by memcached-1.4.1-2.x86_64
[code]....
I have an init script running as a special build user which performs an automated build that fails with (Too many open files).I updated /etc/security/limits to allow the special user more open files, but that didn't work - the init script still isn't allowed more open files.Here's a demonstration of the problem;
Code:
$ su - sbsbuild -c "ulimit -n"
Password:
[code]....
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.
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:
[Code]...
recently i have been building my own kernels, and have been successful. however, over the last 2 days, using the proper documentation and methods i always get to the same point that rpmbuild fails at. it's very frustrating to say the least...i am somewhat new to fedora, as i tend to use debian-based systems or freeBSD, where the approach and methodology is quite different to that of redhat. the command used:
rpmbuild -bb --with baseonly --with firmware --without debuginfo --target=`uname -m` kernel.spec
this builds the kernel with modules(needed by me) and this is where it fails:
[Code]...
if anyone has fix let me know, i can't update or upgrade rpmubuild without doing so to my whole system, so i hope this isn't a bug in rpmbuild.... i already had to upgrade yum & yum-utils because of a bug that wouldn't let "builddep" work. (come on fedora, this is a standard release, i shouldn't be having problems with yum or with rpm! this is apart of the OS's core isn't it? anyway, if someone who is in the know has a solution
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'm trying to move an existing webserver from an old machine to a machine with Fedora 12 installed on it. ThSince the version available in the repository is version 2.X I downloaded the source from apache.org and tried to compile it. I ran configure using the default options and it an without any warnings or errors. However when I run make it fails with the following error:
gcc -c -I../os/unix -I../include -DLINUX=22 -DHAVE_SET_DUMPABLE -DUSE_HSREGEX -DNO_DL_NEEDED `../apaci` htpasswd.c
htpasswd.c:101: error: conflicting types for getline
/usr/include/stdio.h:653: note: previous declaration of getline was here
make[2]: *** [htpasswd.o] Error 1
make[2]: Leaving directory `/root/apache_1.3.41/src/support'
make[1]: *** [build-support] Error 1
make[1]: Leaving directory `/root/apache_1.3.41'
make: *** [build] Error 2
what the problem and more importantly the solution to this problem is?
I am using my athlon64 machine running Debian squeeze i386 to build some packages optimized for a K6-2 machine. I decided to start with libc6 since most packages depend on it.
I installed the build dependencies via
Code:
apt-get build-dep eglibc
Then, as an unprivileged user, I downloaded the debianized source via
Code:
apt-get source eglibc
I changed to the source directory and ran
Code:
dpkg-buildpackage -rfakeroot -us -us
About 6 hours later, the build failed: [URL]
There were four config.log files:
Code:
./build-tree/i386-xen/config.log
./build-tree/i386-i686/config.log
./build-tree/i386-libc/config.log
./build-tree/i386-amd64/config.log
All of which end with exit status 0. They are also about 1600 lines each so I haven't read them entirely. If someone can tell me which one/ones is/are relevant, I will post it/them to a pastebin.
Question is: How do I compile a package for little endian on big endian proceessors? Gpart is known to build on arm-el, ia64, i386, and amd64. I'm using gcc 4.3 and have versions 3.4, 4.1, 4.2. Build environment is debian lenny, powerpc.
View 4 Replies View RelatedI had no problems up to the newest kernel version. But for 2.6.40-4 akmods fails to build the kmod with the following error:
Code:
Building RPM using the command '/usr/bin/akmodsbuild --target x86_64 --kernels 2.6.40-4.fc15.x86_64 /usr/src/akmods/VirtualBox-OSE-kmod.latest'
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40-4.fc15.x86_64/vboxnetflt/vboxnetflt.mod.o
LD [M] /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40-
[Code]...
I have used the NVidia proprietary drivers for awhile. Yes, I know about nv and I even know about the prepackaged ones, but I've never minded getting the latest from NVidia, dropping out of X, and running the install which automatically rebuilds everything.
I recently took the synaptic update to 2.6.32-24. It worked fine and -- I guess -- migrated my driver. I didn't think about it. For no particular reason today I tried to build the latest NVIDIA driver (256.53 -- had been on an earlier 256 series). The build failed with some conftest failures. Even trying to rebuild the working driver failed. Reverting to 2.6.32-23 allowed both to be built and they work. So something the NVIDIA installer is expecting headerwise must be different between 2.6.32-23 and -24.
i want to build .deb packages from the official nvidia installer (one for the driver and one for the kernel module). How can I do it?
View 11 Replies View RelatedIm trying to build Mandrivas theme ia_ora from source but it fails.
Code:
sh install.sh
-- Found Qt-Version 4.7.1 (using /usr/bin/qmake-qt4)
-- Found X11: /usr/lib64/libX11.so
-- Found KDE 4.6 include dir: /usr/include/kde4
-- Found KDE 4.6 library dir: /usr/lib64/kde4/devel
[Code]...
I can't get the nVidia kernel module built. Each time DKMS runs to install it (I'm trying to install it with the nvidia-kernel-legacy-173xx-dkms package on ), the build fails with a different error. Here is an exemple /var/lib/dkms/nvidia/173.14.27/build/make.log (I have a geForce FX 5200 on the computer I'm trying to install the nVidia driver):
DKMS make.log for nvidia-173.14.27 for kernel 2.6.32-5-686 (i686)
dimanche 24 avril 2011, 17:28:09 (UTC+0200)
make: entrant dans le r©pertoire /var/lib/dkms/nvidia/173.14.27/build
[code]....
I have not had this problem on this machine since the days of fedora 1. The problem is that there is not kmod-nvidia driver for the current kernel in the rpmfusion repo, nor akmod can build one at boot up. Looking at the log files, akmods spits this error message:
Quote:
09 Jul 14:54:26 akmodsbuild: + make -j2 SYSSRC=/usr/src/kernels/2.6.29.5-191.fc11.i586 module
09 Jul 14:54:26 akmodsbuild:
09 Jul 14:54:26 akmodsbuild: The C compiler 'cc' does not appear to be able to
09 Jul 14:54:26 akmodsbuild: create executables. Please make sure you have
[Code].....
When we expect a new rpm from current 195.36.15 nvidia driver? And if it is possible someone to get my a link to this rpm,build for my. like step by step "How to build rpm from nvidia source driver.All this is because i don`t like to install after every update!
View 1 Replies View RelatedI'm trying to build the package zaptel on debian, but I'm encountering two errors:
1- When I try to run the "make menuselect" command, I get an error stating that I need ncurses which is missing. I tried to get it installed but didn't get to do it yet.
2- After that, there's the command "make" I think it's to build the package. Yet again this fails, and the error I get is "you do not appear to have the sources for the 2.6.26-2-686 kernel installed".
before i get a lot of annoyed responses, I did check the forum and found a couple older previous threads on this topic, but they don't seem to really explain any real solutions to the problem im having.Here's the story- I was looking around for instructions and found this "howto guide" on installing nvidia display driver [URL]I went through the steps he listed:
downloaded the driver packages, install the dependencies from the shell, and then i pressed CTRL+ALT+F2 to get out of X and into text mode. I stopped my gdm with the command: sudo /etc/init.d/gdm stopand then i tried to install the driver using: sudo sh (on my NVIDIA driver- his version was a bit outdated compared to the one I downloaded)But here is where the problem starts, as I go through the installation process and click yes, i reach the "progress bar" then the screen says "unable to build the NVIDIA kernel module". and then it just exits. What is going on here? Am I missing some other package or file?
I'm trying to install the nVidia driver for a fresh Installation of OpenSUSE 11.4 (32-bit) but I'm running into some issues. I followed the instructions (SDB:NVIDIA the hard way - openSUSE) using the driver binary mentioned in the workaround link (NVIDIA DRIVERS 256.53 Certified) but the installer fails while building the kernel module with the following errors:
Code:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Sun Mar 13 17:32:56 2011
[code]....
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 installed slackware 13.1 x86_64 bit with multilib, and its been about a month already, I'm really enjoying slackware but I am being troubled with my nvidia card, and I need to get my 3D acceleration working. And I've been looking around the net for information and kept on trying to make my nvidia card to work but to no avail. I cant get X to start, once I put in a xorg.conf stating to use the nvidia card. After troubleshooting for almost 2 weeks and now at my wits end, I now come humbly looking for help in linuxquestions slackware community forum.I've installed nvidia 64 bit kernel, drivers from slackbuilds (version 256.44). The laptop model I'm trying to get it working is an -ASUS K52J Intel Core i3 2.40Ghz with 2GB RAM and with an Nvidia Geforce 310M with 1GB dedicated VRAM.
View 14 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]....
I started a thread asking for advice in the hardware forum. I didn't want to post a duplicate thread, but I was unable to get it moved here, so I'm kindly asking you slackers to help me install the aforementioned driver.
View 1 Replies View Related