DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=wLB8qfjPdS4MxJiU
	WPpMPABbtfubuzaVJzFtmp0YkB2T9VTi6kcek+HrvNJ3g6T+uwqrmXzTQ1IqNxj0
	u92ZNwIC+75ahEfYxWGCtDev3+LlLf6epYwczWIUU+4iz61nKfrldNnQU9zZyl8K
	DNluKaAgJvzIdeJA7Sp/r5wNJF4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: needed : building instruction of newlib under window 10 cygwin32 or cygwin64ls
To: cygwin@cygwin.com
References: <B242BB0F12C2544BB4FEB0B1B67AAF8E15BCD4CB@NDMSMBX402.ndc.nasa.gov>
From: Mark Geisert <mark@maxrnd.com>
Message-ID: <dfa28d6d-affe-8424-e3db-795f72c5b5a4@maxrnd.com>
Date: Fri, 27 Jul 2018 16:10:46 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46
MIME-Version: 1.0
In-Reply-To: <B242BB0F12C2544BB4FEB0B1B67AAF8E15BCD4CB@NDMSMBX402.ndc.nasa.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Shen, Chang (MSFC-EV43) wrote:
> Hi Mark:
>
> Great!
>
> It works now.  Only after I did below to filter out anything from windows path.  I guess something was used other than cygwin's tools.
>
> export path=/usr/local/bin:/bin:/usr/bin:

That would certainly explain some of your difficulties :).  I'm not sure how you 
set up your Cygwin environment.  But usually, the setup*.exe program one gets 
from the project's home page https://cygwin.com takes care of everything.

> In your replay, you did not run make in cygwin.  Instead going to newlib to run make.  Is this because we already has cygwin?
> I went up one level to in src folder and run make.  It builds.  But this step is not needed, right?

It depends on what you want to build :-).  You originally said you wanted to 
build newlib, so I provided steps for that.  If you build in the topmost build 
directory, then all of the Cygwin DLL and Cygwin support programs are built. 
(Not Cygwin-hosted packages.  Those are built separately.)  All Cygwin programs 
and the Cygwin DLL itself use newlib as their C runtime library, because they 
don't use glibc like Linux programs do.

So, for example, if you were developing or debugging something in the Cygwin 
DLL, you'd build at the top level.  But if you only need newlib, you can build 
just that.  But that only works if you configure at top build level then 
configure at newlib level.

HTH,

..mark


--
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