public inbox for
 help / color / mirror / Atom feed
From: David Brown <>
To: Davide Viti <>,
Subject: Re: Compiling for old system
Date: Fri, 28 May 2021 18:56:47 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 27/05/2021 23:03, Davide Viti via crossgcc 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]
> [2]

As an alternative to Cygwin, you could try msys2 / mingw-64.  My
experience is that this can often be a lot faster than Cygwin, and
creates stand-alone programs that feel less "alien" in Windows.
However, it has limitations if you need more accurate POSIX emulation,
such as for fork() calls.  It's worth trying.

You could also install VirtualBox and run the Linux system within a
virtual machine, on the Windows host, if you can't escape from using
Windows on the actual PC.

  parent reply	other threads:[~2021-05-28 16:56 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
2021-05-28 21:44     ` zinosat
2021-05-28 16:56 ` David Brown [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).