Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Microblaze and ARC toolchains
Date: Mon, 2 Dec 2013 20:51:42 +0100	[thread overview]
Message-ID: <20131202205142.5b4cfd3c@skate> (raw)
In-Reply-To: <E6BF041E97966E4DB955F0DF883AD2D685F1B041@de02wembxa.internal.synopsys.com>

Mischa, Spenser,

On Mon, 2 Dec 2013 13:20:41 +0000, Mischa Jonker wrote:

> >  * On the ARC side of things, what I get is a failure at the uClibc
> >    build step. However, what's weird is that I did get one
> > successful build, but now that I've restarted everything from
> > scratch, it fails (and did so two times in a row) :
> 
> Unfortunately I am unable to reproduce: I have rebased the patches to
> the latest status of today and used your defconfig below. I even
> cleared the "dl" folder. 

Ignore my previous e-mail. It was my fault. My patches to try to avoid
MAKEINFO were changing "make install" to just "make" due to me
overriding MAKE_OPT. So obviously, binutils were no longer being
installed, causing all sort of weird problems.

> I will retest it on our compute farm that has very old Linux
> distributions running on it with almost no development tools at all.
> Maybe the issue shows itself there.

Don't spend time doing that. The ARC and Microblaze builds are now OK.
I'm just fixing a few things, and I will send a complete batch of
patches for Peter to pull as soon as things are ready for me.

Thanks, and sorry for the noise,

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

      parent reply	other threads:[~2013-12-02 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 23:40 [Buildroot] Microblaze and ARC toolchains Thomas Petazzoni
     [not found] ` <E6BF041E97966E4DB955F0DF883AD2D685F1B041@de02wembxa.internal.synopsys.com>
2013-12-02 19:51   ` Thomas Petazzoni [this message]

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=20131202205142.5b4cfd3c@skate \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox