Chrome OS 72 has glibc 2.27

Question

Chrome OS 72 has glibc 2.27

bsiegert opened this issue 6 years ago · comments

Description

I am on dev channel. The glibc package (installed from binary, as part of the default install) contains dangling symlinks to system libs, because Chrome OS itself is now on glibc 2.27. Compiling anything thus fails with

$ gcc -o foo foo.c
/usr/local/bin/ld: cannot find /usr/local/lib64/libc.so.6
/usr/local/bin/ld: cannot find /usr/local/lib64/ld-linux-x86-64.so.2
collect2: error: ld returned 1 exit status
$ ls -l /usr/local/lib64/libc.so.6
lrwxrwxrwx. 1 chronos chronos 12 Jun 25 02:32 /usr/local/lib64/libc.so.6 -> libc-2.23.so
$ ls -l /usr/local/lib64/libc-2.23.so
lrwxrwxrwx. 1 chronos chronos 19 Jun 25 02:32 /usr/local/lib64/libc-2.23.so -> /lib64/libc-2.23.so
$ ls /lib64/libc-*.so
/lib64/libc-2.27.so

Maybe it is in fat time to use glibc 2.27, as suggested in #2885?

Versions and system information

glibc version 2.23

chromebrew: 1.0.4

ChromeOS:

CHROMEOS_RELEASE_BUILDER_PATH=caroline-release/R72-11264.0.0          
CHROMEOS_RELEASE_BUILD_NUMBER=11264                                   
CHROMEOS_RELEASE_BUILD_TYPE=Official Build                            
CHROMEOS_RELEASE_CHROME_MILESTONE=72                                  
CHROMEOS_RELEASE_DESCRIPTION=11264.0.0 (Official Build) dev-channel caroline

Model: Samsung Chromebook Pro

Architecture: x86_64

Ed Reel · Answer 1 · Fri Nov 23 2018 22:16:00 GMT+0800 (China Standard Time)

Thank you for the heads up @bsiegert. We will cross this bridge once 72 becomes the stable release.

JL2210 · Answer 2 · Tue Nov 27 2018 00:08:39 GMT+0800 (China Standard Time)

This is great! After we make this update, the cross script can finally be perfected and will work!

JL2210 · Answer 3 · Wed Nov 28 2018 00:11:01 GMT+0800 (China Standard Time)

I tried this before, back when glibc 2.23 gave segfaults. It didn't work. However, if this is the new system
C library, it most likely will.

Mack · Answer 4 · Wed Dec 05 2018 07:31:08 GMT+0800 (China Standard Time)

can I use your cross script?

Benny Siegert · Answer 5 · Wed Dec 05 2018 17:24:33 GMT+0800 (China Standard Time)

In the meantime: Is there a way I could rebuild glibc-2.23 from source (thus, without the symlinks) but not remove the installed glibc package before?

JL2210 · Answer 6 · Thu Dec 06 2018 23:56:09 GMT+0800 (China Standard Time)

@sajjaadf Doesn't work yet. @bsiegert wget https://ftp.gnu.org/gnu/libc/glibc-2.27.tar.xz
NOT SUPPORTED!

Mack · Answer 7 · Fri Dec 07 2018 04:22:08 GMT+0800 (China Standard Time)

When it works can I use it? [image: Picture] Sajjaad Farzad About Me <https://about.me/sajjaadf?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb>

…

On Thu, Dec 6, 2018 at 7:57 AM James Larrowe ***@***.***> wrote: @sajjaadf <https://github.com/sajjaadf> Doesn't work yet. @bsiegert <https://github.com/bsiegert> wget https://ftp.gnu.org/gnu/libc/glibc-2.27.tar.xz NOT SUPPORTED! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2890 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ael7o5mBFiWKc7WJArIlZIpypiLUi1d1ks5u2T5bgaJpZM4YwYJB> .

JL2210 · Answer 8 · Fri Dec 07 2018 21:09:29 GMT+0800 (China Standard Time)

@sajjaadf @bsiegert If you intend to do anything with Chromebrew, you need to revert to the stable channel. The stable channel is the only supported channel.

Martin Krastev · Answer 9 · Sun Jan 13 2019 00:20:03 GMT+0800 (China Standard Time)

Just a heads-up: r72 has landed on the beta channel, bringing along the same problem.

In the meantime, a workaround allowing the use of crew's current gcc7 and clang packages on r72:

fix all links under /usr/local/lib that originally point to /lib/*-2.23 versions to point to /lib/*-2.27 versions
when building via gcc or clang, pass /lib/ld-2.27.so as a link dependency

Ed Reel · Answer 10 · Sun Jan 13 2019 00:22:32 GMT+0800 (China Standard Time)

@blu: Thanks for the heads-up. We have that issue addressed. @skiman6010 has confirmed the problem is resolved after a glibc 2.27 update.

JL2210 · Answer 11 · Sun Jan 13 2019 01:59:00 GMT+0800 (China Standard Time)

Sorry about that. I was on my email, and didn't see the edit you made.

JL2210 · Answer 12 · Sun Jan 13 2019 02:00:38 GMT+0800 (China Standard Time)

@blu Check the update-glibc-2.23-2.27 branch on @uberhacker's fork of Chromebrew.
How's Wayland development going?

Martin Krastev · Answer 13 · Sun Jan 13 2019 04:01:11 GMT+0800 (China Standard Time)

@JL2210 Thanks, will do! Wayland's on the backburner ATM, hopefully I'll kick back into it full swing in a couple of weeks.

Neale Pickett · Answer 14 · Mon Feb 18 2019 10:48:08 GMT+0800 (China Standard Time)

Chrome 72 is now stable: I'm on the stable channel and just hit a bunch of dangling symlinks.

Martin Krastev · Answer 15 · Wed Feb 20 2019 16:59:57 GMT+0800 (China Standard Time)

Chrome 72 is now stable: I'm on the stable channel and just hit a bunch of dangling symlinks.

This is normal for r72 and current crew. It can be addressed as described here: #2890 (comment)

Neale Pickett · Answer 16 · Wed Feb 20 2019 23:26:30 GMT+0800 (China Standard Time)

Thank you. This comment prompted me to update the issue:

We will cross this bridge once 72 becomes the stable release.

It is now time to cross the bridge.

Neale Pickett · Answer 17 · Fri Mar 01 2019 00:52:34 GMT+0800 (China Standard Time)

This issue appears to have been resolved recently. I can't close the issue but that may be appropriate.