l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
October 7: Social gathering
Next Installfest:
TBD
Latest News:
Aug. 18: Discounts to "Velocity" in NY; come to tonight's "Photography" talk
Page last updated:
2007 May 19 21:18

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
[vox-tech] Re: [vox-tech fix] compiling cvs nv
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vox-tech] Re: [vox-tech fix] compiling cvs nv



Jimbo wrote:
Alex Mandel wrote:
Jimbo wrote:
Greetings:

My kde desktop has been crashing. Found out that there wasn't enough air going over my gpu.

With this I searched and found a program called nvclock. After d/l via synaptic and trying it it wouldn't recognize my gpu (8800gtx). I was fortunate to talk to the programmer in irc channel #nvclock in which I have to cvs the updated nvclock then compile it. With his help he gave me the shell commands that then proceeded to unload a whole bunch of files. He had to go to bed so I didn't bug him on compiling.

I have tried to self teach myself how to compile (via googling) what I have just d/l but finding that it is becoming a very huge obstacle.

If someone has the time can someone please enlighten me? I have no idea where to begin.

If this helps this is the shell imput/output: (had to d/l cvs)

The typical I don't know what I'm doing nor do I need to compile.
1. Make sure you have compiling tools, on Ubuntu a package call build-essential has it all. gcc/g++ and all the other goodies.
2. cd into the directory nvclock
3. ./configure
4. make
5. make install or checkinstall(I prefer checkinstall as it makes a package for your system which makes it easy to uninstall later)- note checkinstall is different from your normal packages and it may or may not work on other people's computers, mileage varies and it's not the technically correct way to compile packages.

hope that helps,
Alex
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech

[root@localhost jimbo]# cd /home/jimbo/nvclock
[root@localhost nvclock]# ./configure
bash: ./configure: No such file or directory
[root@localhost nvclock]#
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech

Welp I have compiled my first doo dad. Although rocky and not exactly what I had in mind I did it, even if it was wrong. I had to use a command ./autogen.sh

What I don't understand is since this was kinda an upgrade to an existing program then why didn't it do just that? The old program is still there in its same place.
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.