Problems with updating nearly any package meant for Cygwin or using packages such as libtool

Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[viper_88]

First of all, I would like to warn some that this message may be a bit
lengthy.

I installed Cygwin 1.7.9-1 mainly for the purpose of compiling and trying
out THC-Hydra. I've managed to install some necessary dependencies, but
other are so troublesome I just can't deal with them.

The avalanche of my problems has started when I wanted to install
compat-libstdc++ 33-3.2.3. The installation failed due to the following
dependencies errors:

error: Failed dependencies:
        /sbin/ldconfig is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.0) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.1) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.1.3) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.2) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.3) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libgcc_s.so.1 is needed by compat-libstdc++-33-3.2.3-55.fc5
        libgcc_s.so.1(GCC_3.0) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libgcc_s.so.1(GCC_3.3) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libgcc_s.so.1(GLIBC_2.0) is needed by
compat-libstdc++-33-3.2.3-55.fc5
        libm.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5

Being presented this message, I thought a good idea would be to first update
GCC to its newest version, since libstdc++ required the same files but from
different versions of GCC. I found GCC version 4.6.2 and downloaded it but,
unfortunately, in order to install it, I also needed a newer version of GNU
GMP. The newest yet unofficial version I found was GMP 5.0.2. I thought that
installing it would go smoothly, but so I was wrong... The very
configuration of GMP 5.0.2 seemed to be working fine. However, when I
performed "make" ("make -j 2" in particular, so that the process is faster),
I received some warning errors. The errors themselves are as follows:

$ make -j 2 > GMP_Make_Output.txt
obprintf.c:66:0: warning: ISO C forbids an empty translation unit
obvprintf.c:46:0: warning: ISO C forbids an empty translation unit
obprntffuns.c:66:0: warning: ISO C forbids an empty translation unit
repl-vsnprintf.c:389:0: warning: ISO C forbids an empty translation unit
libtool: link: warning: undefined symbols not allowed in pentium4-pc-cygwin
shar
ed libraries
libtool: link: warning: undefined symbols not allowed in pentium4-pc-cygwin
shared libraries.

I tried configuring GMP 3 times to make sure if there are any variants of
options which could solve this problem. I tried to configure it:

1. Without any flags for "./configure".

