Thanks! Downloaded along with mpfr, ppl-0.11.2 (configure said that my
existing version is "buggy" :-) ) and cloog-ppl-0.15.9.
If I dump mpfr, ppl and cloog-ppl in the main gcc source directory
(and name those directories like that - "mpfr", "ppl" and "cloog-ppl")
would that be enough for the GCC build or do I have to compile/install
them separately?
As far as I know that is fine. I haven't done much with PPL myself.
It says on the gcc pre-requisite pages that these packages are good for
doing the optimisations, so I thought there is no harm to include these
in the build as well. I'll try them when I do my 2nd pass.
Currently I took the plunge and dumped the whole binutils directory in
the main gcc source...will see how it goes after I selected
--host=x86_64 and --target=powerpc, fingers crossed!
If I copy binutils sources to the main gcc source directory what would
be the sign that they are incompatible - the same error as I was
getting before (line 83 etc)?
No, the errors are much more subtle. I really can't encourage this
unless you are prepared to investigate and solve problems yourself.
I hope there is no conflict, but if there is and I get an error I will
build binutils separately.
What do you see in the config.log file?
The same one I was getting with the ppc target - line 83 etc etc.
I'm sorry, I don't recall what that was. If it's a missing 'as' file
then the simple answer is still going to be to install the binutils. At
one time gcc would fall back to running 'as' even for a cross-compiler,
but perhaps that is no longer the case.
I am a bloody moron! I forgot to rename the mpfr directory when dumping
the source and this was the reason for the build to stop midway through
- it is OK now, I just compiled GCC with the multilib option on without
any glitches. We're getting there!!!
MZ
