public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: newlib@sourceware.org
Subject: Re: nds broken by recent patches
Date: Fri, 28 Jan 2022 09:36:45 -0700	[thread overview]
Message-ID: <3da42247-9096-0a03-4b38-66460854c2c7@gmail.com> (raw)
In-Reply-To: <YfPDA/LVL745V+02@vapier>



On 1/28/2022 3:18 AM, Mike Frysinger wrote:

> np.  if my changes break a target, feel free to kick it up and i'll take a
> look.  shouldn't be too hard as long as the port is healthy and binutils &
> gcc work properly.  just remember to highlight the exact tuple you're using
> so i don't have to try and guess for these esoteric targets.  i tried to use
> nds32-elf here and that doesn't work, so i had to dig through grep output to
> see that nds32le-elf seems to work.
Well, part of the problem is we've got multiple targets failing in many 
different ways.

For example, someone mucked up the compiler for or1k-elf at the same 
time you're doing your refactoring.  Now I've got a patch to fix the 
compiler ICE, *but* I'm also getting a crap-ton of new testsuite 
failures in the testsuite due to missing _init/_fini symbols.  I don't 
know yet if that's a newlib issue or something else mucked up on the 
compiler side.

The h8300-elf port in the last few days has started failing while 
building newlib with:

cp: cannot stat 'libc/crt0.o': No such file or directory

The iq-2000-elf port has started failing building newlib in the last few 
days with:

make[3]: *** No rule to make target 'configure', needed by 
'config.status'.  Stop.
make[3]: Leaving directory 
'/home/jlaw/jenkins/workspace/iq2000-elf/iq2000-elf-obj/newlib/iq2000-elf/libgloss/iq2000'
make[2]: *** [Makefile:132: stmp-bsp] Error 2


And there's others.  Some are definitely on the GCC side (arc failures 
for example) , but having so many things breaking at once is frustrating.

Jeff

  parent reply	other threads:[~2022-01-28 16:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <171dc9cb-6b2c-ead3-1c55-27fadb33220f@gmail.com>
2022-01-28 10:23 ` [PATCH 1/2] newlib: fix preprocessor checks Mike Frysinger
2022-01-28 10:23   ` [PATCH 2/2] newlib: add AC_CACHE_CHECK sugar around " Mike Frysinger
2022-01-31 14:20     ` Corinna Vinschen
2022-01-31 14:18   ` [PATCH 1/2] newlib: fix " Corinna Vinschen
     [not found] ` <YfPDA/LVL745V+02@vapier>
2022-01-28 16:36   ` Jeff Law [this message]
2022-01-28 21:54     ` nds broken by recent patches Jeff Law
2022-01-28 23:32       ` Stafford Horne
2022-01-29  0:58         ` Jeff Law
2022-01-29  2:12           ` Stafford Horne
2022-01-29  3:28             ` Jeff Law
2022-01-29  5:15       ` Mike Frysinger
2022-01-29  5:12     ` [PATCH/committed] libgloss: update Makefile regen rules for merged arches Mike Frysinger
2022-01-29  5:13     ` nds broken by recent patches Mike Frysinger
2022-01-31 14:34       ` R. Diez
2022-02-01 17:25       ` Jeff Law
2022-02-02 10:23         ` Mike Frysinger
2022-02-02 20:59           ` Jeff Law
2022-02-03 16:11       ` libgloss multilib installs broken [was nds broken by recent patches] Jeff Law
2022-02-04  5:45         ` Mike Frysinger
2022-02-07 15:40           ` Jeff Law
2022-02-04  8:55         ` [PATCH] libgloss: restore multilib settings in subdir makefiles 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=3da42247-9096-0a03-4b38-66460854c2c7@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=newlib@sourceware.org \
    --cc=vapier@gentoo.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).