From: Nathanael Nerode <neroden@twcny.rr.com>
To: Andrew Cagney <ac131313@redhat.com>, nickk@ubicom.com
Cc: gdb@sources.redhat.com
Subject: Re: Trunk build problems
Date: Sun, 22 Dec 2002 23:43:00 -0000 [thread overview]
Message-ID: <3E06BE00.1070707@twcny.rr.com> (raw)
In-Reply-To: <3DFE3F30.5060304@redhat.com>
>> - Under cygwin, libtermcap attempts to be build (which doesn't exist).
>> This
>> causes a circular make problem as it can't change into the directory
>> so does
>> a make in src again.
Rrrrm. I'll see if I can track that one down, it's new to me.
--Nathanael
next prev parent reply other threads:[~2002-12-23 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 12:36 Nick Kelsey
2002-12-16 12:41 ` Daniel Jacobowitz
2002-12-16 12:59 ` Elena Zannoni
2002-12-16 13:01 ` Andrew Cagney
2002-12-16 13:18 ` DJ Delorie
2002-12-22 23:43 ` Nathanael Nerode [this message]
[not found] ` <redirect-4840171@silicondust.com>
2002-12-16 13:12 ` Nick Kelsey
2002-12-16 19:22 ` Christopher Faylor
2002-12-16 17:58 ` Christopher Faylor
2002-12-16 18:06 ` Christopher Faylor
[not found] <redirect-4840161@silicondust.com>
2002-12-18 19:21 ` Nick Kelsey
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=3E06BE00.1070707@twcny.rr.com \
--to=neroden@twcny.rr.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=nickk@ubicom.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