public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] libgloss: drop unused multi-build logic
Date: Tue, 20 Dec 2022 00:08:07 +0000 (GMT)	[thread overview]
Message-ID: <20221220000807.0FDA53858D32@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=2dfc4a9e973dd6c74b61b1f25630080de23580dd

commit 2dfc4a9e973dd6c74b61b1f25630080de23580dd
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Tue Dec 13 21:12:02 2022 -0500

    libgloss: drop unused multi-build logic
    
    Now that aarch64 & arm have migrated off this, we can punt it.

Diff:
---
 libgloss/doc/porting.texi |  4 +--
 libgloss/multi-build.in   | 66 -----------------------------------------------
 2 files changed, 1 insertion(+), 69 deletions(-)

diff --git a/libgloss/doc/porting.texi b/libgloss/doc/porting.texi
index 496fae352..15f214d02 100644
--- a/libgloss/doc/porting.texi
+++ b/libgloss/doc/porting.texi
@@ -398,9 +398,7 @@ any target that has migrated to @value{automake}.
 
 Libgloss automatically builds itself for all multilib configurations that the
 active toolchain supports.  This logic is provided by common code from the
-combined toolchain source tree.  This should @strong{not} be confused with the
-Libgloss-specific @file{multi-build.in} file.  That is used by a few ports to
-further produce multiple targets.
+combined toolchain source tree.
 
 @node GCC, Libraries, Libgloss, Top
 @chapter Porting GCC
diff --git a/libgloss/multi-build.in b/libgloss/multi-build.in
deleted file mode 100644
index 80919ed6f..000000000
--- a/libgloss/multi-build.in
+++ /dev/null
@@ -1,66 +0,0 @@
-# This is like ../multilib.am and ../config-ml.in and ../config/multi.m4 mashed
-# into one file.  It relies on some custom hardcoded MULTI* variables in the
-# respective Makefile.in instead of dynamic compiler probing that ../multilib.am
-# does.
-
-PWD_COMMAND=$${PWDCMD-pwd}
-
-# FIXME: There should be an @-sign in front of the `if'.
-# Leave out until this is tested a bit more.
-libgloss-multi-do:
-	if [ -z "$(MULTIDIRS)" ]; then \
-	  true; \
-	else \
-	  rootpre=`${PWD_COMMAND}`/; export rootpre; \
-	  srcrootpre=`cd $(srcdir); ${PWD_COMMAND}`/; export srcrootpre; \
-	  lib=`echo "$${rootpre}" | sed -e 's,^.*/\([^/][^/]*\)/$$,\1,'`; export lib; \
-	  compiler="$(CC)"; \
-	  for dir in $(MULTIDIRS); do \
-	    if [ "$${dir}" = "." ]; then \
-	      true; \
-	    else \
-	      destpre=`echo $${rootpre}/$${dir}`/; export destpre; \
-	      if ! test -d $${destpre} ; then \
-		mkdir -p $${destpre}; \
-		cd $${destpre}; \
-		config_cmd=`../config.status --config | sed -re "s:--srcdir=([^/]):--srcdir=../\1:"`; \
-		$(SHELL) -c "$(SHELL) $${srcrootpre}/configure $${config_cmd}";\
-		sed -e "s:^MULTIDIRS[[:space:]]*+=.*$$:MULTIDIRS = :" \
-		    -e "s:^MULTILIBNAME[[:space:]]*=.*$$:MULTILIBNAME = MULTIDIR_$${dir}_NAME:" \
-		    -e "s:^MULTI_FLAGS_FOR_TARGET[[:space:]]*=.*$$:MULTI_FLAGS_FOR_TARGET = MULTIDIR_$${dir}_FLAGS:" \
-		    -e "s:^objdir[[:space:]]*=.*$$:objdir = ..:" \
-			Makefile > Makefile.tem; \
-		rm -f Makefile; \
-		mv Makefile.tem Makefile; \
-	      else \
-		cd $${destpre}; \
-	      fi; \
-	      if ($(MAKE) $(FLAGS_TO_PASS) \
-		    CFLAGS="$(CFLAGS)" \
-		    CCASFLAGS="$(CCASFLAGS)" \
-		    FCFLAGS="$(FCFLAGS)" \
-		    FFLAGS="$(FFLAGS)" \
-		    ADAFLAGS="$(ADAFLAGS)" \
-		    prefix="$(prefix)" \
-		    exec_prefix="$(exec_prefix)" \
-		    GCJFLAGS="$(GCJFLAGS)" \
-		    GOCFLAGS="$(GOCFLAGS)" \
-		    CXXFLAGS="$(CXXFLAGS)" \
-		    LIBCFLAGS="$(LIBCFLAGS)" \
-		    LIBCXXFLAGS="$(LIBCXXFLAGS)" \
-		    LDFLAGS="$(LDFLAGS)" \
-		    MULTIFLAGS="" \
-		    DESTDIR="$(DESTDIR)" \
-		    SOURCE="${srcdir}/" \
-		    INSTALL="$(INSTALL)" \
-		    INSTALL_DATA="$(INSTALL_DATA)" \
-		    INSTALL_PROGRAM="$(INSTALL_PROGRAM)" \
-		    INSTALL_SCRIPT="$(INSTALL_SCRIPT)" \
-		    $(DO)); then \
-		cd $${rootpre}; \
-	      else \
-		exit 1; \
-	      fi; \
-	    fi; \
-	  done; \
-	fi

                 reply	other threads:[~2022-12-20  0:08 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=20221220000807.0FDA53858D32@sourceware.org \
    --to=vapier@sourceware.org \
    --cc=newlib-cvs@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).