> Once I got back to my saved mailing list archive and re-read the
> documentation, I discovered that I was trying to compile the current version
> of rtlinux code with (the equivalent of) a makefile designed for v1-code.
> There are apparently a bunch of compiler switches and command-line #defines
> that are setup in rtl.mk.mk that are absolutely necessary for the current
> .h-files that weren't needed in v1. After including that file into my
> makefile AND using the CC defined in it instead of my own version of CC, I
> found that everything compiled with no problem at all.
Yes, rtl.mk is essential for building RTLinux programs.
> Which brings me to two points::
> 1. My original, plaintive cry for help went out over two weeks ago. How
> come no-one answered it until now?
Can't speak for others; I've been on vacation.
The compiler flags are (mostly) not specific to RTLinux. Any time you
compile a Linux kernel module, you'll see something very similar.
Michael.
> But much more importantly
> 2. There are some things about what rtl.mk does that see to me to be
> less than "ideal":
> A. It seems to me that turning off some warnings, e.g.
> -Wstrict-prototypes -fno-strict-aliasing
> to avoid a flood of diagnostics isn't the right way to get a clean
> compile because it mignt suppress diagnostics about my own code that I might
> have needed to see
>
> B. Implementing #defines fromt the compiler command-line
> -D__KERNEL__ -D__SMP__
> -DCPU=586 -D__RTL__
> -DMODULE -D_LOOSE_KERNEL_NAMES
> most of which (I believe) only affect the rtl-header files and should have
> been in rtl.h rather than cluttering up the command-line. Further, some of
> these ( like __SMP__) might have no applicability to my system and at least
> one ( CPU=586) could be wrong for some implementations.
>
> All of this makes we wonder exactly what woes we're trying to cover up
> with these things.
>
> Norm
>
>
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/
