Re: A job for a lazy afternoon: oskit-mach and -Wall

[Michael Teichgraeber]

A lot of warnings are caused by constructs within oskit-20010214
headers, such as

    o multi-line string literals (in about 8 files):

      |    asm volatile("
      |              jmp     0f
      |              0:
      |         ")               .


      This should be the same and fixes it:

      |    asm volatile ("\n"
      |                  "    jmp     0f\n"
      |                  "    0:\n")

      (Is the amount of whitespace before the assembler commands
       meaningfull?)


    o lines containg strings behind #e{lse,ndif} directives (some
      dozen header files)


So oskit itself will probably have to be modified. Or would it be wise
to copy these parts of oskit (header files within oskit-20010214/oskit
and sources for crtn.o, dos.o, multiboot.o) at some place within
oskit-mach to get it independent of oskit?


Michael