* glibc-2.33-r1.tbz2 MD5 SHA1 size ;-) ...Running pre-merge checks for sys-libs/glibc-2.33-r1
Failed to emerge sys-libs/glibc-2.33-r1, Log file:
Why is it checking the build environment for a binary package?
As it stands, I can't fix this problem.
I tried editing the ebuild (removing the __thread check) and rebuilding
the manifest but it still fails at the same place. I've double- and triple-checked it's the right ebuild but it's still running the checks!
Some assistance on installing glibc would be much appreciated!
On Tue, 7 Sep 2021 09:32:41 -0700, Daniel Frey wrote:
Why is it checking the build environment for a binary package?
I was wondering the same.
As it stands, I can't fix this problem.
I tried editing the ebuild (removing the __thread check) and rebuilding
the manifest but it still fails at the same place. I've double- and
triple-checked it's the right ebuild but it's still running the checks!
Some assistance on installing glibc would be much appreciated!
You can untar the binary package into /, which bypasses the checks. Then
you can emerge it so that portage knows where it stands.
The usual guarantees apply: if it breaks your system, you get to keep the pieces. I'd backup / first.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 292 |
Nodes: | 16 (2 / 14) |
Uptime: | 196:28:34 |
Calls: | 6,617 |
Calls today: | 1 |
Files: | 12,168 |
Messages: | 5,315,700 |