All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder for powerpc64le?
Date: Thu, 27 Oct 2016 09:56:07 +0200	[thread overview]
Message-ID: <20161027095607.4fdc7bc5@free-electrons.com> (raw)
In-Reply-To: <20161027035203.GA2558@tungsten.ozlabs.ibm.com>

Hello,

On Thu, 27 Oct 2016 14:52:03 +1100, Sam Bobroff wrote:

> > I'd say that both are useful, though (2) looks more interesting to me.  
> 
> At the moment, it's (2), although I might eventually try to get (1) going as
> well.

OK.

> >  (2) Requires adding some base toolchain configurations in
> >      https://git.buildroot.org/buildroot-test/tree/web/toolchains/configs/.
> >      One .config file per toolchain configuration, and each of them
> >      should be referenced in toolchain-configs.csv.  
> 
> OK! It's (2), so what do I need do next? Do I need to create the configs or
> provide you with some info? (If it's me, are there instructions somewhere?)

You clone the Git repository at
https://git.buildroot.org/buildroot-test/, add new .config files in
web/toolchains/configs/, and reference them in
web/toolchains/configs/toolchain-configs.csv, and then send patches on
the Buildroot mailing list, as usual.

> Oh, also, how are the pre-built toolchains managed? I notice that some of the
> configs use them and some don't. Can we create ones for the new targets?

Yes, we can. In this case, just provide me the base Buildroot
configuration for those targets, and I'll build the toolchains
accordingly.

Do you want just powerpc64/glibc and powerpc64el/glibc, or are there
other interesting C libraries supporting powerpc64 that we should test ?

> > Also, if you're interested in powerpc64 and powerpc64le and we indeed
> > add toolchain configurations in the autobuilders, it would be nice if
> > you could add:
> > 
> > N:	Sam Bobroff <sam.bobroff@au1.ibm.com>
> > F:	arch/Config.in.powerpc
> > 
> > to the DEVELOPERS file. This way, you will receive a daily e-mail with
> > the failures that occurred on powerpc, powerpc64 and powerpc64le (i.e
> > all BR2_ARCH values described in arch/Config.in.powerpc).  
> 
> I can only help with powerpc64 and powerpc64le, if that's OK then I'm happy to
> add myself. I can probably find someone else around here to put their hand up
> too. Should I just send a buildroot patch with the change?

We currently don't have a way of expressing interest only for powerpc64
but not powerpc. Is it fine if you get both results?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-10-27  7:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26  5:15 [Buildroot] Autobuilder for powerpc64le? Sam Bobroff
2016-10-26  7:12 ` Thomas Petazzoni
2016-10-27  3:52   ` Sam Bobroff
2016-10-27  7:56     ` Thomas Petazzoni [this message]
2016-11-01  4:52       ` Sam Bobroff

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=20161027095607.4fdc7bc5@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.