On 2017-10-05 06:57 AM, nick wrote: > > > On 2017-10-04 07:27 PM, nick wrote: >> >> >> On 2017-10-04 02:25 PM, Manuel López-Ibáñez wrote: >>> On 04/10/17 12:31, nick wrote: >>>> Care to explain how that's an issue when not installing gcc and >>>> just running the test suite? Also care to explain how ccache >>>> fails everything I run a change to my build config? >>> >>> For what is worth, there are thousands of things that can fail when building GCC and it is very easy to make a mess out of it. >>> >>> My advice is to follow the docs to the letter and script everything that you do so you can easily start from zero and do the steps again. >>> >>> Start here: https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps >>> Check also here: https://gcc.gnu.org/wiki/FAQ >>> >>> My personal build+test script is here: https://gcc.gnu.org/wiki/ManuelL%C3%B3pezIb%C3%A1%C3%B1ez?action=AttachFile&do=view&target=gccfarming >>> >>> It may be a bit outdated and it is designed for the GCC Compile Farm, but it may give you ideas for creating your own. If you are testing a fix, the most robust approach (and the one followed by my script) is to have a pristine copy of the source tree and a pristine build and, separately, a patched version of the source tree and a patched build. >>> >>> I hope this helps, >>> >>> Manuel. >> >> Manuel, >> >> Thanks for the help. I did go through those links and found nothing wrong with how I am building gcc which is from inside odbjir below >> the gcc source: >> ../configure --prefix=$HOME/GCC-7.0.1 --enable-languages=c,c++,fortran,go >> make -j8 >> and then the tests: >> make -k check >> It fails on the libgomp and outputs to the libgomp.log file this which is weird: >> Running target unix >> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. >> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. >> Using ../../../../libgomp/testsuite/config/default.exp as tool-and-target-specific interface file. >> Running ../../../../libgomp/testsuite/libgomp.c/c.exp ... >> Executing on host: /home/nick/gcc/obdjir/gcc/xgcc -B/home/nick/gcc/obdjir/gcc/ -B/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/./libgomp/ -B/home/nick/gcc/obdjir/x86_64-pc-lin >> ux-gnu/./libgomp/.libs -I/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/./libgomp -I../../../../libgomp/testsuite/../../include -I../../../../libgomp/testsuite/.. -c -o ia325310 >> .o ia325310.c (timeout = 300) >> spawn -ignore SIGHUP /home/nick/gcc/obdjir/gcc/xgcc -B/home/nick/gcc/obdjir/gcc/ -B/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/./libgomp/ -B/home/nick/gcc/obdjir/x86_64-pc-lin >> ux-gnu/./libgomp/.libs -I/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/./libgomp -I../../../../libgomp/testsuite/../../include -I../../../../libgomp/testsuite/.. -c -o ia325310. >> o ia325310.c^M ^[[01m^[[Kia325310.c:2:6:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[Ksize of array '^[[01m^[[Kdummy^[[m^[[K' is negative^M >> int ^[[01;31m^[[Kdummy^[[m^[[K[sizeof (int) == 4^M >> ^[[01;31m^[[K^~~~~^[[m^[[K^M >> ^[[01m^[[Kia325310.c:4:41:^[[m^[[K ^[[01;31m^[[Kerror: ^[[m^[[K'^[[01m^[[K__i386__^[[m^[[K' undeclared here (not in a function); did you mean '^[[01m^[[K__k8__^[[m^[[K'?^M >> && sizeof (long) == 4 ? 1 : -1] = { ^[[01;31m^[[K__i386__^[[m^[[K };^M >> ^[[01;31m^[[K^~~~~~~~^[[m^[[K^M >> ^[[32m^[[K__k8__^[[m^[[K^M >> compiler exited with status 1 >> >> The compiler is exited with a status of 1 which I assume is a failure and abort. Does anyone have any ideas why this would be >> occurring? >> >> I will try the tests again after building with the --prefix but I really don't see how that would help. Only reason is Jonathan >> stated it may help. >> >> Thanks, >> Nick >> > > It fails even after doing it a odbjir directory outside of gcc source directory with this configure: > ../gcc/configure --enable-languages=c,c++,fortran,go > > I really have no idea how the tests are continuing to fail in the exact same way. The compiler builds > fine but fails the tests for some reason. Does anyone have an idea? I am missing tclx does the tester > require that in the ubuntu repos as literally that seems to be the only thing I can think of. This > is no mentioned in the docs through. > > Nick > Seems to work now. Building in a separate directory outside of gcc seems to have fixed it. Will just run the tests again before submitting my patch. Nick
