Joern Rennecke wrote:
It appears that most of the errors are of the form:
collect-ld:
cannot find -lgfortranbegin
I've found that the problem was related to configure deciding to build
fortran and enable runtime tests for it when doing check-gcc even though
libgfortran was not present; I had
>
> Steven Bosscher wrote:
>
> >
> > So you don't report any error messages at all and leave us guessing?
> >
>
> AFAIK fortran is not supposed to be configured at all for a cross-compiler.
> Or has that changed recently? It was certainly not configured in my
> previous
> builds of gcc 4.2
Steven Bosscher wrote:
So you don't report any error messages at all and leave us guessing?
AFAIK fortran is not supposed to be configured at all for a cross-compiler.
Or has that changed recently? It was certainly not configured in my
previous
builds of gcc 4.2 snapshots.
On 11/1/06, Joern RENNECKE <[EMAIL PROTECTED]> wrote:
With literally more than ten thousand lines of error messages per
multilib for fortran, that makes the test results unreportable.
So you don't report any error messages at all and leave us guessing?
Gr.
Steven
