linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	Paul Moore <paul@paul-moore.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Richard Guy Briggs <rgb@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: manual merge of the audit tree with the powerpc tree
Date: Tue, 14 Dec 2021 21:30:12 +0100	[thread overview]
Message-ID: <102e59ba-fcf0-dd85-9338-75b7ce5fbd83@kaod.org> (raw)
In-Reply-To: <1a78709f-162e-0d78-0550-4e9ef213f9c6@csgroup.eu>

On 12/14/21 20:32, Christophe Leroy wrote:
> 
> 
> Le 14/12/2021 à 19:23, Paul Moore a écrit :
>> On Tue, Dec 14, 2021 at 12:59 PM Christophe Leroy
>> <christophe.leroy@csgroup.eu> wrote:
>>> Hello Paul,
>>>
>>> I've been trying to setup your test suite on my powerpc board but it's
>>> based on Perl and on a lot of optional Perl packages. I was able to add
>>> them one by one until some of them require some .so libraries
>>> (Pathtools-Cwd), and it seems nothing is made to allow cross building
>>> those libraries.
>>>
>>> Do you have another test suite based on C and not perl ?
>>>
>>> If not, what can I do, do you know how I can cross compile those Perl
>>> packages for PPC32 ?
>>
>> Is there no Linux distribution that supports PPC32?  I would think
>> that would be the easiest path forward, but you're the PPC32 expert -
>> not me - so I'll assume you already tried that or it didn't work for
>> other reasons.
> 
> There hasn't been Linux distribution supporting PPC32 for a few years
> now. And regardless, the boards I'm running Linux on are home made
> embedded boards, with limited amount of memory and flashdisk space and
> no video chip, so they are hardly supported by any distributions, even
> older ones.

We still have debian. you will find images under :

   https://cdimage.debian.org/cdimage/ports/snapshots/2021-04-17/

and from there, you can update to unstable, which runs fine under
a mac99 QEMU machine.

Cheers,

C.

  reply	other threads:[~2021-12-14 20:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  2:31 linux-next: manual merge of the audit tree with the powerpc tree Stephen Rothwell
2021-10-26 10:55 ` Michael Ellerman
2021-10-26 14:27   ` Paul Moore
2021-10-27 11:29     ` Michael Ellerman
2021-10-27 11:41       ` Christophe Leroy
2021-10-27 14:18         ` Paul Moore
2021-12-14 17:59           ` Christophe Leroy
2021-12-14 18:23             ` Paul Moore
2021-12-14 19:32               ` Christophe Leroy
2021-12-14 20:30                 ` Cédric Le Goater [this message]
2021-12-16  9:08                   ` Christophe Leroy
2021-12-16 23:04                     ` Paul Moore
2021-12-17 14:11                       ` Christophe Leroy
2022-01-12 17:19                         ` Paul Moore

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=102e59ba-fcf0-dd85-9338-75b7ce5fbd83@kaod.org \
    --to=clg@kaod.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paul@paul-moore.com \
    --cc=rgb@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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 NNTP newsgroup(s).