akozakie
11-04-02, 08:14 AM
Hi. I hope someone here can help me, I'm completely out of ideas.
After testing the driver on RedHat 7.2 (kernel 2.4.9-something) at home for a few months I decided to install it on my more important machine, running RedHat 7.1. A few days earlier I installed the newest errata kernel, 2.4.18-17.7.x. A mistake?
I just can't make NVdriver from tarball. I get a lot of weird compilation errors and warnings (nv.c->nv.o), mostly "nondigits in number" and "parse error" in the kernel headers. As far as I can tell, the headers are where they should be, undamaged, the right version (unless it's a mix), and quite readable C, no reason for such errors, but they're very #define-heavy and preprocessed nv.c does have errors. For example, the first two "nondigits", a "parse error" and
"panic_R_ver_str declared as a function returning a function" are caused by the following lines, included from kernel.h, and preprocessed:
void panic_R_ver_str(01075bf0)(const char * fmt, ...)
__attribute__ ((noreturn, format (printf, 1, 2)));
well, I can't parse this either. I have used gcc for years, but with pure ANSI code, long, complicated, but not very advanced, nothing GNU-specific. What's
wrong? Missing/superfluous #define springs to mind, but I can only guess. BTW, in the kernel.h those lines look as follows:
NORET_TYPE void panic(const char * fmt, ...)
__attribute__ ((NORET_AND format (printf, 1, 2)));
Are there any success stories with RedHat 7.1 + errata + kernel 2.4.18-17 + gcc 2.96-85 (or 2.96-108, upgrade didn't help)? Am I doing something wrong? What else should I check?
For now I just use nv. I decided not to upgrade the kernel at home yet, just in case.
Adam K.
After testing the driver on RedHat 7.2 (kernel 2.4.9-something) at home for a few months I decided to install it on my more important machine, running RedHat 7.1. A few days earlier I installed the newest errata kernel, 2.4.18-17.7.x. A mistake?
I just can't make NVdriver from tarball. I get a lot of weird compilation errors and warnings (nv.c->nv.o), mostly "nondigits in number" and "parse error" in the kernel headers. As far as I can tell, the headers are where they should be, undamaged, the right version (unless it's a mix), and quite readable C, no reason for such errors, but they're very #define-heavy and preprocessed nv.c does have errors. For example, the first two "nondigits", a "parse error" and
"panic_R_ver_str declared as a function returning a function" are caused by the following lines, included from kernel.h, and preprocessed:
void panic_R_ver_str(01075bf0)(const char * fmt, ...)
__attribute__ ((noreturn, format (printf, 1, 2)));
well, I can't parse this either. I have used gcc for years, but with pure ANSI code, long, complicated, but not very advanced, nothing GNU-specific. What's
wrong? Missing/superfluous #define springs to mind, but I can only guess. BTW, in the kernel.h those lines look as follows:
NORET_TYPE void panic(const char * fmt, ...)
__attribute__ ((NORET_AND format (printf, 1, 2)));
Are there any success stories with RedHat 7.1 + errata + kernel 2.4.18-17 + gcc 2.96-85 (or 2.96-108, upgrade didn't help)? Am I doing something wrong? What else should I check?
For now I just use nv. I decided not to upgrade the kernel at home yet, just in case.
Adam K.