On Tuesday, 28 April 2015 at 02:18:29 UTC, Mike wrote:
On Tuesday, 28 April 2015 at 02:12:11 UTC, Jens Bauer wrote:
On Tuesday, 28 April 2015 at 00:34:42 UTC, Mike wrote:
Given the other replies in this thread, this looks promising.
However, I went to give it a test today, and found out my
host PC's distribution (Arch Linux) hasn't yet released GCC
5.1; it's still in testing.
You don't have to wait for an Arch Linux release of GCC 5.1,
because you're going to build it yourself anyway, right ?
-It can be downloaded from
ftp.gnu.org/gnu/gcc/gcc-5.1.0/gcc-5.1.0.tar.bz2
I always thought we needed to build our cross-compilers with
the same version as the host in order to have confidence in the
build. Correct me if I'm wrong.
Mike
It has always been recommended that the gcc used should be as
close as possible to the gcc being compiled. This was very
important in gcc 2.8 time. 2.7 could not compile anything after
2.8. I think they are more stable now and the previous release
may always be used to compile the last release.
It is important that we first test with the original sources.
Packages may have modified them which may cause issues. It is
also important that the system is totally clean from previous
installation. I have tried to build in a vm but it has always
failed with something like 32/64 bit issue in system headers.
I will put a sample build script in gdc list.
