From: Jean-Marie Lemetayer <jeanmarie.lemetayer@gmail.com>
To: "Jasmin J." <jasmin@anw.at>
Cc: crossgcc <crossgcc@sourceware.org>
Subject: Re: [RFC] Refactor autoconf options and build scripts
Date: Tue, 15 Sep 2015 14:21:00 -0000 [thread overview]
Message-ID: <CAAdc0hxMOv8N0sESueCcj6BPVcr3oUvSyEqmaKwsLCzoFrC=QQ@mail.gmail.com> (raw)
In-Reply-To: <55F61553.6040401@anw.at>
Folks,
To continue the Jasmin work about Travis-CI, I have copy paste the
Jasmin `.travis.yml` on my fork and add a script line to build all
samples this way:
for SAMPLE in $(./ct-ng list-samples 2>/dev/null | sed -n
's/^\[...\] *\(.*\)$/\1/p'); do ./ct-ng $SAMPLE; ./ct-ng build; done
It seems to be working for now: https://travis-ci.org/jmlemetayer/crosstool-ng
But going further into the Travis-CI documentation I see that the
build timeouts after 50 minutes:
http://docs.travis-ci.com/user/customizing-the-build/#Build-Timeouts
So it seems not to be the good strategy as building all samples
serially will take more than 50 minutes. But we could run parallel
builds using matrix build:
http://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix
The only difference is that we can't run build dynamically (using
`list-samples`) and we have to say which samples we want to build for
the continuous integration.
So, I think it could be a good thing to test / refresh the whole
samples and add them into the parallel integration builds when ready.
Regards,
JML
2015-09-14 2:31 GMT+02:00 Jasmin J. <jasmin@anw.at>:
> Hi!
>
>> I will give it a try, when I have time this week.
> Well, I was too curious to sleep ... ;)
> Here the result of the first ct-ng test build:
> https://travis-ci.org/jasmin-j/crosstool-ng/builds/80157690
>
> Here is the source for travis-ci:
> https://github.com/jasmin-j/crosstool-ng/tree/add_travis_ci
>
>> Maybe someone is so pleasant to tell me which binutils/gcc/libc(newlib)/gdb
>> combinations I shall try as a first step.
> What shall I try?
>
> BR
> Jasmin
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2015-09-15 14:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 17:32 Bryan Hundven
2015-09-08 23:42 ` Jasmin J.
2015-09-12 18:03 ` Thomas Petazzoni
2015-09-12 21:23 ` Bryan Hundven
2015-09-13 14:13 ` Trevor Woerner
2015-09-13 23:19 ` Jasmin J.
2015-09-13 23:35 ` Jasmin J.
2015-09-14 0:31 ` Jasmin J.
2015-09-15 14:21 ` Jean-Marie Lemetayer [this message]
2015-09-15 14:39 ` Trevor Woerner
2015-09-15 15:22 ` Jean-Marie Lemetayer
2015-09-15 18:30 ` Jasmin J.
2015-09-15 20:38 ` Jasmin J.
2015-09-15 20:49 ` Bryan Hundven
2015-09-15 22:46 ` Jasmin J.
2015-09-15 23:21 ` Bryan Hundven
2015-09-16 11:17 ` Jasmin J.
2015-09-16 11:45 ` Jean-Marie Lemetayer
2015-09-16 11:47 ` Jean-Marie Lemetayer
2015-09-16 13:20 ` Jasmin J.
2015-09-16 13:47 ` Jean-Marie Lemetayer
2015-09-16 14:50 ` Jasmin J.
2015-09-21 22:55 ` Jasmin J.
2015-09-22 8:17 ` Jean-Marie Lemetayer
2015-09-22 21:18 ` Bryan Hundven
2015-09-13 22:59 ` Jasmin J.
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='CAAdc0hxMOv8N0sESueCcj6BPVcr3oUvSyEqmaKwsLCzoFrC=QQ@mail.gmail.com' \
--to=jeanmarie.lemetayer@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=jasmin@anw.at \
/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).