All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-02-21
Date: Wed, 24 Feb 2016 23:09:45 +0100	[thread overview]
Message-ID: <56CE2A29.6080106@mind.be> (raw)
In-Reply-To: <20160224214249.GO14809@waldemar-brodkorb.de>

On 02/24/16 22:42, Waldemar Brodkorb wrote:
> Hi Thomas,
> Thomas Petazzoni wrote,
> 
>> Hello,
>>
>>>        sparc |                  libdrm-2.4.66 | NOK | http://autobuild.buildroot.net/results/a17047ada385e5be5f60c07254597fcb7c4183d0/
>>>        sparc |                  libdrm-2.4.66 | NOK | http://autobuild.buildroot.net/results/6d79591bce2d3fa5b93e268fe50d5b89ecd24521/
>>
>> Could be fixed by http://patchwork.ozlabs.org/patch/569818/, but this
>> patch is wrong I believe now that we have proper Config.in options to
>> describe atomic operation dependencies.
>>
>> Waldemar, could you have a look?
> 
> What about adding a nice chapter to the buildroot manual explaining
> how to handle typical build problems. Subchapters like:
> - PIE and static builds 
> - Atomic build failures

 Great plan! Patches welcome :-)


 Regards,
 Arnout

> 
> come into my mind. 
> 
> Then anybody trying to fix autobuilder problems could step in.
> 
> My personal agenda for buildroot is more like this:
> - fix ARM noMMU internal toolchain 
> - push any required elf2flt changes to new (old) upstream and update
>   br url to fetch it from there
> - add internal bfin toolchain support as soon as gcc 6 is out and
>   integrated
> - resend my coldfire/m68k patch set in a more granular way
> - fix any interesting uClibc-ng compile problems
> ..
> - analyze any interesting sparc/sparc64 autobuilder problems
>   if no other is fixing it :)
> 
> best regards
>  Waldemar
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-02-24 22:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-02-21 Thomas Petazzoni
2016-02-22 14:05 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-02-23 10:12   ` John Keeping
2016-02-23 10:40     ` Jeroen Roovers
2016-02-23 11:03       ` John Keeping
2016-02-23 12:30       ` Thomas Petazzoni
2016-02-24 11:08   ` Eric Limpens
2016-02-24 20:45     ` Arnout Vandecappelle
2016-02-24 20:59       ` Eric Limpens
2016-02-24 21:42   ` Waldemar Brodkorb
2016-02-24 22:09     ` Arnout Vandecappelle [this message]
2016-02-27 15:19   ` Romain Naour
2016-02-27 22:05   ` Bernd Kuhls
2016-03-01  9:38     ` Thomas Petazzoni
2016-02-28  0:17   ` Bernd Kuhls
2016-03-01  9:39     ` Thomas Petazzoni
2016-03-03 13:56   ` Gustavo Zacarias
  -- strict thread matches above, loose matches on Subject: below --
2016-02-22 19:05 Olivier Schonken
2016-02-22 21:55 ` Romain Naour
2016-02-22 22:21 ` Thomas Petazzoni
2016-02-23  7:34   ` Olivier Schonken
2016-02-23  8:11     ` Thomas Petazzoni
2016-02-23 11:13       ` Olivier Schonken
2016-02-24 21:30       ` Waldemar Brodkorb

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=56CE2A29.6080106@mind.be \
    --to=arnout@mind.be \
    --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.