Hi Michael,
Thanks for hanging in there with me :)
I know now why those three libs didn't build -- their configure-target-*
target failed, because when it tried to compile a little test program, the
loader couldn't find libmpc. I did include the --with-mpc flag in the
GCCFLAGS in your Makefile, but apparently that doesn't carry down through to
here -- so I just moved it (and gmp and mpfr) all to /usr/lib, and now the
configure-target-libstdc++-v3 no longer gets that error. Unfortunately, it
failed to find arm-linux-gnueabi-ar when it was trying to archive libgcc.a.
It does exist (in build/sysroot/.../cross-gcc-linaro/bin, but I'll have to
dig around a bit more to see how to get it to find it there (or maybe I'll
just throw them all into /usr/bin :)
Anyway, I think I'm getting close...
Diane
On Wed, Mar 30, 2011 at 5:36 PM, Michael Hope <michael.h...@linaro.org>wrote:
> Hi Diane. Please send through your configure arguments and a log of
> the output of configure. I suspect that these libraries are somehow
> half disabled leading to a later build error.
>
> -- Michael
>
> On Wed, Mar 30, 2011 at 3:20 PM, Diane Holt <holt.di...@gmail.com> wrote:
> > On Tue, Mar 29, 2011 at 6:18 PM, Michael Hope <michael.h...@linaro.org>
> > wrote:
> >>
> >> >> The build got pretty far, but eventually failed with:
> >> >>
> >> >> make[4]: Entering directory
> >> >> `/home/ubuntu/work/build/gcc/libiberty/testsuite'
> >> >> make[4]: Nothing to be done for `install'.
> >> >> make[4]: Leaving directory
> >> >> `/home/ubuntu/work/build/gcc/libiberty/testsuite'
> >> >> make[3]: Leaving directory `/home/ubuntu/work/build/gcc/libiberty'
> >> >> /bin/sh: line 3: cd: arm-linux-gnueabi/libstdc++-v3: No such file or
> >> >> directory
> >> >> make[2]: *** [install-target-libstdc++-v3] Error 1
> >> >> make[2]: Leaving directory `/home/ubuntu/work/build/gcc'
> >> >> make[1]: *** [install] Error 2
> >> >> make[1]: Leaving directory `/home/ubuntu/work/build/gcc'
> >> >> make: *** [stamp/gcc-install] Error 2
> >> >>
> >> >> Any idea what I need to do about that? (I tried adding
> >> >> --enable-languages=c,c++ but that didn't help.)
> >> >
> >> >Not sure there. Could you capture the output from configure and send
> >> >it through?
> >>
> >
> > Actually all the install-target-* targets fail (of the three it tries to
> > do), and in the same way -- ie., on that relative-path cd. If I comment
> out
> > the actions for install-target-libstdc++-v3, install-target-libgcc, and
> > install-target-libiberty, then the build finishes, creating the tar file.
> >
> > This is what the target for libstdc++-v3 looks like (they're all pretty
> much
> > the same, just with a different subdir in the cd and a different exports
> > var):
> >
> > install-target-libstdc++-v3: installdirs
> > @: $(MAKE); $(unstage)
> > @r=`${PWD_COMMAND}`; export r; \
> > s=`cd $(srcdir); ${PWD_COMMAND}`; export s; \
> > $(RAW_CXX_TARGET_EXPORTS) \
> > (cd $(TARGET_SUBDIR)/libstdc++-v3 && \
> > $(MAKE) $(TARGET_FLAGS_TO_PASS) install)
> >
> > I'm not sure where that cd is supposed to be relative to, but nowhere do
> I
> > have a libstdc++* or libgcc* shared lib (or static), so it looks to me
> like
> > they're not getting built -- nothing fails, so I assume they're not even
> > trying to be built. I don't know why, though. So even though I got
> through
> > to the tarfile creation, it isn't actually complete -- but I suppose as a
> > workaround for now, I could try snagging those libs from release you guys
> > built and see if that works.
> >
> > Diane
> >
> >
>
_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
