public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Sam James <sam@gentoo.org>, Mark Wielaard <mark@klomp.org>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: New sourceware binutils-gentoo-sparc builders
Date: Sun, 15 Jan 2023 01:22:16 +0100	[thread overview]
Message-ID: <75f698a1-1ca4-1abf-d68c-130d8f4b26ff@physik.fu-berlin.de> (raw)
In-Reply-To: <A4991FAD-0898-4CFC-B1C5-D69D8AA20993@gentoo.org>

Hi Sam!

On 1/14/23 22:34, Sam James wrote:
>> Thanks to Sam James, the Gentoo Foundation and OSUOSL
>> builder.sourceware.org now has a gentoo-sparc worker [1]
>> which runs binutils CI [2] and try [3] builders.

Nice. Would it be possible to add gcc and glibc there as well?

> I've filed a bug for this at https://sourceware.org/bugzilla/show_bug.cgi?id=30002,
> but in doing so, I ended up finding some interesting bits from the last few years.
> 
> glaubitz from Debian bisected the issue at https://sourceware.org/bugzilla/show_bug.cgi?id=26391#c10
> and came up with:
> ```
> 496afd17055aeb7d8f45e01715c475664f2b73bd is the first bad commit
> commit 496afd17055aeb7d8f45e01715c475664f2b73bd
> Author: H.J. Lu <hjl.tools@gmail.com>
> Date: Sat Sep 12 05:37:30 2020 -0700
> 
> elf: Add -z unique-symbol to avoid duplicated local symbol names
> ```

I completely forgot about this bug. I had to reread the bug report to make sure
I actually did the bisect ;-).

Adrian

-- 
  .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


  reply	other threads:[~2023-01-15  0:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 21:02 Mark Wielaard
2023-01-14 21:34 ` Sam James
2023-01-15  0:22   ` John Paul Adrian Glaubitz [this message]
2023-01-15  0:52     ` Sam James

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=75f698a1-1ca4-1abf-d68c-130d8f4b26ff@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=binutils@sourceware.org \
    --cc=mark@klomp.org \
    --cc=sam@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).