public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Olaf Foellinger <Olaf.Foellinger@bln.sesa.de>
To: cygwin@cygwin.com
Subject: Re: mutt and gpg 1.07
Date: Mon, 03 Jun 2002 01:47:00 -0000	[thread overview]
Message-ID: <20020603084308.GB216@NBOF> (raw)
In-Reply-To: <3CF7D1B5.2020901@scytek.de>

Hi Volker,

On Fri, May 31, 2002 at 09:40:37PM +0200, Volker Quetschke wrote:
> Hi!
> 
> >>>now where gnupg 1.07 is out and builds cleanly under cygwin I'll repeat
> >>>my question whether it is possible to get mutt working with gpg. All my
> >>>tries failed so far with the error that gpg cannot find the file mutt
> >>>reports to him. I'm not a developer so I cannot resolve the problem
> >>>myself but this is the biggest problem for me.
> >>>
> >>here's a more detailed error description. I'm using the cygwin mutt
> >>together with a gpg 1.07 which builds cleanly under cygwin.
> 
> Now it builds OOB, at least when you use the attached patch.
> 
> >>When I try to encrypt a message and press y to send mutt presents me a
> >>list of possible keys.  I choose one and I get the error
> >>
> >>gpg: /tmp/mutt-NBOF-1728-4: encryption failed: file open error
> >>Bitte drücken Sie eine Taste...
> 
> Yes, the gnupg 1.0.7 version uses the "windows file system", and I think 
> you don't have a c:\tmp\ directory. Even if you have, this is not the 
> same directory ( \tmp ) for mutt. (mutt is a real cygwin application)
> 
> >>and indeed there isn't such a file 
> >>
> >>$ ls /tmp
> >>mutt-NBOF-1620-143  mutt-NBOF-1728-1  mutt-NBOF-1728-2
> >>
> >>It seems to me that mutt doesn't create the right file or does report
> >>the wrong filename to gpg. 
> 
> Mutt does, but gpg looks elseware.
> 
> As I had a look into this problem I realized that it was easy to fix 
> configure.ac to make gnupg compile OOB. Then I removed the special cases 
> with __CYGWIN__ for the file handling and it still build without a problem.
> 
> This patch might fix your problem, feel free to test the patched gpg.
> 
> I only looked at the parts of the source with special __CYGWIN__ cases 
> therefore if might be that I missed someting. (Please report if it works 

I've applied your patch and got the folowing problems while compiling:

make[2]: Wechsel in das Verzeichnis Verzeichnis /tmp/gnupg-1.0.7/g10
source='passphrase.c' object='passphrase.o' libtool=no \
depfile='.deps/passphrase.Po' tmpdepfile='.deps/passphrase.TPo' \
depmode=gcc /bin/sh ../scripts/depcomp \
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../include -I../intl    -g -O2
-Wall -c
`test -f passphrase.c || echo './'`passphrase.c
In file included from passphrase.c:40:
./include/util.h:226: warning: `stricmp' redefined
/usr/include/string.h:80: warning: this is the location of the previous definition
passphrase.c: In function `agent_open':
passphrase.c:479: storage size of `client_addr' isn't known
passphrase.c:518: warning: implicit declaration of function `socket'
passphrase.c:518: `AF_UNIX' undeclared (first use in this function)
passphrase.c:518: (Each undeclared identifier is reported only once
passphrase.c:518: for each function it appears in.)
passphrase.c:518: `SOCK_STREAM' undeclared (first use in this function)
passphrase.c:528: dereferencing pointer to incomplete type
passphrase.c:531: warning: implicit declaration of function `connect'
passphrase.c:479: warning: unused variable `client_addr'
passphrase.c:480: warning: `len' might be used uninitialized in this function
make[2]: *** [passphrase.o] Fehler 1
make[2]: Verlassen des Verzeichnisses Verzeichnis /tmp/gnupg-1.0.7/g10
make[1]: *** [all-recursive] Fehler 1
make[1]: Verlassen des Verzeichnisses Verzeichnis /tmp/gnupg-1.0.7
make: *** [all] Fehler 2

My developing experience is to small to fix this problem. Do you have
any hints ?



Gruss Olaf Föllinger

--
Besuchen Sie uns auf der Internet World vom 4. - 6. Juni 2002 in Berlin - Halle 4.2, Stand D15

Olaf Föllinger
Leiter Fachbereich IT
S.E.S.A. Software und Systeme AG

Alt-Moabit 91a
D-10559 Berlin
Germany
Tel:   +49 30 390722 -291
Fax:   +49 30 390722 -222
Mobil: +49 173 6227080
http://www.sesa.de
mailto: Olaf.Foellinger@sesa.de

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

  parent reply	other threads:[~2002-06-03  8:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03  6:35 Olaf Foellinger
2002-05-17  4:15 ` Olaf Foellinger
2002-05-28  8:12   ` Olaf Foellinger
2002-05-28 15:16     ` Volker Quetschke
2002-05-29 10:28       ` Olaf Foellinger
2002-05-30 10:03         ` Volker Quetschke
2002-05-30 11:14           ` Olaf Foellinger
2002-05-31 19:56     ` Volker Quetschke
     [not found]       ` <20020531203828.GA22766@redhat.com>
2002-06-01 17:32         ` Volker Quetschke
2002-06-02  5:54           ` Nicholas Wourms
2002-06-03  1:47       ` Olaf Foellinger [this message]
2002-06-03 12:10         ` Volker Quetschke
2002-06-03 13:00           ` Nicholas Wourms

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020603084308.GB216@NBOF \
    --to=olaf.foellinger@bln.sesa.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).