From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79433 invoked by alias); 14 Jan 2020 10:44:34 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 79416 invoked by uid 89); 14 Jan 2020 10:44:34 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=ubizjak@gmail.com, ubizjakgmailcom, H*f:sk:wXbnv3V, H*i:sk:wXbnv3V X-HELO: mail-wm1-f68.google.com Received: from mail-wm1-f68.google.com (HELO mail-wm1-f68.google.com) (209.85.128.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 14 Jan 2020 10:44:24 +0000 Received: by mail-wm1-f68.google.com with SMTP id b19so13136415wmj.4 for ; Tue, 14 Jan 2020 02:44:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uWsFolmbRQA6DedVDNDBGX52XCB090aY4JV4Ji2oDEE=; b=DRL37PgxD2ms72+V2eibJacAcLTB3fFQ0KySRZ9hHRLqKstchwHfcG6gOviV0z7FK9 gjPBgTvm95ANRDYe02pYotanLjL7RlnGXBUQUQabdn6gkahQ3tkK4CJitZyEENtVbQvU RAxjwNqv2ujmxgkK4vgEOQ3kmg0+a0JIWcSf3Ax4WCGAN3C5m0HCwNFHaoWdhTb00Fpy hzD7meM0UoxMNA0/vyP4TJcYe0XTUu8y7uAhClMTxEMMjKRS2vNSMJ5Ab+IVAYOhuGrB am91EftsDf3aieOFsUzCDCs8Rlzfg2pnHlbZDxsKPm7Wg6sxnbBSo4MEgSIK+XVTf0rv iXYA== MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Tue, 14 Jan 2020 11:34:00 -0000 Message-ID: Subject: Re: contrib/gcc_update does not work To: Uros Bizjak Cc: GCC Development Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-01/txt/msg00235.txt.bz2 On Tue, 14 Jan 2020 at 10:38, Uros Bizjak wrote: > > On Tue, Jan 14, 2020 at 11:34 AM Jonathan Wakely wrote: > > > > On Tue, 14 Jan 2020 at 09:22, Uros Bizjak 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 :-) 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.