public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Mikael Pettersson <mikpelinux@gmail.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
	gcc-patches@gcc.gnu.org, "Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: Re: [PATCH] add glibc-stdint.h to vax and lm32 linux target (PR target/105525)
Date: Mon, 22 May 2023 18:00:10 +0200	[thread overview]
Message-ID: <20230522160010.ukaw5xwhxgql5gre@lug-owl.de> (raw)
In-Reply-To: <CAM43=SPeSKACeu+GwBrM2nAdfyP4_Kt05OB2xOpNGquWvbnLLg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]

Hi Mikael!

On Mon, 2023-05-22 17:25:39 +0200, Mikael Pettersson <mikpelinux@gmail.com> wrote:
> On Mon, May 22, 2023 at 3:57 PM Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> > On Mon, 2023-05-22 14:10:48 +0100, Maciej W. Rozycki <macro@orcam.me.uk> wrote:
> > > On Fri, 19 May 2023, Mikael Pettersson wrote:
> > > > 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!
> >
> > I'd be very much interested in running your script as one build
> > variant for my http://toolchain.lug-owl.de/ efforts. Is it available
> > somewhere? That would be nice!
> 
> The script is publicly available as https://github.com/mikpe/buildcross.git.
> Usage for actively maintained toolchains is pretty easy. For example, to build
> a cross to sparc64-unknown-linux-gnu you just run
> 
>     buildcross -jN sparc64
> 
> and it will leave the toolchain in cross-sparc64. (Other bits will
> land in downloads/,
> sources/, and host-tools/.)

Thanks, I'll have a look!

> If you're only interested in linux-gnu toolchains for actively
> maintained targets there's
> a build-many-glibcs.py script in glibc that should be a better fit.

My intention is to gain access to as many targets and different
configurations and build strategies as possible. glibc's script is
already included. (As I build with all languages, most of the target
configurations fail right now.)

Thanks!

Jan-Benedict
-- 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2023-05-22 16:00 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
2023-05-22 13:57         ` Jan-Benedict Glaw
2023-05-22 15:25           ` Mikael Pettersson
2023-05-22 16:00             ` Jan-Benedict Glaw [this message]

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=20230522160010.ukaw5xwhxgql5gre@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=macro@orcam.me.uk \
    --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).