public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: hunt@redhat.com, neroden@twcny.rr.com
Cc: gdb@sources.redhat.com
Subject: Re: No rule to make target `maybe-install-tix', needed by `install-gdb'
Date: Fri, 14 Mar 2003 16:29:00 -0000	[thread overview]
Message-ID: <200303141629.h2EGTqt18709@duracef.shout.net> (raw)

hunt> The checked-in toplevel Makefile.in was not generated from the
hunt> Makefile.def in CVS.  Run 
hunt> "autogen Makefile.def" to regenerate.

Ah, the light bulb goes on.  It looks like Nathanael had a local
"no-tix" version of Makefile.def when he ran autogen.

I can fix this ... just a bit of testing to do first.

Michael C

             reply	other threads:[~2003-03-14 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 16:29 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-13  7:48 Michael Elizabeth Chastain
2003-03-13 22:54 ` Martin M. Hunt
2003-03-14 19:26   ` Nathanael Nerode

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=200303141629.h2EGTqt18709@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb@sources.redhat.com \
    --cc=hunt@redhat.com \
    --cc=neroden@twcny.rr.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).