public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112762] [14 Regression] Cannot build crosscompilers for some uclinux targets since r14-5791-g24592abd68e6ef
Date: Wed, 29 Nov 2023 18:03:35 +0000	[thread overview]
Message-ID: <bug-112762-4-uu6NQrPXVL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112762-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Part of the problem is *-uclinux is not matched in config.gcc where
linux-protos.h/linux.o gets added:
```
*-*-linux* | frv-*-*linux* | *-*-kfreebsd*-gnu | *-*-gnu* |
*-*-kopensolaris*-gnu | *-*-uclinuxfdpiceabi)
...
  # Linux C libraries selection switch: glibc / uclibc / bionic.
  # uclibc and bionic aren't usable for GNU/Hurd and neither for GNU/k*BSD.
  case $target in
    *linux*)
      tm_p_file="${tm_p_file} linux-protos.h"
      tmake_file="${tmake_file} t-linux"
      extra_objs="${extra_objs} linux.o"
      extra_options="${extra_options} linux.opt"
      ;;
  esac

```

As I mentioned there seems to be some misunderstanding what is the canonical
form for the triplet, or is both canonical (and different?) and just need fix
the usage for when uclinux is used and have them set tm_p_file/extra_objs
correctly, if they use linux.h .

  parent reply	other threads:[~2023-11-29 18:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 12:33 [Bug target/112762] New: Cannot build crosscompilers for some uclinux targets fkastl at suse dot cz
2023-11-29 17:46 ` [Bug target/112762] [14 Regression] Cannot build crosscompilers for some uclinux targets since r14-5791-g24592abd68e6ef pinskia at gcc dot gnu.org
2023-11-29 17:54 ` pinskia at gcc dot gnu.org
2023-11-29 17:58 ` mpolacek at gcc dot gnu.org
2023-11-29 18:03 ` pinskia at gcc dot gnu.org [this message]
2023-11-29 19:00 ` joseph at codesourcery dot com
2023-12-06 13:34 ` cvs-commit at gcc dot gnu.org
2023-12-06 13:37 ` mpolacek at gcc dot gnu.org
2023-12-06 13:37 ` mpolacek 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-112762-4-uu6NQrPXVL@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).