public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Koeller <thomas@koeller.dyndns.org>
To: kseitz@sources.redhat.com
Cc: insight-prs@sources.redhat.com,
Subject: Re: pending/165: insight pr #148
Date: Fri, 20 Sep 2002 02:03:00 -0000 [thread overview]
Message-ID: <20020920090303.3316.qmail@sources.redhat.com> (raw)
The following reply was made to PR pending/165; it has been noted by GNATS.
From: Thomas Koeller <thomas@koeller.dyndns.org>
To: kseitz@sources.redhat.com, insight-prs@sources.redhat.com,
kseitz@sources.redhat.com, nobody@sources.redhat.com,
thomas@koeller.dyndns.org, insight-gnats@sources.redhat.com
Cc:
Subject: Re: pending/165: insight pr #148
Date: Fri, 20 Sep 2002 11:01:11 +0200
On Donnerstag, 19. September 2002 04:57, you wrote:
> Synopsis: insight pr #148
>
> Responsible-Changed-From-To: unassigned->kseitz
> Responsible-Changed-By: kseitz
> Responsible-Changed-When: Wed Sep 18 19:57:09 2002
> Responsible-Changed-Why:
> mine
> State-Changed-From-To: open->feedback
> State-Changed-By: kseitz
> State-Changed-When: Wed Sep 18 19:57:09 2002
> State-Changed-Why:
> Hmm. I've updated to using a newer cygwin and compiler environment. I
> don't see these problems at all. I'm using gcc-3.2 20020818. Where are you
> with this?
>
> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&databa
>se=insight&pr=165
We changed to Linux/based development meanwhile, and I did not upgrade my
tool chain any more, but as far as I remember I found a workaround for the
original problem. The build process aborted during building of the tcl, tk and itcl
libraries. After executing 'ar rcs <lib>' on the newly generated libraries, the build
process could be restarted.
tk
--
Thomas Koeller
thomas@koeller.dyndns.org
next reply other threads:[~2002-09-20 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 2:03 Thomas Koeller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-18 19:57 kseitz
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=20020920090303.3316.qmail@sources.redhat.com \
--to=thomas@koeller.dyndns.org \
--cc=insight-prs@sources.redhat.com \
--cc=kseitz@sources.redhat.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).