public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yann at sionneau dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98784] [9/10/11/12 Regression] problematic build of uClibc with -fPIC
Date: Mon, 28 Jun 2021 16:50:07 +0000	[thread overview]
Message-ID: <bug-98784-4-KZRBCY9dRq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98784-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784

--- Comment #14 from YannSionneau <yann at sionneau dot net> ---
Created attachment 51074
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51074&action=edit
non-working uClibc-ng build

This is a build of uClibc-ng that does not allow normal Linux booting.
You can boot to a shell by doing init=/bin/sh but any command you type (like
ls) would run the command and then crash the system because init (in fact the
shell, the parent of the forked command) gets killed.

This might be related to issue in signal handling since the parent is supposed
to receive a SIGCHILD signal when its child exits.

Difference with previous attachment is just that the follow buildroot patch is
not applied to gcc:
https://git.buildroot.net/buildroot/commit/?id=4d16e6f5324f0285f51bfbb5a3503584f3b3ad12

  parent reply	other threads:[~2021-06-28 16:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 22:13 [Bug c/98784] New: [gcc 8.4/9.3/10] sparcv8 regression romain.naour at gmail dot com
2021-01-21 23:01 ` [Bug c/98784] " ebotcazou at gcc dot gnu.org
2021-01-21 23:26 ` romain.naour at gmail dot com
2021-01-21 23:43 ` ebotcazou at gcc dot gnu.org
2021-01-22  7:33 ` [Bug target/98784] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2021-01-23 11:43 ` romain.naour at gmail dot com
2021-01-23 17:33 ` ebotcazou at gcc dot gnu.org
2021-01-23 20:07 ` romain.naour at gmail dot com
2021-01-23 21:56 ` [Bug target/98784] [8/9/10/11 Regression] problematic build of uClibc with -fPIC ebotcazou at gcc dot gnu.org
2021-01-24  9:17 ` ebotcazou at gcc dot gnu.org
2021-01-26 21:24 ` romain.naour at gmail dot com
2021-01-26 22:29 ` romain.naour at gmail dot com
2021-04-09  8:08 ` rguenth at gcc dot gnu.org
2021-05-14  9:54 ` [Bug target/98784] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:19 ` rguenth at gcc dot gnu.org
2021-06-28 16:40 ` yann at sionneau dot net
2021-06-28 16:50 ` yann at sionneau dot net [this message]
2022-05-27  9:44 ` [Bug target/98784] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07 10:38 ` [Bug target/98784] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-08-08  9:51 ` wbx at openadk dot org
2024-04-30 15:05 ` [Bug target/98784] [11/12/13/14/15 " dm.chestnykh at gmail dot com
2024-04-30 17:55 ` dm.chestnykh at gmail dot com
2024-04-30 17:59 ` pinskia at gcc dot gnu.org

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=bug-98784-4-KZRBCY9dRq@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).