Suppose you know what you are doing, should gcc at least give
an option to turn off those warnings? Actually the openh323
maintainer said he has the patch and sent in three times, but
no one is listening. Can I ask him to send to you, Matt? Maybe
it can be included in Redhat gcc, and eventually i
While trying to build the openh323 project (www.openh323.org), you
will get tons of warnings. You can reproduce this by compiling a small
module:
http://www.openh323.org/bin/pwlib_min_1.1pl19.tar.gz
I checked with the maintainer about those warnings and was told
that they are harmless and gcc s
then check LINUX_VERSION_CODE
Frank
On Wed, 23 Aug 2000, Frank Liu wrote:
>
> This is not runtime, it is compile time.
> (even if it is runtime, how can uname() tell if you are running
> a kernel provided by redhat or downloaded from kernel.org?).
>
> Anyway, the program calls func
On 23 Aug 2000, Chmouel Boudjnah wrote:
> John Summerfield <[EMAIL PROTECTED]> writes:
>
> > > > [summer@emu summer]$ cat /boot/kernel.h
> > > > cat: /boot/kernel.h: No such file or directory
>
> [...]
>
> > [summer@possum summer]$ ls -l /boot/kernel.h
> > -rw-r--r-- 1 root 237 Dec
/boot/kernel.h is generated by /etc/rc.d/rc.sysinit at
the boot time if it isn't already there (or CPU changed):
check that file for the detailed logic on when/how to
generate this file.
So /boot/kernel.h may show you have a redhat system, but
doesn't mean you have a redhat kernel. I have systems
ending on the running kernel.
>
> You shouldn't #ifdef this, you should use runtime checks using the
> uname() function.
>
> Matt
>
> On Wed, Aug 23, 2000 at 02:35:23PM -0500, Frank Liu wrote:
> >
> > Since redhat kernel is a bit different from the stock
Since redhat kernel is a bit different from the stock kernel source.
In my C source code, I need to do things differently depending on
what kernel the user has. How can I #ifdef test that?
Thanks!
Frank
___
Redhat-devel-list mailing list
[EMAIL PROTE
