From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool
Date: Wed, 16 Nov 2011 20:01:00 -0000 [thread overview]
Message-ID: <4EC41689.8090601@gmail.com> (raw)
In-Reply-To: <32857072.post@talk.nabble.com>
On 11/16/2011 8:34 PM, viper_88 wrote:
>
>
> $
>
> I'm not sure, but I guess this ends my use of Cygwin for the purpose of
> compiling THC-Hydra with its full capabilities :/ If there aren't any
> options to make it work indeed, I think that the only way to accomplish my
> goal (apart from a full-fetched installation of Linux on my hard drive) is
> to install it on a virtual machine.
>
> Of course, if anyone knows of a way to make GLIBC work with Cygwin, I will
> be more than glad to learn it
why do you need glibc ?
cygwin has its own libc (newlib) and hydra-7.1-src
build easily on cygwin
$ ./configure
$ make
------------------------
....
If men could get pregnant, abortion would be a sacrament
cd hydra-gtk && sh ./make_xhydra.sh
Trying to compile xhydra now (hydra gtk gui) - dont worry if this fails,
this is really optional ...
`src/xhydra' -> `../xhydra.exe'
The GTK GUI is ready, type "./xhydra" to start
Now type make install
----------------------------
$ find . -name "*.exe"
./hydra-gtk/src/xhydra.exe
./hydra.exe
./pw-inspector.exe
./xhydra.exe
Regards
Marco
--
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
next prev parent reply other threads:[~2011-11-16 20:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 19:28 viper_88
2011-11-15 20:46 ` Larry Hall (Cygwin)
2011-11-16 19:34 ` viper_88
2011-11-16 20:01 ` marco atzeri [this message]
2011-11-17 12:15 ` viper_88
2011-11-17 13:00 ` marco atzeri
2011-11-17 20:34 ` Dave Korn
2011-11-17 20:38 ` Dave Korn
2011-11-17 18:50 ` Andrey Repin
2011-11-16 20:05 ` Jesse Ziser
2011-11-16 20:41 ` Tim Prince
2011-11-16 20:12 ` Christopher Faylor
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=4EC41689.8090601@gmail.com \
--to=marco.atzeri@gmail.com \
--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).