From: Jesse Ziser <ziser@arlut.utexas.edu>
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:05:00 -0000 [thread overview]
Message-ID: <4EC41760.5010203@arlut.utexas.edu> (raw)
In-Reply-To: <32857072.post@talk.nabble.com>
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
next prev parent reply other threads:[~2011-11-16 20:05 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
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 [this message]
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=4EC41760.5010203@arlut.utexas.edu \
--to=ziser@arlut.utexas.edu \
--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).