X-Recipient: archive-cygwin@delorie.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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=bjYeyEw6bDU1skYws6lSbQONLZotYrRO9t7pqjkIeZVlSaBOX4d9F
	xJfEETYA+dq2Kad6l5Fmfotcytql224MQtaGQA+wWja1/BQrZYUYtSpG4t+sh+SJ
	VFEWJI0IAoF2kNJHyEMuXtRurmXURSlBsHwV2VKCom2M9PVYvrwTC0=
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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=fyXuh/WTsdYLWFdTM1C8RrwDCes=; b=WJ42EelByg/1ZHWKn3psxN7pr44l
	0/OUfbduOhh1Z9QIsy56rmuV+shvACMwdPFSXaIpGZwqpDaURYX4e/yQqSsy/skk
	68YsIQUiDRCp1TMs1uMuYxqyMlGOXPQADYkhzvAGWA3U3f6he+0/TS11imuKJFel
	uK1OeB2BChlOW40=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19cp1on+O+SJYpkoBsR4RpR
Date: Wed, 18 Jun 2014 19:19:01 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: No glibc in cygwin
Message-ID: <20140618231901.GB5547@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <C60D6B2FF205DA478ED856CA0A1D481017CE32EA@EM-EXMRP103.us.saic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C60D6B2FF205DA478ED856CA0A1D481017CE32EA@EM-EXMRP103.us.saic.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Wed, Jun 18, 2014 at 11:03:52PM +0000, Lucero, Aldo wrote:
>I am trying to port some Fortran/C code from Linux to Windows using
>Cygwin (CYGWIN_NT-6.1 elp-w7wks-40 1.7.30(0.272/5/3) 2014-05-23 10:36
>i686 Cygwin) The main program spawns several processes using fork() and
>one of those processes will create another process using clone().  I
>have read under the FAQ that glibc is not part of Cygwin and that using
>fork in Cygwin is not stable.

fork() in Cygwin has to be pretty stable since it is fundamental to a
UNIX/Linux system.  Cygwin doesn't implement "clone()" however.  It is
theoretically possible to do so but it wouldn't be trivial.

>I have been able to compile my code in Cygwin, but when trying to link
>my libraries (static), it cannot find clone function (under C code).
>Do you guys have any recommendations as far as whether to continue
>trying to get my code to work under Cygwin or should I try to find some
>other Windows compiler(s)?  I apologize if I am not being clear, but I
>am wondering if somebody else has had this issue and if they were able
>to resolve it.

This isn't a compiler issue.  You'd have to find something similar to
Cygwin which implemented clone().  Or add the functionality yourself.

cgf

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