2. With "./configure --disable-shared --enable-static --enable--cxx" with
environment variables (I gave the variables a try after reading this
tutorial:
http://cygwin.wikia.com/wiki/How_to_install_a_newer_version_of_GCC).

3. With "./configure --disable-shared --enable-static --enable--cxx" without
environment variables.

Each time the same warnings came up when running "make".

Making some research on the Internet, I found out that the error my be the
result of no "libtool -no-undefined" command related to forbidding libtool
to use shared libraries. I was relatively happy to find another solution to
another problem, but still, this wasn't enough... When I run either "libtool
--mode=-no-undefined", or "libtool --mode=no-undefined" in libtool 2.4.1, I
receive the following message:
http://old.nabble.com/file/p32849825/GMP%2Boutputs%2Band%2Bthe%2Blog.zip
GMP+outputs+and+the+log.zip 
http://old.nabble.com/file/p32849825/Libtool%2Boutputs.zip
Libtool+outputs.zip 

$ libtool --mode=-no-undefined
libtool: -no-undefined: invalid argument for --mode

Again, I thought that updating the libtool itself could, probably, help me.
So I checked up the libtool's website and downloaded version 2.4.2. Now the
configuration and installation of libtool itself is the point at which my
mind boggles completely. The reason for this is that neither "./configure",
"make -j 2", nor "make install" doesn't return any error, and after the
whole process libtool's version remains at 2.4.1 :/

This is just insane, and I'm starting to feel that using Cygwin is like
facing a pyramid of problems... I simply don't know what next to do from
here. I don't know if it's the problem with setup.exe which suggests
official but older versions than those I downloaded, or maybe something
completely else...

At this point I am totally clueless and would be incredibly grateful if
anyone could help me out.

P.S. I've attached the outputs of GMP and libtool installation to this
message
-- 
View this message in context: http://old.nabble.com/Problems-with-updating-nearly-any-package-meant-for-Cygwin-or-using-packages-such-as-libtool-tp32849825p32849825.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[Larry Hall (Cygwin)]

On 11/15/2011 2:28 PM, viper_88 wrote:
> The avalanche of my problems has started when I wanted to install
> compat-libstdc++ 33-3.2.3. The installation failed due to the following
> dependencies errors:
>
> error: Failed dependencies:
>          /sbin/ldconfig is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libc.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libc.so.6(GLIBC_2.0) is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libc.so.6(GLIBC_2.1) is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libc.so.6(GLIBC_2.1.3) is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libc.so.6(GLIBC_2.2) is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libc.so.6(GLIBC_2.3) is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libgcc_s.so.1 is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libgcc_s.so.1(GCC_3.0) is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libgcc_s.so.1(GCC_3.3) is needed by compat-libstdc++-33-3.2.3-55.fc5
>          libgcc_s.so.1(GLIBC_2.0) is needed by
> compat-libstdc++-33-3.2.3-55.fc5
>          libm.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5

Hm.  This looks to me like output of rpm or yum on a Linux system.  If
you're trying to install Linux binary RPMs onto Cygwin, you're in for a
world of hurt.  Cygwin != Linux.  You need to build from source on Cygwin.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[viper_88]

Larry Hall (Cygwin) wrote:
> 
> On 11/15/2011 2:28 PM, viper_88 wrote:
>> The avalanche of my problems has started when I wanted to install
>> compat-libstdc++ 33-3.2.3. The installation failed due to the following
>> dependencies errors:
>>
>> error: Failed dependencies:
>>          /sbin/ldconfig is needed by compat-libstdc++-33-3.2.3-55.fc5
>>          libc.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>          libc.so.6(GLIBC_2.0) is needed by
>> compat-libstdc++-33-3.2.3-55.fc5
>>          libc.so.6(GLIBC_2.1) is needed by
>> compat-libstdc++-33-3.2.3-55.fc5
>>          libc.so.6(GLIBC_2.1.3) is needed by
>> compat-libstdc++-33-3.2.3-55.fc5
>>          libc.so.6(GLIBC_2.2) is needed by
>> compat-libstdc++-33-3.2.3-55.fc5
>>          libc.so.6(GLIBC_2.3) is needed by
>> compat-libstdc++-33-3.2.3-55.fc5
>>          libgcc_s.so.1 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>          libgcc_s.so.1(GCC_3.0) is needed by
>> compat-libstdc++-33-3.2.3-55.fc5
>>          libgcc_s.so.1(GCC_3.3) is needed by
>> compat-libstdc++-33-3.2.3-55.fc5
>>          libgcc_s.so.1(GLIBC_2.0) is needed by
>> compat-libstdc++-33-3.2.3-55.fc5
>>          libm.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
> 
> Hm.  This looks to me like output of rpm or yum on a Linux system.  If
> you're trying to install Linux binary RPMs onto Cygwin, you're in for a
> world of hurt.  Cygwin != Linux.  You need to build from source on Cygwin.
> 
> -- 
> Larry
> 
> _____________________________________________________________________
> 
> A: Yes.
>  > Q: Are you sure?
>  >> A: Because it reverses the logical flow of conversation.
>  >>> Q: Why is top posting annoying in email?
> 
> --
> 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
> 
> 
> 
Hello there, Larry, and thank you for your reply.

You were right, I indeed tried to install compat-libstdc++ using an RPM
file. I am still learning Cygwin, so I wasn't sure whether it supports them
or not (and the RPM's were the first to pop when searching for any sources).
It seems, however, that now I have faced a problem with GLIBC, which is
required to update GCC, that I won't be able to deal with (and I haven't
updated libstdc++ due to this yet)...

Namely, when looking up if I had GLIBC installed, I realized that I didn't
have it at all. I found GLIBC version 2.14.1, but when I ran "./configure" I
was presented with the following message:

"You must configure in a separate build directory".

This made me to run into further research during which I found out that
GLIBC needs a temporary directory created with the "mkdir" command. I
struggled with this concept a bit, but I finally managed to create such a
directory. Then I ran the usual "./configure" command (thinking that  now
everything will work just fine) only to be presented this:

Hubert@Hubert-PC /cygdrive/c/Cygwin/usr/src/glibc-build
$ ../glibc-2.14.1/configure
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking for gcc... gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
configure: running configure fragment for add-on libidn
configure: running configure fragment for add-on nptl
*** The GNU C library is currently not available for this platform.
*** So far nobody cared to port it and if there is no volunteer it
*** might never happen.  So, if you have interest to see glibc on
*** this platform visit
***     http://www.gnu.org/software/libc/porting.html
*** and join the group of porters

Hubert@Hubert-PC /cygdrive/c/Cygwin/usr/src/glibc-build
$

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
-- 
View this message in context: http://old.nabble.com/Problems-with-updating-nearly-any-package-meant-for-Cygwin-or-using-packages-such-as-libtool-tp32849825p32857072.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[marco atzeri]

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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[Jesse Ziser]

On 11/16/2011 1:34 PM, viper_88 wrote:
>
>
> Larry Hall (Cygwin) wrote:
>>
>> On 11/15/2011 2:28 PM, viper_88 wrote:
>>> The avalanche of my problems has started when I wanted to install
>>> compat-libstdc++ 33-3.2.3. The installation failed due to the following
>>> dependencies errors:
>>>
>>> error: Failed dependencies:
>>>           /sbin/ldconfig is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>           libc.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>           libc.so.6(GLIBC_2.0) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>           libc.so.6(GLIBC_2.1) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>           libc.so.6(GLIBC_2.1.3) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>           libc.so.6(GLIBC_2.2) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>           libc.so.6(GLIBC_2.3) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>           libgcc_s.so.1 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>           libgcc_s.so.1(GCC_3.0) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>           libgcc_s.so.1(GCC_3.3) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>           libgcc_s.so.1(GLIBC_2.0) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>           libm.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>
>> Hm.  This looks to me like output of rpm or yum on a Linux system.  If
>> you're trying to install Linux binary RPMs onto Cygwin, you're in for a
>> world of hurt.  Cygwin != Linux.  You need to build from source on Cygwin.
>>
>> --
>> Larry
>>
>> _____________________________________________________________________
>>
>> A: Yes.
>>   >  Q: Are you sure?
>>   >>  A: Because it reverses the logical flow of conversation.
>>   >>>  Q: Why is top posting annoying in email?
>>
>> --
>> 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
>>
>>
>>
> Hello there, Larry, and thank you for your reply.
>
> You were right, I indeed tried to install compat-libstdc++ using an RPM
> file. I am still learning Cygwin, so I wasn't sure whether it supports them
> or not (and the RPM's were the first to pop when searching for any sources).

It's not an issue of whether Cygwin supports RPMs.  It's an issue of 
trying to install a Linux executable on Cygwin.  It doesn't matter 
whether it's packaged in an RPM, it's still a Linux binary, not a Cygwin 
binary.

> It seems, however, that now I have faced a problem with GLIBC, which is
> required to update GCC, that I won't be able to deal with (and I haven't
> updated libstdc++ due to this yet)...

 From the Cygwin FAQ (which I strongly recommend reading):


Where is glibc?
	

Cygwin does not provide glibc. It uses newlib instead, which provides 
much (but not all) of the same functionality. Porting glibc to Cygwin 
would be difficult.


THC-Hydra claims that it builds fine on Cygwin.  Does it not?

-- 
+---------------------------+
| Jesse Ziser, Code Warrior |
| Applied Research Labs: UT |
+---------------------------+

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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[Christopher Faylor]

On Wed, Nov 16, 2011 at 11:34:11AM -0800, viper_88 wrote:
>
>
>Larry Hall (Cygwin) wrote:
>> 
>> On 11/15/2011 2:28 PM, viper_88 wrote:
>>> The avalanche of my problems has started when I wanted to install
>>> compat-libstdc++ 33-3.2.3. The installation failed due to the following
>>> dependencies errors:
>>>
>>> error: Failed dependencies:
>>>          /sbin/ldconfig is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>          libc.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>          libc.so.6(GLIBC_2.0) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>          libc.so.6(GLIBC_2.1) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>          libc.so.6(GLIBC_2.1.3) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>          libc.so.6(GLIBC_2.2) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>          libc.so.6(GLIBC_2.3) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>          libgcc_s.so.1 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>          libgcc_s.so.1(GCC_3.0) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>          libgcc_s.so.1(GCC_3.3) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>          libgcc_s.so.1(GLIBC_2.0) is needed by
>>> compat-libstdc++-33-3.2.3-55.fc5
>>>          libm.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
>> 
>> Hm.  This looks to me like output of rpm or yum on a Linux system.  If
>> you're trying to install Linux binary RPMs onto Cygwin, you're in for a
>> world of hurt.  Cygwin != Linux.  You need to build from source on Cygwin.
>> 
>Hello there, Larry, and thank you for your reply.
>
>You were right, I indeed tried to install compat-libstdc++ using an RPM
>file. I am still learning Cygwin, so I wasn't sure whether it supports them
>or not (and the RPM's were the first to pop when searching for any sources).
>It seems, however, that now I have faced a problem with GLIBC, which is
>required to update GCC, that I won't be able to deal with (and I haven't
>updated libstdc++ due to this yet)...
>
>Namely, when looking up if I had GLIBC installed, I realized that I didn't
>have it at all. I found GLIBC version 2.14.1, but when I ran "./configure" I
>was presented with the following message:
>
>"You must configure in a separate build directory".

Sorry but it seems like you're seriously confused about what Cygwin is
and how to use it.

The Cygwin web page tries to make it clear that the way to install and
update Cygwin is via the setup.exe program.  You don't use rpm.  You
install packages via setup.exe.  This is similar in concept to a Linux
environment.  Ubunutu has .deb packages, Fedora has .rpms.  We have our
much cruder .tar.bz2 files.  All are meant to be installed via their
respective package managers.

Glibc will not work on Cygwin.  That is not normally an issue since the
Cygwin DLL is supposed to provide much of the glibc functionality.  It's
the whole reason for the Cygwin project in fact.

I've never heard of a package which required you to build glibc.  It is
very unlikely that you need it.

What you likely do need are things like gcc, binutils, make, and random
other libraries, all of which can be installed via setup.exe.  Once you've
installed those, you should be able to run "configure/make" and it is
possible that things will build correctly.

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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[Tim Prince]

On 11/16/2011 3:04 PM, Jesse Ziser wrote:
> On 11/16/2011 1:34 PM, viper_88 wrote:
>>
>>
>> Larry Hall (Cygwin) wrote:
>>>
>>> On 11/15/2011 2:28 PM, viper_88 wrote:
>>>> The avalanche of my problems has started when I wanted to install
>>>> compat-libstdc++ 33-3.2.3. The installation failed due to the following
>>>> dependencies errors:
>>>>
>>>> error: Failed dependencies:
>>>> /sbin/ldconfig is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>> libc.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>> libc.so.6(GLIBC_2.0) is needed by
>>>> compat-libstdc++-33-3.2.3-55.fc5
>>>> libc.so.6(GLIBC_2.1) is needed by
>>>> compat-libstdc++-33-3.2.3-55.fc5
>>>> libc.so.6(GLIBC_2.1.3) is needed by
>>>> compat-libstdc++-33-3.2.3-55.fc5
>>>> libc.so.6(GLIBC_2.2) is needed by
>>>> compat-libstdc++-33-3.2.3-55.fc5
>>>> libc.so.6(GLIBC_2.3) is needed by
>>>> compat-libstdc++-33-3.2.3-55.fc5
>>>> libgcc_s.so.1 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>> libgcc_s.so.1(GCC_3.0) is needed by
>>>> compat-libstdc++-33-3.2.3-55.fc5
>>>> libgcc_s.so.1(GCC_3.3) is needed by
>>>> compat-libstdc++-33-3.2.3-55.fc5
>>>> libgcc_s.so.1(GLIBC_2.0) is needed by
>>>> compat-libstdc++-33-3.2.3-55.fc5
>>>> libm.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
>>>
>>> Hm. This looks to me like output of rpm or yum on a Linux system. If
>>> you're trying to install Linux binary RPMs onto Cygwin, you're in for a
>>> world of hurt. Cygwin != Linux. You need to build from source on Cygwin.
>>>
>>> --
>>> Larry
>>>
>>> _____________________________________________________________________
>>>
>>> A: Yes.
>>> > Q: Are you sure?
>>> >> A: Because it reverses the logical flow of conversation.
>>> >>> Q: Why is top posting annoying in email?
>>>
>>> --
>>> 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
>>>
>>>
>>>
>> Hello there, Larry, and thank you for your reply.
>>
>> You were right, I indeed tried to install compat-libstdc++ using an RPM
>> file. I am still learning Cygwin, so I wasn't sure whether it supports
>> them
>> or not (and the RPM's were the first to pop when searching for any
>> sources).
>
> It's not an issue of whether Cygwin supports RPMs. It's an issue of
> trying to install a Linux executable on Cygwin. It doesn't matter
> whether it's packaged in an RPM, it's still a Linux binary, not a Cygwin
> binary.
>
>> It seems, however, that now I have faced a problem with GLIBC, which is
>> required to update GCC, that I won't be able to deal with (and I haven't
>> updated libstdc++ due to this yet)...
>
>  From the Cygwin FAQ (which I strongly recommend reading):
>
>
> Where is glibc?
>
>
> Cygwin does not provide glibc. It uses newlib instead, which provides
> much (but not all) of the same functionality. Porting glibc to Cygwin
> would be difficult.
>
>
> THC-Hydra claims that it builds fine on Cygwin. Does it not?
>

As thc was stated to use mingw for Windows support, it would seem that 
it should work with the mingw cross compilers, although uwin was 
recommended.  If you want native cygwin, or even if the purpose is only 
to gain a more recent version of g++ cross compiler (without all the 
language support of the cross compilers on the cygwin install menu) it 
seems you should consider whether the gain is worth the effort, when 
your original question was how to get a gfortran for Windows.

-- 
Tim Prince

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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[viper_88]

If only compiling and installing Hydra in real life was so easy, I wouldn't
be writing about things that don't work. First things first, though...
Let me tell you, from begining to end, what I have got through first to end
up with having problems using and/or updating libtool as said in the very
title.
When I want to compile Hydra, I get this:
Hubert@Hubert-PC ~
$ cd Hydra

Hubert@Hubert-PC ~/Hydra
$ ./configure

Starting hydra auto configuration ...

Checking for openssl (libssl, libcrypto, ssl.h, sha.h) ...
                                                       ... found
Checking for idn (libidn.so) ...
                             ... NOT found, unicode logins and passwords
will no
t be supported
Checking for pcre (libpcre.so, pcre.h) ...
                                       ... NOT found, server response checks
wil
l be less reliable
Checking for Postgres (libpq.so, libpq-fe.h) ...
                                             ... NOT found, module postgres
disa
bled
Checking for SVN (libsvn_client-1 libapr-1.so libaprutil-1.so) ...
                                                               ... NOT
found, mo
dule svn disabled
Checking for firebird (libfbclient.so) ...
                                       ... NOT found, module firebird
disabled
Checking for MYSQL client (libmysqlclient.so, math.h) ...
                                                      ... NOT found, module
Mysq
l will not support version > 4.x
Checking for AFP (libafpclient.so) ...
                                   ... NOT found, module Apple Filing
Protocol d
isabled - Apple sucks anyway
Checking for NCP (libncp.so / nwcalls.h) ...
                                         ... NOT found, module NCP disabled
Checking for SAP/R3 (librfc/saprfc.h) ...
                                      ... NOT found, module sapr3 disabled
Get it from http://www.sap.com/solutions/netweaver/linux/eval/index.asp
Checking for libssh (libssh/libssh.h) ...
                                      ... NOT found, module ssh disabled
Get it from http://www.libssh.org
Checking for Oracle (libocci.so libclntsh.so / oci.h) ...
                                                      ... NOT found, module
Orac
le disabled
Checking for GUI req's (pkg-config, gtk+-2.0) ...
                                              ... found

Hydra will be installed into .../bin of: /usr/local
  (change this by running ./configure --prefix=path)

Writing Makefile.in ...

Cygwin detected, if compilation fails just update your installation.

Windres found, will attach icons to hydra cygwin executables

now type "make"

Hubert@Hubert-PC ~/Hydra
$

As you can easily see, most of the stuff is missing. It's a bit odd, though,
since when I look for, say, pcre (which I definitely had installed), I get
this:

Hubert@Hubert-PC ~
$ apt-cyg find pcre
Working directory is /setup
Mirror is ftp://mirror.mcs.anl.gov/pub/cygwin
--2011-11-16 22:31:12--  ftp://mirror.mcs.anl.gov/pub/cygwin/setup.bz2
           => `.listing'
Resolving mirror.mcs.anl.gov (mirror.mcs.anl.gov)... 146.137.96.7,
146.137.96.15
, 2620:0:dc0:1800:214:4fff:fe7d:1b9
Connecting to mirror.mcs.anl.gov (mirror.mcs.anl.gov)|146.137.96.7|:21...
connec
ted.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /pub/cygwin ... done.
==> PASV ... done.    ==> LIST ... done.

    [ <=>                                   ] 1,043       --.-K/s   in 0s

2011-11-16 22:31:14 (4.76 MB/s) - `.listing' saved [1043]

Removed `.listing'.
--2011-11-16 22:31:14--  ftp://mirror.mcs.anl.gov/pub/cygwin/setup.bz2
           => `setup.bz2'
==> CWD not required.
==> PASV ... done.    ==> RETR setup.bz2 ... done.
Length: 276018 (270K)

100%[======================================>] 276,018      169K/s   in 1.6s

