X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:subject:to:in-reply-to:message-id
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=qTOocmFMtu67kFFrxTpmjTUdjS9YT2rRmdFAfYBlkT7RQFQDaeN00
	WENGpNBIG0zjiffwN+sBkvdUZZxQOaylISusVFBBCbTL/ZjiTUIczlVM2Ww3yzfL
	NIiPTwwD/HXUrTpMiuHPxfBgz5eHjLtBd3VsMyDyrbtXsHahr/IwDw=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:subject:to:in-reply-to:message-id
	:mime-version:content-type:content-transfer-encoding; s=default;
	bh=YrlKziEaQeRUrSJBwrNLo/982As=; b=HC/KWnXpKZJIYMcOhzQIcfDYFhWN
	Q0GYPAiJCmuBAZ3xaVjzmqIUwDe6UM5oVKpxpr4qsNE/tvjsIMIy4J5ZtD/TtFq5
	qrKy6hWsyMvLFR4oHsNeQEsph5Iy+N1pzxkvUQNfJVc4s505lAe+L2GkvEXetNYp
	mqpwusCV2orcoN4=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=H*RU:209.85.160.194, HX-Spam-Relays-External:209.85.160.194
X-HELO:	mail-qt1-f194.google.com
Date:	Mon, 13 May 2019 15:21:12 -0400
From:	Jack <ostroffjh AT users DOT sourceforge DOT net>
Subject:	Re: Building Bedrockdb in cygwin
To:	cygwin AT cygwin DOT com
In-Reply-To:	<DB7PR01MB5386FAFF2B644783A79628BDDE0F0@DB7PR01MB5386.eurprd01.prod.exchangel abs.com> (from jicman@outlook.com on Mon May 13 15:01:28 2019)
Message-Id:	<OCHW6GTN.IBP5MV5P.5IS2I3RS@I6DS4IYZ.HY33WISX.DCFLZWPD>
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id x4DJLPvt013453

On 2019.05.13 15:01, Jose Isaias Cabrera wrote:
> So, it looks like the root (c49b808ae490f03d665df5faae457f613aa31aaf)  
> does not exists... Thanks for the quick reply, though.
This issue is that at that point, the higher level make assumes that  
mbedtls is a git repository.

> cd mbedtls && git checkout -q c49b808ae490f03d665df5faae457f613aa31aaf
> fatal: reference is not a tree:  
> c49b808ae490f03d665df5faae457f613aa31aaf
I don't fully understand the git submodules, but something in the main  
git repository should have the info about where the git submodule's  
upstream repository is.  I'll guess here that you started by unpacking  
a tarball, and not cloning the Bedrock git repository, and that they  
failed to include the main .git folder in the tarball.  You'll probably  
either need to start by a git clone, or have them tell you how to  
manually specify the missing submodule information.

However, in doing a bit of searching, I just found a stackoverflow  
answer which includes "This is the most common problem with submodules.  
The commit that you are on in the outer repository has a reference to a  
commit in the submodule that someone did not push up yet. It's a  
dependency problem. Always push from the inside-out. This is most  
likely not something you did wrong, but someone else that's working in  
the repository. "    This implies that mbedtls does have a .git folder,  
but that particular commit is not yet available.  Try doing a "git  
pull" when in that subdirectory.  Otherwise, wait for a response from  
the Bedrock team.

Jack
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -