public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Olaf Foellinger <Olaf.Foellinger@bln.sesa.de>
To: Volker Quetschke <quetschke@scytek.de>, cygwin@cygwin.com
Subject: Re: mutt and gpg 1.07
Date: Thu, 30 May 2002 11:14:00 -0000	[thread overview]
Message-ID: <20020530143015.GA1036@NBOF> (raw)
In-Reply-To: <3CF63620.1050400@scytek.de>

On Thu, May 30, 2002 at 04:24:32PM +0200, Volker Quetschke wrote:
> Hi!
> 
> >>Unfortunately I can't help you with your problem, but I am very curious 
> >>how you build gnupg 1.07.
> >>
> >>Which configure flags did you use?
> >
> >>From the ChangeLog
> >(http://lists.gnupg.org/pipermail/gnupg-announce/2002q2/000251.html):
> >..
> >* Some fixes to build cleanly under Cygwin32.
> >..
> >
> >I didn't use any specific flags, and beside some warnings about not
> >finding some libraries gpg builds OOTB.
> 
> I only asked because after the ./configure the make stops with:
> ----
> [snip]
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../include -I../intl    -g -O2 
> -Wall -c `test -f w32reg.c || echo './'`w32reg.c
> In file included from w32reg.c:30:
> ../include/util.h:226: warning: `stricmp' redefined
> /usr/include/string.h:80: warning: this is the location of the previous 
> definition
> rm -f libutil.a
> ar cru libutil.a g10u.o logger.o fileutil.o miscutil.o strgutil.o 
> ttyio.o argparse.o memory.o secmem.o errors.o iobuf.o dotlock.o http.o 
> simple-gettext.o w32reg.o
> libutil.a
> libutil.a: not found
> make[2]: *** [libutil.a] Error 127
> make[2]: Leaving directory `/home/q/gnupg/gnupg-1.0.7/util'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/q/gnupg/gnupg-1.0.7'
> make: *** [all] Error 2
> ----
> 
> I used cygwin 1.3.10, update a few minutes ago.
> 
> I only asked because this doesn't look like OOB. :-)

O.k., just try make a few times. This is a minor bug in the generated
makefile. If no further compilation calls appear, one can type make
install and anything works. This is not OOTB of course.


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/

  reply	other threads:[~2002-05-30 14:36 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 [this message]
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
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=20020530143015.GA1036@NBOF \
    --to=olaf.foellinger@bln.sesa.de \
    --cc=cygwin@cygwin.com \
    --cc=quetschke@scytek.de \
    /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).