On Sat, 4 Jun 2016, Ethin Probst wrote:
Yesterday I managed to successfully build GCC and all of the accompanying languages that it supports by default (Ada, C, C++, Fortran, Go, Java, Objective-C, Objective-C++, and Link-time Optimization (LTO)). I did not build JIT support because I have not herd if it is stable or not. Anyways, seeing as I didn't (and still do not) want to wait another 12 hours for that to build, I compressed it into a .tar.bz2 archive,
Did you use "make -j 8" (where 8 is roughly how many CPUs you have in your server)? 12 hours seems excessive.
copied it over to another server, decompressed it, and here's when the
Did you copy it to exactly the same path as on the original server, preserving time stamps, and do both servers have identical systems?
problems start. Keep in mind that I did ensure that all files were compressed and extracted. When I go into my build subdirectory build tree, and type "make install -s", it installs gnat, gcc (and g++), gfortran, gccgo, and gcj, but it errors out (and, subsequently, bales out) and says the following: Making install in tools make[3]: *** [install-recursive] Error 1 make[2]: *** [install-recursive] Error 1 make[1]: *** [install-target-libjava] Error 2 make: *** [install] Error 2 And then: $ gcj gcj: error: libgcj.spec: No such file or directory
A more common approach would be to run "make install DESTDIR=/some/where", tar that directory, copy this archive to other servers, and untar it in the right location. That's roughly what linux distributions do.
I'm considering the test suite, but until it installs, I'm not sure if executing the test suite would be very wise at this point. To get it to say that no input file was specified, I have to manually run the following commands: $ cd x86_64-pc-linux-gnu/libjava $ cp libgcj.spec /usr/bin
That seems like a strange location for this file.
Has the transportation of the source code caused the build tree to be messed up? I know that it works perfectly fine on my other server. Running make install without the -s command line parameter yields nothing. Have I done something wrong?
"nothing" is not very helpful... Surely it gave some error message. -- Marc Glisse
