From: Nick Clifton <nickc@redhat.com>
To: binutils@sourceware.org
Subject: [PATCH]: Fix include paths in iq2000.cpu
Date: Mon, 22 May 2006 15:39:00 -0000 [thread overview]
Message-ID: <m3d5e6whra.fsf@redhat.com> (raw)
Hi Guys,
I am applying the patch below to fix a small problem with the
cpu/iq2000.cpu file. This file includes the iq2000m.cpu and
iq10.cpu files, but it had a built-in path to them that does not
work under all circumstances. Since the make rules set up the
correct include paths anyway, there is no need for a built-in path,
so I have removed them.
Cheers
Nick
cpu/ChangeLog
2006-05-22 Nick Clifton <nickc@redhat.com>
* iq2000.cpu: Fix include paths for iq2000m.cpu and iq10.cpu.
Index: cpu/iq2000.cpu
===================================================================
RCS file: /cvs/src/src/cpu/iq2000.cpu,v
retrieving revision 1.4
diff -c -3 -p -r1.4 iq2000.cpu
*** cpu/iq2000.cpu 6 Jul 2005 08:18:52 -0000 1.4
--- cpu/iq2000.cpu 22 May 2006 09:05:57 -0000
***************
*** 1173,1182 ****
(if (keep-mach? (iq2000))
! (include "../../cpu/iq2000m.cpu"))
(if (keep-mach? (iq10))
! (include "../../cpu/iq10.cpu"))
!
!
!
--- 1173,1179 ----
(if (keep-mach? (iq2000))
! (include "iq2000m.cpu"))
(if (keep-mach? (iq10))
! (include "iq10.cpu"))
reply other threads:[~2006-05-22 9:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3d5e6whra.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).