Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
To:	cygwin AT cygwin DOT com
X-Injected-Via-Gmane:	http://gmane.org/
Path:	not-for-mail
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
Newsgroups:	gmane.os.cygwin
Subject:	Re: PGP signatures for packages?
Date:	Sat, 18 May 2002 01:07:59 -0400
Lines:	46
Message-ID:	<3CE5E1AF.8080709@ece.gatech.edu>
References:	<FC169E059D1A0442A04C40F86D9BA7600C6104 AT itdomain003 DOT itdomain DOT net DOT au> <001f01c1fe1c$ecd4e840$c23fa8c0 AT transarc DOT ibm DOT com>
NNTP-Posting-Host:	c-24-98-131-105.atl.client2.attbi.com
Mime-Version:	1.0
X-Trace:	main.gmane.org 1021698274 9030 24.98.131.105 (18 May 2002 05:04:34 GMT)
X-Complaints-To:	usenet AT main DOT gmane DOT org
NNTP-Posting-Date:	Sat, 18 May 2002 05:04:34 +0000 (UTC)
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language:	en-us

Michael Young wrote:

>>And adding GPG as a package should be easy. There is already vounteer
>>binary downloads 'out there'. You just need to merge tehir build recipe
>>and patchs and the volunteer maintainer instructions.
>>
> 
> My understanding is that the official Windows binaries for GnuPG are
> built on Linux using a cross-compiler.  I don't suppose that's a
> legitimate approach for an official Cygwin package, though, is it?


No.  "official windows binaries" typically use the msvcrt.dll runtime, 
not cygwin1.dll.  Which means they don't understand cygwin's filename 
structure or mount points, making them awkward to use within the cygwin 
environment.

We need a cygwin build -- perhaps built using a cygwin-targetted cross 
compiler on linux-host, but definitely not using a 
native-mswindows(mingw) targetted cross compiler on any host platform.


> I'll look at what it will take to do a native configure/compile.


Errmmmm...in this context, 'native' is usually taken to mean "native 
microsoft" -- e.g. msvcrt.dll-runtime-based -- not cygwin-based.

---------------
Now that I've thoroughly confused everyone, let's clear up the mess:

    host        target         typical name
1  cygwin      cygwin         "self-hosted cygwin build"
2  linux       cygwin         "linux hosted cygwin target cross compile"
3  linux       mingw? native? "linux hosted native windows target"
                               "linux host, mingw target cross compile"
4  mingw/native?  mingw/native?  "self hosted mingw (or "native") build"

1) is good.  2) is good.  3) is bad.  4) is bad.

As Robert said, there are **cygwin** ports of GPG 'out there' -- search 
the mailing list archives for postings (I recall someone mentioning it 
along with mutt or pine in a recent email...)

--Chuck




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -