From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH] libgloss: visium: fix sbrk search path
Date: Wed, 27 Dec 2023 01:22:29 -0500 [thread overview]
Message-ID: <20231227062229.518-1-vapier@gentoo.org> (raw)
The code was loading the common ../sbrk.c file rather than the visium
specific sbrk.c due to VPATH setup. Add an explicit rule for this one
file so we make sure the correct one is used.
---
libgloss/visium/Makefile.in | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libgloss/visium/Makefile.in b/libgloss/visium/Makefile.in
index 0e1789a2635c..bc18b2951edb 100644
--- a/libgloss/visium/Makefile.in
+++ b/libgloss/visium/Makefile.in
@@ -97,6 +97,9 @@ sim-syscalls.o: syscalls.c syscall.h io.h
debug-syscalls.o: syscalls.c syscall.h io.h
${CC} ${CFLAGS_FOR_TARGET} ${CFLAGS} -c -o $@ $<
+sbrk.o: $(srcdir)/sbrk.c
+ ${CC} ${CFLAGS_FOR_TARGET} ${CFLAGS} -c -o $@ $<
+
$(OBJS): %.o: ../%.c
${CC} ${CFLAGS_FOR_TARGET} ${CFLAGS} -c -o $@ $<
--
2.43.0
next reply other threads:[~2023-12-27 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 6:22 Mike Frysinger [this message]
2023-12-27 6:23 ` [PATCH] libgloss: merge visium into top-level Makefile Mike Frysinger
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=20231227062229.518-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=newlib@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).