2011-11-16 22:31:16 (169 KB/s) - `setup.bz2' saved [276018]

Updated setup.ini

Searching for installed packages matching pcre:
libpcre-devel
libpcre0
libpcrecpp-devel
libpcrecpp0
pcre

Searching for installable packages matching pcre:
libpcre-devel
libpcre0
libpcrecpp-devel
libpcrecpp0
pcre
pcre-devel

Hubert@Hubert-PC ~
$

pcre is installed already, so I have no idea why Cygwin says it is not (I
also thought I had postgres, but instead I found postgresql which seems not
to be what's needed). Generally speaking, most of the packages is missing,
so the compiled Hydra would lack many of its capabilities (and that I don't
want). The reason for which I started looking around was to gather
everything and make everything work. So that is one thing. The other one is
that when I wanted to update libstdc++, in order to later work with GCC, I
got this:

error: Failed dependencies:
        /sbin/ldconfig is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.0) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.1) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.1.3) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.2) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libc.so.6(GLIBC_2.3) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libgcc_s.so.1 is needed by compat-libstdc++-33-3.2.3-55.fc5
        libgcc_s.so.1(GCC_3.0) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libgcc_s.so.1(GCC_3.3) is needed by compat-libstdc++-33-3.2.3-55.fc5
        libgcc_s.so.1(GLIBC_2.0) is needed by
compat-libstdc++-33-3.2.3-55.fc5
        libm.so.6 is needed by compat-libstdc++-33-3.2.3-55.fc5

(which is already strange, saying it wants files from GCC 3.3 when I already
have GCC  4.5.3).

Now I had read that Cygwin uses newlib instead of glibc (I really do some
research and educate myself before writing anywhere for help). Since you say
RPM's cannot be installed with Cygwin, I've been trying to find libstdc++
source to compile it in Cygwin. I've browsed the doxygen directory under the
http://gcc.petsads.us/libstdc++ , but the only thing I found there,
regarding the latest 4.5.2 version, were some manuals in html or  PDF -
there is no configure file to begin with. How am I, then, supposed to
configure and install it? 
As for the GCC itself, when I want to update my GCC 4.5.3 to GCC 4.6.2 by
configuring it first in preparation for libstdc++, assuming that the newest
version of GCC would make it work, I get this:

Hubert@Hubert-PC ~/gcc-4.6.2
$ ./configure
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /usr/bin/sed
checking for gawk... gawk
checking to see if cat works as expected... yes
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for gnatbind... gnatbind
checking for gnatmake... gnatmake
checking whether compiler driver understands Ada... yes
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1
$$f
2
checking for objdir... .libs
checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h... no
configure: error: Building GCC requires GMP 4.2+, MPFR 2.3.1+ and MPC
0.8.0+.
Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify
their locations.  Source code for these libraries can be found at
their respective hosting sites as well as at
ftp://gcc.gnu.org/pub/gcc/infrastructure/.  See also
http://gcc.gnu.org/install/prerequisites.html for additional info.  If
you obtained GMP, MPFR and/or MPC from a vendor distribution package,
make sure that you have installed both the libraries and the header
files.  They may be located in separate packages.

The culprit that causes it to fail is, clearly, this: "configure: error:
Building GCC requires GMP 4.2+, MPFR 2.3.1+ and MPC 0.8.0+." I wanted to
start installing everything that's required by GCC, and so I found a yet
newer version of GMP than the one pointed out which is GMP 5.0.2. When
running "make" after configuration, I get the following errors:

Hubert@Hubert-PC ~/gmp-5.0.2
$ make -j 2 > Make.log
obprintf.c:66:0: warning: ISO C forbids an empty translation unit
obvprintf.c:46:0: warning: ISO C forbids an empty translation unit
obprntffuns.c:66:0: warning: ISO C forbids an empty translation unit
repl-vsnprintf.c:389:0: warning: ISO C forbids an empty translation unit
libtool: link: warning: undefined symbols not allowed in pentium4-pc-cygwin
shared libraries

Hubert@Hubert-PC ~/gmp-5.0.2
$

Now as for "ISO c forbids empty translation units", I haven't found a
solution yet. But as for the "undefined symbols", I read that a solution for
this might be to set libtool as "-no-undefined". So i run "libtool
--mode=-no-undefined" (as shown in libtool's --help output)  in my libtool
2.4.2, and get this in return:

Hubert@Hubert-PC ~
$ libtool --mode=-no-undefined
libtool: -no-undefined: invalid argument for --mode

Hubert@Hubert-PC ~
$

Running it either with the dash before "no", or without it, makes no
difference. Getting through all of this trouble I can't say that compiling
and installing Hydra is such an ease, and the only thing to do is to type
"/configure", make", "make install" (as much as I would like it to be so)
-- 
View this message in context: http://old.nabble.com/Problems-with-updating-nearly-any-package-meant-for-Cygwin-or-using-packages-such-as-libtool-tp32849825p32861517.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[marco atzeri]

On 11/17/2011 1:15 PM, viper_88 wrote:
>
> If only compiling and installing Hydra in real life was so easy, I wouldn't
> be writing about things that don't work. First things first, though...
> Let me tell you, from begining to end, what I have got through first to end
> up with having problems using and/or updating libtool as said in the very
> title.
> When I want to compile Hydra, I get this:
> Hubert@Hubert-PC ~
> $ cd Hydra
>
> Hubert@Hubert-PC ~/Hydra
> $ ./configure
>
> Starting hydra auto configuration ...
>
> Checking for openssl (libssl, libcrypto, ssl.h, sha.h) ...
>                                                         ... found
> Checking for idn (libidn.so) ...
>                               ... NOT found, unicode logins and passwords
> will no
> t be supported
> Checking for pcre (libpcre.so, pcre.h) ...
>                                         ... NOT found, server response checks
> wil
> l be less reliable
> Checking for Postgres (libpq.so, libpq-fe.h) ...
>                                               ... NOT found, module postgres
> disa
> bled
> Checking for SVN (libsvn_client-1 libapr-1.so libaprutil-1.so) ...
>                                                                 ... NOT
> found, mo
> dule svn disabled
> Checking for firebird (libfbclient.so) ...
>                                         ... NOT found, module firebird
> disabled
> Checking for MYSQL client (libmysqlclient.so, math.h) ...
>                                                        ... NOT found, module
> Mysq
> l will not support version>  4.x
> Checking for AFP (libafpclient.so) ...
>                                     ... NOT found, module Apple Filing
> Protocol d
> isabled - Apple sucks anyway
> Checking for NCP (libncp.so / nwcalls.h) ...
>                                           ... NOT found, module NCP disabled
> Checking for SAP/R3 (librfc/saprfc.h) ...
>                                        ... NOT found, module sapr3 disabled
> Get it from http://www.sap.com/solutions/netweaver/linux/eval/index.asp
> Checking for libssh (libssh/libssh.h) ...
>                                        ... NOT found, module ssh disabled
> Get it from http://www.libssh.org
> Checking for Oracle (libocci.so libclntsh.so / oci.h) ...
>                                                        ... NOT found, module
> Orac
> le disabled
> Checking for GUI req's (pkg-config, gtk+-2.0) ...
>                                                ... found
>
> Hydra will be installed into .../bin of: /usr/local
>    (change this by running ./configure --prefix=path)
>
> Writing Makefile.in ...
>
> Cygwin detected, if compilation fails just update your installation.
>
> Windres found, will attach icons to hydra cygwin executables
>
> now type "make"
>
> Hubert@Hubert-PC ~/Hydra
> $
>
> As you can easily see, most of the stuff is missing. It's a bit odd, though,
> since when I look for, say, pcre (which I definitely had installed), I get
> this:
>
> Hubert@Hubert-PC ~
> $ apt-cyg find pcre
> Working directory is /setup
> Mirror is ftp://mirror.mcs.anl.gov/pub/cygwin
> --2011-11-16 22:31:12--  ftp://mirror.mcs.anl.gov/pub/cygwin/setup.bz2
>             =>  `.listing'
> Resolving mirror.mcs.anl.gov (mirror.mcs.anl.gov)... 146.137.96.7,
> 146.137.96.15
> , 2620:0:dc0:1800:214:4fff:fe7d:1b9
> Connecting to mirror.mcs.anl.gov (mirror.mcs.anl.gov)|146.137.96.7|:21...
> connec
> ted.
> Logging in as anonymous ... Logged in!
> ==>  SYST ... done.    ==>  PWD ... done.
> ==>  TYPE I ... done.  ==>  CWD (1) /pub/cygwin ... done.
> ==>  PASV ... done.    ==>  LIST ... done.
>
>      [<=>                                    ] 1,043       --.-K/s   in 0s
>
> 2011-11-16 22:31:14 (4.76 MB/s) - `.listing' saved [1043]
>
> Removed `.listing'.
> --2011-11-16 22:31:14--  ftp://mirror.mcs.anl.gov/pub/cygwin/setup.bz2
>             =>  `setup.bz2'
> ==>  CWD not required.
> ==>  PASV ... done.    ==>  RETR setup.bz2 ... done.
> Length: 276018 (270K)
>
> 100%[======================================>] 276,018      169K/s   in 1.6s
>
> 2011-11-16 22:31:16 (169 KB/s) - `setup.bz2' saved [276018]
>
> Updated setup.ini
>
> Searching for installed packages matching pcre:
> libpcre-devel
> libpcre0
> libpcrecpp-devel
> libpcrecpp0
> pcre
>
> Searching for installable packages matching pcre:
> libpcre-devel
> libpcre0
> libpcrecpp-devel
> libpcrecpp0
> pcre
> pcre-devel
>
> Hubert@Hubert-PC ~
> $
>
> pcre is installed already, so I have no idea why Cygwin says it is not (I
> also thought I had postgres, but instead I found postgresql which seems not
> to be what's needed). Generally speaking, most of the packages is missing,
> so the compiled Hydra would lack many of its capabilities (and that I don't
> want). The reason for which I started looking around was to gather
> everything and make everything work. So that is one thing. The other one is
> that when I wanted to update libstdc++, in order to later work with GCC, I
> got this:

Dear Hubert,
the problem is that the configure scripts incorrectly looks for
libpcre.so that on cygwin is called differently:

/usr/bin/cygpcre-0.dll

so you need to modify the configure accordingly or
remove the test and leave only the check for "pcre.h"

same for libidn     /usr/bin/cygidn-11.dll

libpq     /usr/bin/cygpq.dll

and so on.
These are upstream bugs in configure, looking for the lib
is wrong as different platforms have different conventions.
They should only look for the header.

libstdc++ is also available on cygwin

$ cygcheck -c -d |grep c++
libstdc++6                     4.5.3-3
libstdc++6-devel               4.5.3-3

please install gcc4-g++ if you want to compile C++


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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[Andrey Repin]

Greetings, viper_88!

> As you can easily see, most of the stuff is missing. It's a bit odd, though,
> since when I look for, say, pcre (which I definitely had installed), I get
> this:

> Searching for installed packages matching pcre:
> libpcre-devel
> libpcre0
> libpcrecpp-devel
> libpcrecpp0
> pcre

> Searching for installable packages matching pcre:
> libpcre-devel
> libpcre0
> libpcrecpp-devel
> libpcrecpp0
> pcre
> pcre-devel

> Hubert@Hubert-PC ~
> $

> pcre is installed already,

I think you need pcre-devel if you're looking to compile stuff that depends on
it...


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 17.11.2011, <22:47>

Sorry for my terrible english...


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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[Dave Korn]

On 17/11/2011 13:00, marco atzeri wrote:

> the problem is that the configure scripts incorrectly looks for
> libpcre.so that on cygwin is called differently:
> 
> /usr/bin/cygpcre-0.dll
> 
> so you need to modify the configure accordingly or
> remove the test and leave only the check for "pcre.h"
> 
> same for libidn     /usr/bin/cygidn-11.dll
> 
> libpq     /usr/bin/cygpq.dll
> 
> and so on.
> These are upstream bugs in configure, looking for the lib
> is wrong as different platforms have different conventions.
> They should only look for the header.

  Well, they could look for the lib too, as long as they used the correct
autoconf macro (AC_CHECK_LIB or AC_SEARCH_LIB) to do so.  Rather than try
searching in arbitrary and unknown places for unknown file names, that just
tries running a compile with the relevant -l flag and seeing if it succeeds -
which for the purposes of the build is more definitively accurate anyway.


    cheers,
      DaveK


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

Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool

[Dave Korn]

On 17/11/2011 20:33, Dave Korn wrote:
> On 17/11/2011 13:00, marco atzeri wrote:
> 
>> the problem is that the configure scripts incorrectly looks for
>> libpcre.so that on cygwin is called differently:
>>
>> /usr/bin/cygpcre-0.dll
>>
>> so you need to modify the configure accordingly or
>> remove the test and leave only the check for "pcre.h"
>>
>> same for libidn     /usr/bin/cygidn-11.dll
>>
>> libpq     /usr/bin/cygpq.dll
>>
>> and so on.
>> These are upstream bugs in configure, looking for the lib
>> is wrong as different platforms have different conventions.
>> They should only look for the header.
> 
>   Well, they could look for the lib too, as long as they used the correct
> autoconf macro (AC_CHECK_LIB or AC_SEARCH_LIB) to do so.  


  Whoops, no they can't.  The hydra configure script isn't from autconf at
all; it's just hand-written.

  Well, at least it serves as an object lesson in why you shouldn't do that
(see also: reinventing the wheel, NIH syndrome).

    cheers,
      DaveK

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