public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: newlib@sourceware.org
Subject: Re: libgloss multilib installs broken [was nds broken by recent patches]
Date: Mon, 7 Feb 2022 08:40:56 -0700	[thread overview]
Message-ID: <42d3f65b-b268-5f7b-1d9d-081fa26e1c23@gmail.com> (raw)
In-Reply-To: <Yfy9cjPARL/E8vmA@vapier>



On 2/3/2022 10:45 PM, Mike Frysinger wrote:
> On 03 Feb 2022 09:11, Jeff Law wrote:
>> I must have tested the wrong thing as bfin-elf isn't working yet.  It
>> doesn't help that I'm only looking at this for a few minutes before my
>> workday starts...    At least now I  know what's going on.
>>
>> The *build* is fine, things go south at *install* time.
>>
>> bfin has a wide variety of multilibs and we're installing them into the
>> wrong directories.
> well that's annoying.  i was actually testing this code path recently as part
> of migrating libgloss to automake, and the install logic worked there, so i
> guess i fixed this bug and didn't realize it.
Saw you committed the fix for this over the weekend.  I can confirm that 
the bfin, visium, frv and c6x ports are happy again.  I had suspected 
they were all the same problem.

At this point there's nothing failing due to newlib/libgloss issues.  
Thanks for all the fixes.

jeff

  reply	other threads:[~2022-02-07 15:40 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   ` nds broken by recent patches Jeff Law
2022-01-28 21:54     ` 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 [this message]
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=42d3f65b-b268-5f7b-1d9d-081fa26e1c23@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --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).