On Mon, Dec 29, 2014 at 11:42 AM, Cyd Haselton <chaselton@xxxxxxxxx> wrote: > On Sat, Dec 27, 2014 at 11:40 AM, Andrew Haley <aph@xxxxxxxxxx> wrote: >> On 26/12/14 23:54, Cyd Haselton wrote: >>> Just to make sure I'm on the same page: >>> Rebuild 4.8.3 and/or upgrade to 4.8.4 and keep build directory >>> Compare 4.8.4 build dir (or build dir of component that failed) to >>> corresponding 4.9.2 location. >>> >>> That about right? >> >> No. Keep a log of the entire build: >> >> make | tee make.log >> >> and look at how the dynamic libgcc is linked. Look at the makefile >> to see where that lib comes from. Look at the 4.9 makefile to see >> where it is different. >> >> Andrew. >> > > I did as suggested and combed through the libgcc build portion of both > logs. Configure was exactly the same for both. > > I then went through both build logs, line by line. Excluding the > parts where one build made build subdirs as needed, there were a few > differences that appeared to possibly be relevant > > For the libiberty configure, 4.9 ran the following checks (4.8 did not): > checking whether to install libiberty headers and static library... no > configure: target_header_dir = > > For the lto-plugin configure, 4.9 ran the following check (4.8 did not): > checking for -static-libgcc... yes > > For the lto-plugin build, 4.9 used the following option for the > libtool link gcc command (4.8. did not): > -Wc,-static-libgcc > > Full libtool link gcc command for the lto-plugin build for both 4.9 and 4.8: > 4.9 > /android_root/system/bin/sh ./libtool --tag=CC --tag=disable-static > --mode=link gcc --sysroot=/usr/gcc-4.9.2/sysroot -Wall -Wall -O > -mandroid -mbionic -Wc,-static-libgcc -module -bindir > /usr/gcc-4.9.2/libexec/gcc/arm-linux-androideabi/4.9.2 > -static-libstdc++ -static-libgcc > -Wl,--dynamic-linker=/system/bin/linker -lc -ldl -lgcc -lm -o > liblto_plugin.la -rpath > /usr/gcc-4.9.2/libexec/gcc/arm-linux-androideabi/4.9.2 lto-plugin.lo > -Wc,../libiberty/pic/libiberty.a > > 4.8 > /android_root/system/bin/sh ./libtool --tag=CC --tag=disable-static > --mode=link gcc --sysroot=/usr/gcc-4.8.4/sysroot -Wall -Wall -O > -mandroid -mbionic -module -bindir > /usr/gcc-4.8.4/libexec/gcc/arm-linux-androideabi/4.8.4 > -static-libstdc++ -static-libgcc > -Wl,--dynamic-linker=/system/bin/linker -lc -ldl -lgcc -lm -o > liblto_plugin.la -rpath > /usr/gcc-4.8.4/libexec/gcc/arm-linux-androideabi/4.8.4 lto-plugin.lo > -Wc,../libiberty/pic/libiberty.a > > There were others, but I'll hold off including them unless the above > are not relevant to my issue. Polite bump just in case reply was missed. Since the above post I've tried replacing the -static-libgcc reference in the top level Makefile with -shared-libgcc (which results in a slew of errors), specifying the stage1, boot and poststage1 libs in the Makefile with the same libs specified in configure (which doesn't work) and adding the same options from the LDFLAGS I specified in the top-level configure to the post stage1 LDFLAGS and stage1 LDFLAGS. No success so far. I still have the build logs from 4.8 and 4.9...I can upload them if they would be of use in diagnosing this issue.
