[lkml]   [2011]   [Oct]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Please include const-sections into linux-next
    On Fri, 14 Oct 2011, James Bottomley wrote:

    > It's not incredibly trivial: it causes a compile failure on parisc:
    > mm/percpu.c:1372: error: __setup_str_percpu_alloc_setup causes a section
    > type conflict
    > make[1]: *** [mm/percpu.o] Error 1
    > I have no idea why, though.

    Not sure why this would only happen on parisc, but I haven't looked at it
    closely. It means something qualified with const is being defined in a
    section with other definitions that are not const, or vice versa.

    For example:

    static int x __attribute__((__section__("foo"))) = 1;
    static const int y __attribute__((__section__("foo"))) = 2;

    will result in the same error. Since __setup_param() places
    __setup_str_percpu_alloc_setup in .init.rodata as const, it means
    something else has already been defined in .init.rodata without being
    qualified as such.

     \ /
      Last update: 2011-10-16 01:05    [W:0.036 / U:0.072 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site