Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Richard Earnshaw <rearnsha@gcc.gnu.org>
Cc: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>,
	gdb-patches@sources.redhat.com
Subject: Re: ARM Simulator build broken
Date: Wed, 24 Nov 2004 18:42:00 -0000	[thread overview]
Message-ID: <orbrdnay3g.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <1100707579.22014.47.camel@pc960.cambridge.arm.com>

On Nov 17, 2004, Richard Earnshaw <rearnsha@gcc.gnu.org> wrote:

> ! sim-basics_h = $(srccom)/sim-basics.h \
> ! 		cconfig_h \
> ! 		tconfig_h \

How are the cconfig_h and tconfig_h deps supposed to be resolved?  I
don't get any other grep matches for these strings within sim, and
at least the frv sim won't build because sim-core.o needs some
cconfig_h file that doesn't exist.  What was the idea here?
$(cconfig_h) and $(tconfig_h), maybe?

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}


  parent reply	other threads:[~2004-11-24 18:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 12:40 Richard Earnshaw
2004-11-16 15:24 ` Richard Earnshaw
2004-11-16 15:36   ` Hans-Peter Nilsson
2004-11-17 15:04     ` Richard Earnshaw
2004-11-17 16:06       ` Richard Earnshaw
2004-11-17 18:25         ` Hans-Peter Nilsson
2004-11-17 20:38           ` Andrew Cagney
2004-11-18  0:08             ` Hans-Peter Nilsson
2004-11-18 10:22               ` Richard Earnshaw
2004-11-24 18:42         ` Alexandre Oliva [this message]
2004-11-25 10:31           ` Richard Earnshaw
2004-11-25 10:48           ` Richard Earnshaw
2004-11-29 18:27             ` Alexandre Oliva

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=orbrdnay3g.fsf@livre.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hans-peter.nilsson@axis.com \
    --cc=rearnsha@gcc.gnu.org \
    /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