From: Bottom Post <stappers@stappers.nl>
To: crossgcc@sourceware.org
Subject: Re: Compiling for old system
Date: Fri, 28 May 2021 18:33:37 +0200 [thread overview]
Message-ID: <20210528163337.62ks3n5b66hr7hog@gpm.stappers.nl> (raw)
In-Reply-To: <CAFUUR5eOqKihqJB+pBhwEj4985xGHu_aEe-khHM=Lf_+U-p31g@mail.gmail.com>
On Fri, May 28, 2021 at 08:18:33AM -0700, Thomas Fuller wrote:
> On Thu, May 27, 2021, 2:04 PM Davide Viti wrote:
>
> > Hi,
> > I'm trying to create a toolchain targeting an old powerpc system running
> > kernel 2.6.18 and libc 2.5. The toolchain has to be used on a windows
> > machine.
> >
> > I've tried different combinations on Linux and ctng 1.5.2 fits all my
> > needs.
> > I've then tried to build the same on Windows, using cygwin, but compilation
> > fails at "Installing shared core C compiler" [1]
> > The config is available at [2]
> >
> > The compilation process on cygwin is extremely slow: I've managed to enable
> > the experimental feature and restart the build from the last failure, but
> > it still i very slow, especially if compared with Linux builds: I've tried
> > to do a canadian cross, but it's too much for my newbie skills: if anyone
> > would be willing to give me some advices, It'd be great to do that!
> >
> > thank you in advance
> >
> > Davide
> >
> > [1] https://pastebin.com/BBrFVt4e
> > [2] https://pastebin.com/jJmMzm9m
> > --
>
> Can you use WSL and use your working Linux build there?
>
And make it possible to read in the discussion order.
Reply below previous text.
Groeten
Geert Stappers
--
Silence is hard to parse
next prev parent reply other threads:[~2021-05-28 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 21:03 Davide Viti
2021-05-28 15:18 ` Thomas Fuller
2021-05-28 16:33 ` Bottom Post [this message]
2021-05-28 21:44 ` zinosat
2021-05-28 16:56 ` David Brown
2021-05-28 21:50 ` zinosat
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=20210528163337.62ks3n5b66hr7hog@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=crossgcc@sourceware.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).