Skip to content
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

Update MinGW Binutils to the latest version on Stable #107575

Closed
awaken466 opened this issue Feb 1, 2023 · 8 comments
Closed

Update MinGW Binutils to the latest version on Stable #107575

awaken466 opened this issue Feb 1, 2023 · 8 comments

Comments

@awaken466
Copy link

Current version of MinGW Binutils is 2.26, latest is 2.37

@nikic
Copy link
Contributor

nikic commented Feb 1, 2023

Is this on current nightly (that is after #100178)?

@ChrisDenton
Copy link
Member

I'm seeing 2.38 in the latest builds (and mingw at 12.2.0).

@awaken466
Copy link
Author

I'm seeing 2.38 in the latest builds (and mingw at 12.2.0).

check your environment path, maybe there some other mingw, rust uses mingw from environment variable

@awaken466 awaken466 changed the title Update MinGW Binutils to the latest version Update MinGW Binutils to the latest version on Stable Feb 3, 2023
@ChrisDenton
Copy link
Member

I was speaking of nightly. On current stable and beta it's 2.27. I think it's unlikely that newer tools will be backported to stable unless there's a specific problem that makes it a priority.

@mati865
Copy link
Contributor

mati865 commented Feb 7, 2023

We shouldn't backport that upgrade, it's too risky.
The upgrade has broke raw-dylib in some cases #107752 and who knows what else.

@riverar
Copy link
Contributor

riverar commented Feb 8, 2023

@mati865 I don't think #107752 means much for this issue. The version of dlltool used in stable (2.26) uses a temporary prefix of getpid() (source) which isn't ideal given pid reuse is possible.

@jyn514
Copy link
Member

jyn514 commented Apr 8, 2023

#100178 landed in 1.69, which will be stable in 12 days. I feel pretty confident a stable backport isn't warranted given the risk and the fact 1.69 is releasing so soon.

@jyn514 jyn514 closed this as not planned Won't fix, can't repro, duplicate, stale Apr 8, 2023
@mati865
Copy link
Contributor

mati865 commented Apr 8, 2023

It's not exactly the latest version but it's fairly recent (2.38 IIRC).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants