From: Dimitar Dimitrov <dimitar@dinux.eu>
To: newlib@sourceware.org
Subject: [PATCH] libgloss: Fix mkinstalldirs path
Date: Thu, 27 Jan 2022 20:52:43 +0200 [thread overview]
Message-ID: <20220127185243.453766-1-dimitar@dinux.eu> (raw)
With the move of configure scripts out of target directories, relative
paths to top_srcdir got broken:
/bin/sh: .../newlib/libgloss/../../mkinstalldirs: No such file or directory
Fix the PRU build by switching to srcroot relative path, as rest of targets do.
I cannot test bfin, but it appears to have the same issue.
Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>
---
libgloss/bfin/Makefile.in | 3 +--
libgloss/pru/Makefile.in | 3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/libgloss/bfin/Makefile.in b/libgloss/bfin/Makefile.in
index a8ecfaf14..305ce310d 100644
--- a/libgloss/bfin/Makefile.in
+++ b/libgloss/bfin/Makefile.in
@@ -7,7 +7,6 @@ srcdir = @srcdir@
objdir = .
srcroot = $(srcdir)/../..
objroot = $(objdir)/../..
-top_srcdir = @top_srcdir@
prefix = @prefix@
exec_prefix = @exec_prefix@
@@ -30,7 +29,7 @@ MULTISUBDIR =
SHELL = /bin/sh
-mkinstalldirs = $(SHELL) $(top_srcdir)/../../mkinstalldirs
+mkinstalldirs = $(SHELL) $(srcroot)/mkinstalldirs
CC = @CC@
diff --git a/libgloss/pru/Makefile.in b/libgloss/pru/Makefile.in
index 3bf9f4529..7a2f290a8 100644
--- a/libgloss/pru/Makefile.in
+++ b/libgloss/pru/Makefile.in
@@ -29,7 +29,6 @@ srcdir = @srcdir@
objdir = .
srcroot = $(srcdir)/../..
objroot = $(objdir)/../..
-top_srcdir = @top_srcdir@
prefix = @prefix@
exec_prefix = @exec_prefix@
@@ -49,7 +48,7 @@ MULTISUBDIR =
SHELL = /bin/sh
-mkinstalldirs = $(SHELL) $(top_srcdir)/../../mkinstalldirs
+mkinstalldirs = $(SHELL) $(srcroot)/mkinstalldirs
CC = @CC@
--
2.34.1
next reply other threads:[~2022-01-27 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 18:52 Dimitar Dimitrov [this message]
2022-01-28 0:41 ` 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=20220127185243.453766-1-dimitar@dinux.eu \
--to=dimitar@dinux.eu \
--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).