From: Frederic Berat <fberat@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: "Frédéric Bérat via Libc-alpha" <libc-alpha@sourceware.org>,
siddhesh@gotplt.org
Subject: Re: [PATCH v6 00/14] Allow glibc to be built with _FORTIFY_SOURCE
Date: Wed, 12 Jul 2023 15:35:53 +0200 [thread overview]
Message-ID: <CAObJKZqn3A5LTq9Y612pPa2PCyDqVLyi=eoJy4GXf1cw5ZJQcQ@mail.gmail.com> (raw)
In-Reply-To: <mvmjzv6hm6f.fsf@suse.de>
[-- Attachment #1: Type: text/plain, Size: 2172 bytes --]
On Tue, Jul 11, 2023 at 10:44 AM Andreas Schwab <schwab@suse.de> wrote:
>
> https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc/glibc:i686/f/i586
>
> make[2]: Entering directory
> '/home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/support'
> gcc -o
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/support/test-run-command
> -nostdlib -nostartfiles -static -static-pie -Wl,-z,pack-relative-relocs
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/csu/rcrt1.o
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/csu/crti.o
> `gcc --print-file-name=crtbeginS.o`
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/support/test-run-command.o
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/elf/static-stubs.o
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/support/libsupport_nonshared.a
> -Wl,-z,now -Wl,--start-group
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/libc.a
> -lgcc -Wl,--end-group `gcc --print-file-name=crtendS.o`
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/csu/crtn.o
> /usr/lib/gcc/i586-suse-linux/13/../../../../i586-suse-linux/bin/ld:
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/libc.a(memset_chk-nonshared.o):
> unsupported non-PIC call to IFUNC `memset'
> /usr/lib/gcc/i586-suse-linux/13/../../../../i586-suse-linux/bin/ld: failed
> to set dynamic section sizes: bad value
> collect2: error: ld returned 1 exit status
> make[2]: *** [../Rules:290:
> /home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/cc-base/support/test-run-command]
> Error 1
> make[2]: Leaving directory
> '/home/abuild/rpmbuild/BUILD/glibc-2.37.9000.604.g7f079fdc16/support'
>
>
This one will take a bit more time to analyze, I finally succeeded to
reproduce it at least and I'm trying to figure out what's going on.
--
> Andreas Schwab, SUSE Labs, schwab@suse.de
> GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
> "And now for something completely different."
>
>
next prev parent reply other threads:[~2023-07-12 13:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 14:38 Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 01/14] " Frédéric Bérat
2023-07-05 14:41 ` Siddhesh Poyarekar
2023-07-05 14:38 ` [PATCH v6 02/14] Exclude routines from fortification Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 03/14] sysdeps: Ensure ieee128*_chk routines to be properly named Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 04/14] string: Ensure *_chk routines have their hidden builtin definition available Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 05/14] stdio: " Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 06/14] misc/sys/cdefs.h: Create FORTIFY redirects for internal calls Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 07/14] wchar: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 08/14] posix/bits/unistd.h: Clearly separate declaration from definitions Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 09/14] unistd: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 10/14] misc/bits/select2.h: Clearly separate declaration from definitions Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 11/14] misc/bits/syslog.h: Clearly separate declaration from definition Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 12/14] libio/bits/stdio2.h: Clearly separate declaration from definitions Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 13/14] libio/bits/stdio2-decl.h: Avoid PLT entries with _FORTIFY_SOURCE Frédéric Bérat
2023-07-05 14:38 ` [PATCH v6 14/14] sysdeps/ieee754/ldbl-128ibm-compat: Fix warn unused result Frédéric Bérat
2023-07-06 13:15 ` [PATCH v6 00/14] Allow glibc to be built with _FORTIFY_SOURCE Andreas Schwab
2023-07-06 13:41 ` Frederic Berat
2023-07-06 13:46 ` Andreas Schwab
2023-07-10 5:57 ` Frederic Berat
2023-07-06 13:38 ` Andreas Schwab
2023-07-10 5:56 ` Frederic Berat
2023-07-11 8:44 ` Andreas Schwab
2023-07-12 13:35 ` Frederic Berat [this message]
2023-07-12 13:38 ` Andreas Schwab
2023-07-12 13:42 ` Frederic Berat
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='CAObJKZqn3A5LTq9Y612pPa2PCyDqVLyi=eoJy4GXf1cw5ZJQcQ@mail.gmail.com' \
--to=fberat@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
--cc=siddhesh@gotplt.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 read-only IMAP folder(s) and NNTP newsgroup(s).