-
Notifications
You must be signed in to change notification settings - Fork 559
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
[Glib] Upgrade to 2.74.0 #5539
[Glib] Upgrade to 2.74.0 #5539
Conversation
Glib >= 2.69.1 is required by the latest libsoup (3.2.0). |
The error on macOS is quite weird:
I'm not quite sure what's wrong with the |
Even more interesting, on my system I get a different error:
|
I have also encountered this error, too. |
It'd appear they check is the function Going back to the archive issue, the problem seems to be that sandbox:${WORKSPACE}/srcdir/glib-2.74.0/build_glib # file glib/libcharset/libcharset.a
glib/libcharset/libcharset.a: thin archive with 3 symbol entries and the linker can't deal with thin archives. Manually turning this, and all other, thin archives to regular archives with this code for lib in `find -name '*.a'`;
do ar -t $lib | xargs ar rvs $lib.new && mv -v $lib.new $lib;
done suggested at https://stackoverflow.com/a/25555282, I'm able to compile the code successfully (at least on aarch64-apple-darwin where I don't run into the |
That seems to be done pretty much on purpose: https://dev.azure.com/JuliaPackaging/Yggdrasil/_build/results?buildId=22651&view=logs&j=a3369a57-9e06-5de6-9b1e-d73561d89620&t=b24b196c-0a7e-51ab-830a-233ab8132a42&l=3042
|
G/Glib/build_tarballs.jl
Outdated
@@ -66,4 +67,4 @@ dependencies = [ | |||
] | |||
|
|||
# Build the tarballs, and possibly a `build.jl` as well. | |||
build_tarballs(ARGS, name, version, sources, script, platforms, products, dependencies; julia_compat="1.6") | |||
build_tarballs(ARGS, name, version, sources, script, platforms, products, dependencies; julia_compat="1.6", preferred_gcc_version = v"8") |
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.
Is GCC 8 really necessary? Anything older that would work?
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.
I could not remember exactly, only sure that 4 could not work.
Starting with 2.74 GLib can depend on libpcre2. Could also disable building tests using |
Ok, Glib build system is definitely cursed. Now lots of platforms which were successful before are now randomly failing.
I have the feeling that just restarting these jobs may work Edit: indeed that's what happened. Sigh.
Same error as what I was getting before locally ( |
The |
I hadn't looked at the code, but it looks like I was right: https://gitlab.gnome.org/GNOME/glib/-/issues/2766. Sigh. |
No description provided.