New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
binutils: 2.31.1 -> 2.32 #55485
binutils: 2.31.1 -> 2.32 #55485
Conversation
63f17ab
to
2566389
Compare
I am getting some unexplained errors when using this. Probably better to figure those out before merging. |
cc #55165 FWIW, likely same but haven't checked :). |
# Remove gold-symbol-visibility patch when updating, the proper fix | ||
# is now upstream. | ||
# https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=330b90b5ffbbc20c5de6ae6c7f60c40fab2e7a4f;hp=99181ccac0fc7d82e7dabb05dc7466e91f1645d3 | ||
version = "2.31.1"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
may wish to revise commit message since this starts with 2.31.1 not 2.30.
What errors? 😁
Not entirely unexpected, but if you get to a point where details make
sense (or perhaps hydra links) please share! :)
…On Sat, 09 Feb 2019 17:34:52 -0800, Matthew Bauer ***@***.***> wrote:
I am getting some unexplained errors when using this. Probably better to figure those out before merging.
--
You are receiving this because your review was requested.
Reply to this email directly or view it on GitHub:
#55485 (comment) part: text/html
|
Let me find the logs…
…Sent from my iPhone
On Feb 12, 2019, at 5:35 AM, Will Dietz ***@***.***> wrote:
What errors? 😁
Not entirely unexpected, but if you get to a point where details make
sense (or perhaps hydra links) please share! :)
On Sat, 09 Feb 2019 17:34:52 -0800, Matthew Bauer ***@***.***> wrote:
> I am getting some unexplained errors when using this. Probably better to figure those out before merging.
>
> --
> You are receiving this because your review was requested.
> Reply to this email directly or view it on GitHub:
> #55485 (comment) part: text/html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@dtzWill here is the error I get building coreutils on x86_64-linux with this change:
It could be the machine though. I'd be interested in seeing if anyone else has the same issue. |
Have you considered using later 2.31 branch? (no tarballs unfortunately) It happened multiple times for us that fresh binutils caused lots of failures. |
That's likely more appropriate, in terms of getting fixes somewhat
safely.
I'd expect when/if we move to 2.32 we'll really be moving to
2.32+patches or hopefully the 2.32 branch :).
Agreed moving to new versions often introduces problems,
must be done carefully with a need for more thorough testing
than pretty much any other package :).
Sounds like we should perhaps start looking at what things look
like using the branch for 2.31?
(I haven't looked closely, but until there's a feature we need
from 2.32 and 2.31 is getting fixes... that seems the way to go)
…On Fri, 22 Feb 2019 02:24:54 -0800, Vladimír Čunát ***@***.***> wrote:
Have you considered using [later 2.31 branch](https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=shortlog;h=refs/heads/binutils-2_31-branch)? (no tarballs unfortunately) It happened multiple times for us that fresh binutils caused lots of failures.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#55485 (comment) part: text/html
|
Fixes #51293.