[lkml]   [2001]   [Dec]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Fwd: binutils in debian unstable is broken.

    On Wed, 5 Dec 2001, Alan Cox wrote:

    > > The problem appears to be that the linker is now actually doing what
    > > we asked it to do, so the `remove_foo' entry in that table now points
    > > at a function which isn't going to be linked into the kernel. Oh dear.
    > The ideal it seems would be for binutils to support passing a stub function
    > to use in such cases. That would keep the kernel stuff working nicely and
    > allow us to do panic("__exit code called"); if anyone actually did manage
    > to call one.

    We can get a panic() call (and remove the ugly #ifdef's) with
    something like this:

    in some .h file:

    #define DEVEXIT_FUNC(a) (a)
    void panic_exit_code();
    #define DEVEXIT_FUNC(a) ((typeof((a)) *)panic_exit_code)

    in some .c file:

    #ifndef DEVEXIT_LINKED
    void panic_exit_code()
    panic("__exit code called");

    change the drivers like this:

    remove: firestream_remove_one,

    to this:

    remove: DEVEXIT_FUNC(firestream_remove_one),


    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: 2005-03-22 13:13    [W:0.042 / U:16.296 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site