contrib/gcc_update does not work

Andrew Pinski pinskia@gmail.com
Tue Jan 14 12:59:00 GMT 2020


On Tue, Jan 14, 2020 at 4:10 AM Richard Biener
<richard.guenther@gmail.com> wrote:
>
> On Tue, Jan 14, 2020 at 11:44 AM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> >
> > On Tue, 14 Jan 2020 at 10:38, Uros Bizjak <ubizjak@gmail.com> wrote:
> > >
> > > On Tue, Jan 14, 2020 at 11:34 AM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> > > >
> > > > On Tue, 14 Jan 2020 at 09:22, Uros Bizjak <ubizjak@gmail.com> wrote:
> > > > >
> > > > > gcc_update, when called from newly initialized and pulled tree does not work:
> > > >
> > > > Initialized how?
> > >
> > >  1035  mkdir gcc
> > >  1036  cd gcc
> > >  1037  git init
> > >  1038  git pull https://gcc.gnu.org/git/gcc.git
> >
> > Don't do that :-)
>
> I think it's what the wiki still suggests...

Yes the wiki does suggest that but the wiki was about using git mirror.
"With a normal git repository 'git clone' grabs all branches, but
because of the SVN mirror we need to do something more elaborate" :).
This is no longer true and even wrong as the branches are in a
different location really.

Thanks,
Andrew

>
> > You've created an new, empty repository and then filled it with the
> > content from gcc.gnu.org/git/gcc but that's not the same as making a
> > clone of that repo. You could make it the same, but you'd have to do a
> > lot more steps manually. Just use 'git clone'.
> >
> > > > If you do a 'git clone' then it correctly checks out master and sets
> > > > it to track origin/master.
> > >
> > > I see, I'll try this now.



More information about the Gcc mailing list