public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Cyd Haselton <chaselton@gmail.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Stage3 Bootstrap Fails...
Date: Mon, 13 Oct 2014 09:36:00 -0000	[thread overview]
Message-ID: <CAHu5PrYm_mru9CqeM7=mJCGy-NNUDZNuZyGsH68ZMPSd6-592A@mail.gmail.com> (raw)

Hello,

I'm currently in the process of bootstrapping GCC 4.8.0 from version
4.7.0 on an Android tablet in a terminal app that simulates a proper
Linux file system.

Everything goes well until stage3. The make seems to be trying to
configure and build any library that was not specifically disabled in
the initial top-level build.  This causes errors that did not occur
earlier in the process.

The first time this happened, I fixed (I think) the problem by
rerunning the top level config with the added ---disable-xxxx
option...where xxxx is the library that stage3 suddenly tries to
build, and running make restrap.  I've run into the same problem
again, and since restrapping takes a *long* time on my device, and
because i have limited commandline space, I'd like to know if there's
an easier way to get stage3 to only build stuff that's already been
built in previous stages.

Let me know what info I should post about this problem that would
help.  For now, here is the last top-level configure:

../gcc-4.8.0/configure --prefix=/usr/gcc-4.8
--build=arm-linux-androideabi --host=arm-linux-androideabi
--target=arm-linux-androideabi --disable-ld
--with-as=/usr/gcc-4.8/bin/as --with-ld=/usr/gcc-4.8/bin/ld
--enable-shared --enable-languages=c,c++ -disable-gold
--disable-fortran --disable-libssp --disable-libquadmath
--disable-libquadmath-support --disable-libada --disable-nls
--disable-werror --disable-multilib --disable-libgomp --disable-cloog
--disable-sjlj-exceptions --disable-libitm --disable-ppl
--with-build-time-tools=/usr/gcc-4.8/bin
--with-sysroot=/usr/gcc-4.8/sysroot
--with-build-sysroot=/usr/gcc-4.8/sysroot "CFLAGS=-Wall -O2 -mandroid
-mbionic" "LDFLAGS=-Wl,--dynamic-linker=/system/bin/linker -lc -ldl
-lgcc -lm" "LIBCFLAGS=-O2 -g -mandroid -mbionic" "LIBCPPFLAGS=-O2 -g
-mandroid -mbionic" "CXXFLAGS=-frtti" "LIBCXXFLAGS=-O2 -g -mandroid
-mbionic -fno-implicit-templates" "LIBS=-lc -ldl -lgcc -lm -lsupc++
-lgnustl_shared" SHELL=/system/bin/sh

                 reply	other threads:[~2014-10-13  9:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHu5PrYm_mru9CqeM7=mJCGy-NNUDZNuZyGsH68ZMPSd6-592A@mail.gmail.com' \
    --to=chaselton@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).