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] newlib: hoist crt0 install up another dir
Date: Fri, 28 Jan 2022 12:28:33 +0000 (GMT)	[thread overview]
Message-ID: <20220128122833.6D7D63948437@sourceware.org> (raw)

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

commit 7a4bef590b37683b08ebaee384d0694b9afccc57
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Fri Jan 28 07:24:18 2022 -0500

    newlib: hoist crt0 install up another dir
    
    Commit dd23de27c8e45513ad276f503a0036c3bc4e487b ("newlib: libc: install
    CRT0 straight out of subdir") got rid of the libc/sys/ intermediate for
    copying the file up, but the top-level newlib/ dir was still expecting
    a libc/crt0.o to exist so it could install.  Update that to also look
    for the crt0 file directly under libc/ like we already do for crt1.

Diff:
---
 newlib/configure    | 2 +-
 newlib/configure.ac | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/newlib/configure b/newlib/configure
index 9bbb089a9..31b790f2a 100755
--- a/newlib/configure
+++ b/newlib/configure
@@ -12442,7 +12442,7 @@ CRT0=
 CRT0_DIR=
 if test "x${have_crt0}" = "xyes"; then
   CRT0=crt0.o
-  CRT0_DIR=libc/
+  CRT0_DIR=libc/sys/${sys_dir}/
 fi
  if test x$have_crt0 = xyes; then
   HAVE_CRT0_TRUE=
diff --git a/newlib/configure.ac b/newlib/configure.ac
index 13f318922..cac2d7296 100644
--- a/newlib/configure.ac
+++ b/newlib/configure.ac
@@ -361,7 +361,7 @@ CRT0=
 CRT0_DIR=
 if test "x${have_crt0}" = "xyes"; then
   CRT0=crt0.o
-  CRT0_DIR=libc/
+  CRT0_DIR=libc/sys/${sys_dir}/
 fi
 AM_CONDITIONAL(HAVE_CRT0, test x$have_crt0 = xyes)
 AC_SUBST(CRT0)


                 reply	other threads:[~2022-01-28 12:28 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=20220128122833.6D7D63948437@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).