This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu


Angel Tsankov wrote:
OK, the build process anew:

1. I configured gcc-core 4.3.2
with --prefix="$INSTALLED_SOFTWARE"/"$program"
--with-local-prefix="$INSTALLED_SOFTWARE"/"$program"
--with-gmp="$INSTALLED_SOFTWARE"/gmp
--with-mpfr="$INSTALLED_SOFTWARE"/mpfr


I forgot to mention that the host C compiler is GCC 2.95.4.

Quite a big step in GCC versions... Maybe you should try a smaller step first like 2.95.4 -> 3.2.3 and after that the 3.2.3 -> 4.3.2

The GCC configure options include the :

------------- clip -------------------
--program-suffix=suffix
  Appends suffix to the names of programs to install in bindir (see
  above). For example, specifying --program-suffix=-3.1 would result
  in `gcc' being installed as /usr/local/bin/gcc-3.1.
------------- clip -------------------

so it is fully possible to install many GCC-versions to use
the same (native) binutils and C library without the earlier
one(s) (here 2.95.4) being overwritten!

Ok, producing gcc-4.3.x with gcc-2.95.x maybe should still work,
but I still would suggest keeping the old GCC just as producing
some "older" GCC version for producing older sources like older
GCCs - it is a continuous problem that people will (think they)
need older GCCs for producing apps for older systems (As the
matter of fact they would need complete crosstoolchains for older
systems, with the old C libraries etc.).


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]