04-29-2003
here is the website for the nvidia driver for mandrake9
here they you will need to download the first 2 download links
shockfamily.net/cedric/linux/nvidia.html
next here is were you get the other drivers for it to work the links
are here
rpms.mandrakeclub.com/rpms/nexedi/ kernel-source-2.4.19-16mdk.i586.html
and your other driver is in your installer under configure menu in kde or gnome then goto software
libcursess-devel-5.2-27mdk.i586.rpm
then after you download it it's all about 25-30 mb of loading
and after you install it with the rpms then reboot put cd#1 in the cdrom drive then click upgrade and mark all your packages you installed when you did a fresh install and let it do it's thing and reboot and wa la you now have nvidia driver and opengl at full access
10 More Discussions You Might Find Interesting
1. Programming
how to write a program that receive a string from keyboard and then print it out. i write a program:
main()
{
char str;
gets(str);
printf(str);
}
but when i compile it, the system said something like "new line is not last charicter" and sometime the system said "a3.c is up to date"... (1 Reply)
Discussion started by: dell9
1 Replies
2. Programming
How to print current date of the Unix system accessing thru C++ program ?
I wrote like this
#include <time.h>
.......
time_t tt;
struct tm *tod;
....
time(&tt);
tod = localtime(&tt);
cout << tod->tm_mon + 1 << "/"
<< tod->tm_mday << "/"
... (6 Replies)
Discussion started by: ls1429
6 Replies
3. Shell Programming and Scripting
I wonder how I shall read the result below, especially 'what'
shown below.
The result was shown when I entered 'w'.
E.g what is TOP? What is gosh ( what does selmgr mean?)?
login@ idle JCPU PCPU what
6:15am 7:04 39 39 TOP
6:34am 6:45 45 45 TOP
6:41am ... (1 Reply)
Discussion started by: Aelgen
1 Replies
4. UNIX for Dummies Questions & Answers
I just want to exit my script in a new directory from a bash shell. Problem is that the script internally changes to the directory I want to move to, however when exits is still in the original directory. Does that make sense?
ie usage: goto null
changing from /usr/bin/xtra/test/test3/
... (8 Replies)
Discussion started by: Shakey21
8 Replies
5. Shell Programming and Scripting
Having a memory lapse:
If I redefine a command using an alias or a function - How do I access the "real" command without specifying an absoulte path:
i.e.
function man
{
/usr/bin/man |more
}
alias ls='/usr/bin/ls -l'
How do I specify the ls or man command above without the... (6 Replies)
Discussion started by: kornshellmaven
6 Replies
6. UNIX for Advanced & Expert Users
Somehow someone created a file named '-ov' in the root directory.
Given the name, the how was probably the result of some cpio command they bozo'ed.
I've tried a number of different ways to get rid of it using * and ? wildcards, '\' escape patterns etc.. They all fail with " illegal option --... (3 Replies)
Discussion started by: GSalisbury
3 Replies
7. Shell Programming and Scripting
Hopefully this doesn't come off as too much of a "newbie" question or a flamebait. But I have recently begun working with a Sun Solaris box after having spent the past five years working with RedHat. From what i can tell, thing look fairly similar and the 'man' command is some help. But I've... (7 Replies)
Discussion started by: deckard
7 Replies
8. UNIX for Dummies Questions & Answers
I am trying to figure out a way to install drivers for a network card. I have a 3C905C-TXM 3Com card that appeared to check out on Solaris's Web Site. I found what I thought was a driver, although that may not be the case, because the instructions asked me to copy-and-paste the contents into a... (1 Reply)
Discussion started by: Jody
1 Replies
9. Debian
I've had no luck with help on linuxquestions so I figured I'd try here. I'm using debian etch.
The problem is that I can not install my network card because it says:
Makefile:62: *** Linux kernel source not found. Stop.
I have the kernel-headers installed.
I've looked all over the... (9 Replies)
Discussion started by: Virtuality
9 Replies
10. Red Hat
Hi all
I have a Universal PCI RS-232 card and I need to install drivers for it.
I have the drivers CD, Is there anyway I can install it from add/remove program application. It does not give me the option to browse for the drivers.
Secondly, I have tried to install it from the terminal and... (4 Replies)
Discussion started by: ndaka123488
4 Replies
build(1) General Commands Manual build(1)
NAME
build - build SuSE Linux RPMs in a chroot environment
SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm]
build --help
build --verify
DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc-
tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec
file for example), even if the package does not use BuildRoot.
build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec-
tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be
sufficient for the build.
If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If
a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current
directory.
OPTIONS
--clean
remove the build system and reinitialize it from scratch.
--no-init
skip the build system initialization and start with build immediately.
--list-state
list rpms that would be used to create a fresh build root. Does not create the build root or perform a build.
--rpms path1:path2:path3...
Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari-
able.
--arch arch1:arch2:arch3...
What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify
this option.
--root buildroot
Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable.
--useusedforbuild
Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none
are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the
same packages used for the srcrpm build.
--norootforbuild
--help Print a short help text.
--verify
verify the files in an existing build system.
.spec FILE OPTIONS
The build command interprets some special control comments in the specfile:
# norootforbuild
# needsrootforbuild
build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2,
the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to
deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec-
tively.
# needsbinariesforbuild
provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root.
ENVIRONMENT
BUILD_ROOT
The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default.
BUILD_RPMS
Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value
which will do the trick if you have the SuSE Linux DVD mounted.
BUILD_RPM_BUILD_STAGE
The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip-
tions. "-ba" is the default. You can use this to add more options to RPM.
SEE ALSO
rpm(1),
Maximum RPM:
http://www.rpm.org/max-rpm/
cross distribution packaging:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to
SUSE packaging standards and guidelines:
http://en.opensuse.org/Packaging
(c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)