-
Notifications
You must be signed in to change notification settings - Fork 657
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
Segfault reported during build of the zstd library #2135
Comments
I'm on 14.4, but I'm testing now with the latest in git. |
line 392 is just a |
That comes from line 329. It's being ran in a "sub-shell" |
Huh, I actually run into another build issue with gcc :| |
|
@bhundven, I have not seen this issue yet. Is this part of the build done with |
I ran effectively the same command that ends-up being run in the sub-shell and could not trigger the segfault. I would repeatedly clean the directory, build again and no issues. |
maybe a bash segfault? I read that that can happen |
I am trying to build your config on a |
worked for me |
Perhaps it is bash. I will investigate further later today. Thanks for all
the effort!
…On Sat, Mar 23, 2024, 6:41 AM Quentin Boswank ***@***.***> wrote:
worked for me
—
Reply to this email directly, view it on GitHub
<#2135 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB44UA6O6HD4F4BEIIPTK3YZWBBRAVCNFSM6AAAAABFD4MX66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWGQ4TQOBUGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I am starting to doubt that it is bash, because I just updated bash via If I have more information about this I will be sure to update the case. |
@szaydel Did you ever get this working? I am running into a similar issue. |
I have not. Unfortunately, I have been rather short on time lately. I am
planning on coming back to this issue soon though and will report progress,
if any, here.
…On Tue, Apr 23, 2024 at 8:01 PM Caleb Yates ***@***.***> wrote:
@szaydel <https://github.com/szaydel> Did you ever get this working? I am
running into a similar issue.
—
Reply to this email directly, view it on GitHub
<#2135 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB44UB7A52YPHPUAYDOH3LY64N7ZAVCNFSM6AAAAABFD4MX66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZTHEYTQNRRGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I have finally been able to make some time for this and instead of doing the same exact thing and expecting different results I chose to build a different toolchain. This is the configuration which I built:
And, surprisingly I was able to successfully complete the build. This leaves me wondering what it is about the particular choices that I made previously that caused the build to fail whereas today with a different configuration I was able to build. I am going to try building a few different toolchains to see if this issue returns. |
My build system is a Macbook Pro M1, running Mac OS Sonoma 14.2.1. I continue to see the following failure, no matter the number of jobs I set. I confirmed that even setting
-j1
does not improve the situation. With some hacking around I was able to run the command that gets executed manually and I see that azstd.a
is generated and command returns without any segfaults.Version: 1.26.0
OS: MacOS Sonoma 14.2.1 (23C71)
config.txt
build.log
The text was updated successfully, but these errors were encountered: