On 8 June 2015 at 23:36, james harvey <jamespharvey20@xxxxxxxxx> wrote: > Is this: > > git clone git://gcc.gnu.org/git/gcc.git gcc.git > mkdir gcc.git.build > cd gcc.git.build > ../gcc.git/configure --disable-multilib && make -j8 && sudo make install > > The same as: (Ignoring this creates three build directories and takes > up more space.) > > git clone git://gcc.gnu.org/git/gcc.git gcc.git > mkdir gcc.git.build.oldgcc > cd gcc.git.build.oldgcc > ../gcc.git/configure --disable-multilib --disable-bootstrap && make > -j8 && sudo make install > mkdir ../gcc.git.build.currentgcc > cd ../gcc.git.build.currentgcc > ../gcc.git/configure --disable-multilib --disable-bootstrap && make > -j8 && sudo make install > mkdir ../gcc.git.build.currentgcc.redo > cd ../gcc.git.build.currentgcc.redo > ../gcc.git/configure --disable-multilib --disable-bootstrap && make > -j8 && sudo make install > cd .. > diff --brief --recursive gcc.git.build.currentgcc gcc.git.build.currentgcc.redo > > I'm running into a bug using the overlay filesystem in kernel 4 that > is being difficult to track down. The first set of instructions I > listed (making gcc using bootstrapping) fails, but the second set > (making gcc in three separate build directories) succeeds. > > Wondering if the second set gets me around the bug, or if that process > is different than the first. It's completely different. Doing exactly the same thing three times is not what bootstrapping does.
