All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Wrong compiler path when compiling zlib
Date: Thu, 2 Jan 2014 12:34:39 +0200	[thread overview]
Message-ID: <20140102103439.GW6589@tarshish> (raw)
In-Reply-To: <CA+hj=MoPxwwNn76Sh3vgP5VpkFsUn6uMRKtYW76a-A4DpoMkxg@mail.gmail.com>

HI Ivan,

On Thu, Jan 02, 2014 at 11:08:16AM +0100, Ivan Wagner wrote:
> On Thu, Jan 2, 2014 at 10:19 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> > Do you see the same error? Something else? Can you post your .config?
> 
> Yes the error is exactly the same. Here's the .config file:

[...]

> BR2_ARCH="armeb"
> BR2_ENDIAN="BIG"

Big endian ARM? This is quite unusual.

[...]

> BR2_LINUX_KERNEL_CUSTOM_REPO_URL="git://arago-project.org/git/projects/linux-am33x.git"

I don't think that AM33x SoCs are big endian. What happens if you change to 
little endian ARM?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-01-02 10:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 22:46 [Buildroot] Wrong compiler path when compiling zlib Ivan Wagner
2014-01-02  4:47 ` Baruch Siach
2014-01-02  9:06   ` Ivan Wagner
2014-01-02  9:19     ` Baruch Siach
2014-01-02 10:08       ` Ivan Wagner
2014-01-02 10:34         ` Baruch Siach [this message]
2014-01-02 10:37           ` Ivan Wagner
2014-01-02 11:06             ` Baruch Siach
2014-01-02 11:09               ` Ivan Wagner
2014-01-02 11:17                 ` Baruch Siach
2014-01-02 11:35                   ` Ivan Wagner
2014-01-02 12:21                     ` Thomas Petazzoni
2014-01-02 12:33                       ` Ivan Wagner
2014-01-02 12:20             ` Thomas Petazzoni

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=20140102103439.GW6589@tarshish \
    --to=baruch@tkos.co.il \
    --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.