A quick fix -
in fs/nfs/nfsroot.c, search for a line having this (line 135, in
2.6.32)
static const match_table_t tokens __initconst = {
and make it
static const match_table_t tokens /*__initconst */ = {
You will then be able to compile it. By doing this, you waste a couple
of hundreds of bytes as now tokens always exist as opposed to being
freed after the kernel finishes initialization.
The reason for this issue could be the compiler refuses to accept two
different types of data in a same section, which is weird, maybe there
are some implicit alignment requirements defined somewhere, which I
didn't look into.
Cheers,
Rong
On Apr 28, 5:54 am, A Curtis <[email protected]> wrote:
> Has anyone else run into this?
>
> - branch 2.6.36
> fs/nfs/nfsroot.c:403: error: __setup_str_nfs_root_setup causes a
> section type conflict
> fs/nfs/nfsroot.c:403: error: __setup_str_nfs_root_setup causes a
> section type conflict
> make[2]: *** [fs/nfs/nfsroot.o] Error 1
> make[1]: *** [fs/nfs] Error 2
> make: *** [fs] Error 2
>
> Googling around revealed this as an old bug but nothing reported
> recently. The mail lists indicated that this may be a compiler bug.
>
> Is there a bug related to this in android-ndk-r5b/toolchains/arm-
> linux-
> androideabi-4.4.3 ??
>
> Ideas?
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-kernel
