Andrew Morton wrote: > On Tue, 16 Oct 2007 12:48:48 +0530 Kamalesh Babulal <[EMAIL PROTECTED]> wrote: > >> Hi Andrew, >> >> The link failure while compiling the kernel with allyesconfig over the lpar, >> which was seen in 2.6.23-rc8-mm2 (http://lkml.org/lkml/2007/9/30/2) is still >> seen in 2.6.23-mm1, the link failure is >> >> ld: arch/powerpc/kernel/head_64.o(.text+0x80c8): sibling call optimization >> to `.text.init.refok' does not allow automatic multiple TOCs; recompile with >> -mminimal-toc or -fno-optimize-sibling-calls, or make `.text.init.refok' >> extern >> ld: arch/powerpc/kernel/head_64.o(.text+0x8160): sibling call optimization >> to `.text.init.refok' does not allow automatic multiple TOCs; recompile with >> -mminimal-toc or -fno-optimize-sibling-calls, or make `.text.init.refok' >> extern >> ld: arch/powerpc/kernel/head_64.o(.text+0x81c4): sibling call optimization >> to `.text.init.refok' does not allow automatic multiple TOCs; recompile with >> -mminimal-toc or -fno-optimize-sibling-calls, or make `.text.init.refok' >> extern >> ld: final link failed: Bad value >> make: *** [.tmp_vmlinux1] Error 1 >> >> # gcc -v >> Using built-in specs. >> Target: powerpc64-suse-linux >> Configured with: ../configure --enable-threads=posix --prefix=/usr >> --with-local-prefix=/usr/local --infodir=/usr/share/info >> --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib >> --enable-languages=c,c++,objc,fortran,obj-c++,java,ada >> --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 >> --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib >> --with-system-zlib --enable-shared --enable-__cxa_atexit >> --enable-libstdcxx-allocator=new --program-suffix=-4.1 >> --enable-version-specific-runtime-libs --without-system-libunwind >> --with-cpu=default32 --enable-secureplt --with-long-double-128 >> --host=powerpc64-suse-linux >> Thread model: posix >> gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) >> >> ld -v >> GNU ld version 2.17.50.0.5 20060927 (SUSE Linux) >> >> >> Anything I can provide to help diagnose this? >> > > Did we work out which patch is causing this? > - Hi Andrew, No, we did not work out on which patch is causing this ! I will try a bisect to find the patch causing this issue.
-- Thanks & Regards, Kamalesh Babulal, Linux Technology Center, IBM, ISTL. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
