From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Mikael Pettersson <mikpelinux@gmail.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] add glibc-stdint.h to vax and lm32 linux target (PR target/105525)
Date: Mon, 22 May 2023 14:10:48 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2305210111390.27887@angie.orcam.me.uk> (raw)
In-Reply-To: <CAM43=SNxCVJF9YPoK2UV0y37bPtLFzbFxiHq4RDaH_5PRRMoiQ@mail.gmail.com>
On Fri, 19 May 2023, Mikael Pettersson wrote:
> > Hmm, I find it quite insteresting and indeed encouraging that someone
> > actually verifies our VAX/Linux target.
> >
> > Mikael, how do you actually verify it however?
>
> My vax builds are only cross-compilers without kernel headers or libc.
Hmm, interesting, I wasn't aware you could actually build stage 1 GCC
without target headers nowadays.
When I tried it previously, it failed, and I had to come up with a hack
to make glibc's `make install-headers' work, as ordinarily it requires a
target compiler, making it a chicken-and-egg problem.
> The background is that I maintain a script to build GCC-based crosses to
> as many targets as I can, currently it supports 78 distinct processors and
> 82 triplets (four processors have multiple triplets). I only check that I can
> build the toolchains (full linux-gnu ones where possible).
Great work, thanks!
Maciej
next prev parent reply other threads:[~2023-05-22 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 17:45 Mikael Pettersson
2023-04-29 16:58 ` Jeff Law
2023-05-19 12:06 ` Maciej W. Rozycki
2023-05-19 13:59 ` Mikael Pettersson
2023-05-22 13:10 ` Maciej W. Rozycki [this message]
2023-05-22 13:57 ` Jan-Benedict Glaw
2023-05-22 15:25 ` Mikael Pettersson
2023-05-22 16:00 ` Jan-Benedict Glaw
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=alpine.DEB.2.21.2305210111390.27887@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
--cc=jeffreyalaw@gmail.com \
--cc=mikpelinux@gmail.com \
/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).