public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH 2/5] newlib: phoenix: drop missing machine subdirs
Date: Thu, 10 Feb 2022 03:51:23 -0500	[thread overview]
Message-ID: <20220210085126.21023-3-vapier@gentoo.org> (raw)
In-Reply-To: <20220210085126.21023-1-vapier@gentoo.org>

These were never added to the tree, and as we transition from autoconf
to automake, it really wants the latter subdirs to always exist.  These
don't, so delete the logic.
---
 newlib/libc/sys/phoenix/machine/configure    | 11 +----------
 newlib/libc/sys/phoenix/machine/configure.ac |  3 ---
 2 files changed, 1 insertion(+), 13 deletions(-)

diff --git a/newlib/libc/sys/phoenix/machine/configure.ac b/newlib/libc/sys/phoenix/machine/configure.ac
index 05dd0f8e48b6..972ffc9c86ec 100644
--- a/newlib/libc/sys/phoenix/machine/configure.ac
+++ b/newlib/libc/sys/phoenix/machine/configure.ac
@@ -12,9 +12,6 @@ NEWLIB_CONFIGURE(../../../..)
 if test -n "${machine_dir}"; then
   case ${machine_dir} in
 	arm) AC_CONFIG_SUBDIRS(arm) ;;
-	esirisc) AC_CONFIG_SUBDIRS(esirisc) ;;
-	i386) AC_CONFIG_SUBDIRS(i386) ;;
-	powerpc) AC_CONFIG_SUBDIRS(powerpc) ;;
   esac;
 fi
 
-- 
2.34.1


  parent reply	other threads:[~2022-02-10  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  8:51 [PATCH 0/5] newlib: phoenix: kill off all subdir configure scripts Mike Frysinger
2022-02-10  8:51 ` [PATCH 1/5] newlib: phoenix: move some logic from configure to the Makefile Mike Frysinger
2022-02-10  8:51 ` Mike Frysinger [this message]
2022-02-10  8:51 ` [PATCH 3/5] newlib: phoenix: merge machine/ trampoline up a level Mike Frysinger
2022-02-10  8:51 ` [PATCH 4/5] newlib: phoenix: merge machine/ configure scripts " Mike Frysinger
2022-02-10  8:51 ` [PATCH 5/5] newlib: phoenix: merge configure up to top-level Mike Frysinger
2022-02-15 13:38 ` [PATCH 0/5] newlib: phoenix: kill off all subdir configure scripts Corinna Vinschen

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=20220210085126.21023-3-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).