From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] xbps-src: glibc fails to build for x86_64
Date: Wed, 21 Dec 2022 14:58:26 +0100 [thread overview]
Message-ID: <20221221135826.8umsafolQEtipyyru2crCRZw0ByhgHpojU7BXyTuEr0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41216@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 4449 bytes --]
Closed issue by unspecd on void-packages repository
https://github.com/void-linux/void-packages/issues/41216
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.0_1 x86_64-musl GenuineIntel uptodate FF
### Package(s) Affected
glibc-2.36_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Package builds with `./xbps-src -a x86_64 pkg base-chroot`.
### Actual behaviour
```
$ ./xbps-src -a x86_64 pkg base-chroot
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> base-chroot-0.67_1: building [meta] for x86_64...
[skip]
=> glibc-2.36_1: building (dependency of base-chroot) for x86_64...
[skip]
=> glibc-2.36_1: running do_build ...
...
x86_64-linux-gnu-gcc -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -L/usr/x86_64-linux-gnu/usr/lib -shared -static-libgcc -Wl,-O1 -Wl,-z,defs -Wl,-dynamic-linker=/usr/lib64/ld-linux-x86-64.so.2 -Wl,-z,pack-relative-relocs -B/builddir/glibc-2.36/build/csu/ -Wl,--version-script=/builddir/glibc-2.36/build/libc.map -Wl,-soname=libc.so.6 -Wl,-z,relro -Wl,--hash-style=both -Wl,-z,now -nostdlib -nostartfiles -e __libc_main -L/builddir/glibc-2.36/build -L/builddir/glibc-2.36/build/math -L/builddir/glibc-2.36/build/elf -L/builddir/glibc-2.36/build/dlfcn -L/builddir/glibc-2.36/build/nss -L/builddir/glibc-2.36/build/nis -L/builddir/glibc-2.36/build/rt -L/builddir/glibc-2.36/build/resolv -L/builddir/glibc-2.36/build/mathvec -L/builddir/glibc-2.36/build/support -L/builddir/glibc-2.36/build/crypt -L/builddir/glibc-2.36/build/nptl -Wl,-rpath-link=/builddir/glibc-2.36/build:/builddir/glibc-2.36/build/math:/builddir/glibc-2.36/build/elf:/builddir/glibc-2.36/build/dlfcn:/builddir/glibc-2.36/build/nss:/builddir/glibc-2.36/build/nis:/builddir/glibc-2.36/build/rt:/builddir/glibc-2.36/build/resolv:/builddir/glibc-2.36/build/mathvec:/builddir/glibc-2.36/build/support:/builddir/glibc-2.36/build/crypt:/builddir/glibc-2.36/build/nptl -o /builddir/glibc-2.36/build/libc.so -T /builddir/glibc-2.36/build/shlib.lds /builddir/glibc-2.36/build/csu/abi-note.o /builddir/glibc-2.36/build/libc_pic.os /builddir/glibc-2.36/build/elf/interp.os /builddir/glibc-2.36/build/elf/ld.so -lgcc /builddir/glibc-2.36/build/elf/sofini.os
/bin/sh ../scripts/rellns-sh /builddir/glibc-2.36/build/elf/ld.so /builddir/glibc-2.36/build/elf/ld-linux-x86-64.so.2.new
mv -f /builddir/glibc-2.36/build/elf/ld-linux-x86-64.so.2.new /builddir/glibc-2.36/build/elf/ld-linux-x86-64.so.2
/usr/lib/gcc/x86_64-linux-gnu/12.2.0/../../../../x86_64-linux-gnu/bin/ld: /builddir/glibc-2.36/build/libc_pic.os: in function `__libc_start_call_main':
./csu/../sysdeps/nptl/libc_start_call_main.h:29: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/x86_64-linux-gnu/12.2.0/../../../../x86_64-linux-gnu/bin/ld: /builddir/glibc-2.36/build/libc_pic.os: in function `iconv_open':
./iconv/iconv_open.c:32: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/x86_64-linux-gnu/12.2.0/../../../../x86_64-linux-gnu/bin/ld: /builddir/glibc-2.36/build/libc_pic.os: in function `iconv':
./iconv/iconv.c:32: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/x86_64-linux-gnu/12.2.0/../../../../x86_64-linux-gnu/bin/ld: ./iconv/iconv.c:94: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/x86_64-linux-gnu/12.2.0/../../../../x86_64-linux-gnu/bin/ld: /builddir/glibc-2.36/build/libc_pic.os: in function `__GI___gconv_open':
./iconv/gconv_open.c:35: undefined reference to `__stack_chk_guard'
/usr/lib/gcc/x86_64-linux-gnu/12.2.0/../../../../x86_64-linux-gnu/bin/ld: /builddir/glibc-2.36/build/libc_pic.os:./iconv/gconv_open.c:171: more undefined references to `__stack_chk_guard' follow
collect2: error: ld returned 1 exit status
make[2]: *** [../Makerules:690: /builddir/glibc-2.36/build/libc.so] Error 1
make[2]: Leaving directory '/builddir/glibc-2.36/elf'
make[1]: *** [Makefile:484: elf/subdir_lib] Error 2
make[1]: Leaving directory '/builddir/glibc-2.36'
make: *** [Makefile:9: all] Error 2
=> ERROR: glibc-2.36_1: do_build: 'make ${makejobs}' exited with 2
=> ERROR: in do_build() at srcpkgs/glibc/template:121
```
### Steps to reproduce
```
$ git clone https://github.com/void-linux/void-packages && cd void-packages
$ git rev-parse HEAD
a1d55dba6a29d765d107746c0acc9fd0eb46aa88
$ ./xbps-src binary-bootstrap
$ ./xbps-src -a x86_64 base-chroot
```
next prev parent reply other threads:[~2022-12-21 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 11:34 [ISSUE] " unspecd
2022-12-21 12:29 ` paper42
2022-12-21 12:41 ` unspecd
2022-12-21 12:42 ` classabbyamp
2022-12-21 12:44 ` classabbyamp
2022-12-21 13:28 ` unspecd
2022-12-21 13:29 ` classabbyamp
2022-12-21 13:40 ` paper42
2022-12-21 13:55 ` unspecd
2022-12-21 13:58 ` paper42 [this message]
2022-12-21 13:58 ` paper42
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=20221221135826.8umsafolQEtipyyru2crCRZw0ByhgHpojU7BXyTuEr0@z \
--to=paper42@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).