https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58828
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Daniel Fruzynski from comment #5)
> (In reply to Eric Gallager from comment #4)
> > (In reply to Daniel Fruzynski from comment #3)
> > > OK, I found it. I used script symlink-tree (distributed with binutils) to
> > > create symlinks to binutils in gcc source dir. This script removed some
> > > gcc
> > > source files and replaced them with symlinks to corresponding files in
> > > binutils dir. I assumed that it will help me, but it created more
> > > problems.
> > >
> > > I am building gcc without binutils symlinked, and build is on stage 2 now.
> > > Look that it will complete successfully.
> > >
> > > I think that dedicated script to symlink all binutils into gcc dir would
> > > be
> > > useful. Could you create one?
> >
> > "You" as in Richard or Ian?
>
> I meant someone from gcc or binutils team who is responsible for this area.
>
> BTW, now gcc is shipped with contrib/download_prerequisites script which
> handles all this stuff, so you may close this issue if you want.
OK, cool.
