[lkml]   [2004]   [Jun]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] cross-sparse

    On Fri, 18 Jun 2004, Geert Uytterhoeven wrote:
    > IIRC, actually the first error I got when using the native sparse was that it
    > couldn't find stdarg.h.


    > And even the non-native sparse doesn't know about architecture-specific defines
    > like __mc68000__, causing some code paths being wrong. Guess I have to replace
    > them by e.g. CONFIG_M68K.

    No, this is handled by fixing up the expected defines in the


    thing, ie x86 has this:

    CHECK := $(CHECK) -D__i386__=1

    exactly because sparse is architecture-agnostic. Same goes for 64-bit
    issues (sparse defaults to 32-bit types regardless of what the native
    format is), so a 64-bit platform like ppc64 would do:

    CHECK := $(CHECK) -m64 -D__powerpc__=1

    where that "-m64" is the magic flag to sparse for a 64-bit compile

    But your stdarg.h issue is certainly valid. I'd really like for sparse to
    be _totally_ independent of the native compiler install, and I guess we
    could do something like

    CHECK := $(CHECK) -I$(shell $(CC) -print-file-name=include)

    or similar to get this part right too, but then sparse would be hard to
    use stand-alone without the Makefile magic. Hmm.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2009-11-18 23:46    [W:0.030 / U:15.156 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site