From: Tilman Hausherr <tilman@snafu.de>
To: cygwin@cygwin.com
Subject: Re: Postinstall script errors
Date: Fri, 20 Aug 2010 19:32:00 -0000 [thread overview]
Message-ID: <khkt66deplk001uugc7glk44lhhfak87cg@4ax.com> (raw)
In-Reply-To: <20100813094804.GE14202@calimero.vinschen.de>
Hello,
It works now, I was able to install gcc 4.3.4.
Thanks!
Tilman
On Fri, 13 Aug 2010 11:48:04 +0200, Corinna Vinschen wrote:
>On Aug 12 19:50, Tilman Hausherr wrote:
>> On Thu, 12 Aug 2010 11:59:30 +0200, Corinna Vinschen wrote:
>>
>> >That's probably a fault in the postinstall scripts. It would be nice if
>> >you could provide more details about what fails exactly in the script,
>> >or better, what in the script has a non-0 exit code. That would help us
>> >lazy maintainers to fix the scripts faster.
>> >
>> >Keep in mind that the dialog providing info about failing postinstall
>> >scripts is very new. I'm quite sure that we have a couple of scripts
>> >which return with a non-0 exit code but the maintainers just don't know
>> >it yet, and I don't take myself out of the picture.
>>
>> I'm not sure if these faulty postinstall scripts are really THAT
>> important, I got zero reaction on a bug report with details
>> http://sourceware.org/ml/cygwin/2010-08/msg00158.html
>>
>> and I found out in the meantime that it was already reported in january
>> and was already a "known error" at that time.
>> http://old.nabble.com/gcc-command-not-found-td27393452.html#a27395128
>
>I reported this myself a couple of days ago on the cygwin-apps list.
>
> http://cygwin.com/ml/cygwin-apps/2010-08/msg00074.html
>
>
>Dave? Any word on this?
>
>
>Thanks,
>Corinna
>
>--
>Corinna Vinschen Please, send mails regarding Cygwin to
>Cygwin Project Co-Leader cygwin AT cygwin DOT com
>Red Hat
--
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:[~2010-08-20 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 15:18 Jeremy Ramer
2010-08-12 9:59 ` Corinna Vinschen
2010-08-12 13:38 ` Jeremy Ramer
2010-08-12 14:05 ` Corinna Vinschen
2010-08-12 14:10 ` Matthias Andree
2010-08-12 14:41 ` Corinna Vinschen
2010-08-12 14:52 ` Matthias Andree
2010-08-12 14:54 ` Corinna Vinschen
2010-08-12 15:04 ` Matthias Andree
2010-08-12 15:15 ` Corinna Vinschen
2010-08-12 16:02 ` Matthias Andree
2010-08-12 17:56 ` Tilman Hausherr
2010-08-13 9:48 ` Corinna Vinschen
2010-08-20 19:32 ` Tilman Hausherr [this message]
[not found] <58C73DA23112384988EEB999F2EC04DC1E78D328@ATLEISEXCMBX1.eis.equifax.com>
2016-04-11 18:51 ` Ken Brown
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=khkt66deplk001uugc7glk44lhhfak87cg@4ax.com \
--to=tilman@snafu.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).