From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] glibc: ftbfs for ppcle
Date: Sat, 27 Feb 2021 23:58:11 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29106@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3850 bytes --]
New issue by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/29106
Description:
Currently glibc cannot be built for ppcle. When trying to link `libc.so` the error is:
```
powerpcle-linux-gnu-gcc -no-pie -Wl,--as-needed -L/usr/powerpcle-linux-gnu/usr/lib -shared -static-libgcc -Wl,-O1 -mhard-float -Wl,-z,defs -Wl,-dynamic-linker=/usr/lib32/ld.so.1 -B/builddir/glibc-2.32/build/csu/ -Wl,--version-script=/builddir/glibc-2.32/build/libc.map -Wl,-soname=libc.so.6 -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both -Wl,-z,now -nostdlib -nostartfiles -e __libc_main -L/builddir/glibc-2.32/build -L/builddir/glibc-2.32/build/math -L/builddir/glibc-2.32/build/elf -L/builddir/glibc-2.32/build/dlfcn -L/builddir/glibc-2.32/build/nss -L/builddir/glibc-2.32/build/nis -L/builddir/glibc-2.32/build/rt -L/builddir/glibc-2.32/build/resolv -L/builddir/glibc-2.32/build/mathvec -L/builddir/glibc-2.32/build/support -L/builddir/glibc-2.32/build/crypt -L/builddir/glibc-2.32/build/nptl -Wl,-rpath-link=/builddir/glibc-2.32/build:/builddir/glibc-2.32/build/math:/builddir/glibc-2.32/build/elf:/builddir/glibc-2.32/build/dlfcn:/builddir/glibc-2.32/build/nss:/builddir/glibc-2.32/build/nis:/builddir/glibc-2.32/build/rt:/builddir/glibc-2.32/build/resolv:/builddir/glibc-2.32/build/mathvec:/builddir/glibc-2.32/build/support:/builddir/glibc-2.32/build/crypt:/builddir/glibc-2.32/build/nptl -o /builddir/glibc-2.32/build/libc.so /builddir/glibc-2.32/build/csu/abi-note.o /builddir/glibc-2.32/build/libc_pic.os.clean /builddir/glibc-2.32/build/elf/interp.os /builddir/glibc-2.32/build/elf/ld.so -lgcc /builddir/glibc-2.32/build/elf/sofini.os
/bin/sh ../scripts/rellns-sh /builddir/glibc-2.32/build/elf/ld.so /builddir/glibc-2.32/build/elf/ld.so.1.new
mv -f /builddir/glibc-2.32/build/elf/ld.so.1.new /builddir/glibc-2.32/build/elf/ld.so.1
/usr/lib/gcc/powerpcle-linux-gnu/10.2.1/../../../../powerpcle-linux-gnu/bin/ld: /builddir/glibc-2.32/build/libc_pic.os.clean: in function `iconv_open':
/builddir/glibc-2.32/iconv/iconv_open.c:33: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/powerpcle-linux-gnu/10.2.1/../../../../powerpcle-linux-gnu/bin/ld: /builddir/glibc-2.32/build/libc_pic.os.clean: in function `iconv':
/builddir/glibc-2.32/iconv/iconv.c:33: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/powerpcle-linux-gnu/10.2.1/../../../../powerpcle-linux-gnu/bin/ld: /builddir/glibc-2.32/build/libc_pic.os.clean: in function `__GI___gconv_open':
/builddir/glibc-2.32/iconv/gconv_open.c:36: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/powerpcle-linux-gnu/10.2.1/../../../../powerpcle-linux-gnu/bin/ld: /builddir/glibc-2.32/build/libc_pic.os.clean: in function `find_derivation':
/builddir/glibc-2.32/iconv/gconv_db.c:431: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/powerpcle-linux-gnu/10.2.1/../../../../powerpcle-linux-gnu/bin/ld: /builddir/glibc-2.32/build/libc_pic.os.clean: in function `__gconv_compare_alias':
/builddir/glibc-2.32/iconv/gconv_db.c:704: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/powerpcle-linux-gnu/10.2.1/../../../../powerpcle-linux-gnu/bin/ld: /builddir/glibc-2.32/build/libc_pic.os.clean:/builddir/glibc-2.32/iconv/gconv_db.c:722: more undefined references to `__stack_chk_guard' follow
collect2: error: ld returned 1 exit status
make[2]: *** [../Makerules:698: /builddir/glibc-2.32/build/libc.so] Error 1
make[2]: Leaving directory '/builddir/glibc-2.32/elf'
make[1]: *** [Makefile:470: elf/subdir_lib] Error 2
make[1]: Leaving directory '/builddir/glibc-2.32'
make: *** [Makefile:9: all] Error 2
=> ERROR: glibc-2.32_1: do_build: 'make ${makejobs}' exited with 2
=> ERROR: in do_build() at srcpkgs/glibc/template:122
```
It used to build a couple of weeks ago. Last build here was on 2021-01-18 01:10 CET.
next reply other threads:[~2021-02-27 22:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 22:58 pullmoll [this message]
2021-02-27 23:32 ` pullmoll
2021-02-27 23:58 ` q66
2021-02-28 1:00 ` pullmoll
2021-02-28 1:23 ` pullmoll
2021-02-28 1:43 ` pullmoll
2021-02-28 1:45 ` pullmoll
2021-02-28 2:13 ` pullmoll
2021-02-28 2:16 ` pullmoll
2021-04-28 12:14 ` [ISSUE] [CLOSED] " ericonr
2021-04-28 12:14 ` ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29106@inbox.vuxu.org \
--to=pullmoll@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).