All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Native builds broken ?
Date: Mon, 31 Mar 2014 09:34:52 +0200	[thread overview]
Message-ID: <20140331093452.463e4060@amdc2363> (raw)
In-Reply-To: <20140331095623.DB64.AA925319@jp.panasonic.com>

Hi Masahiro,

> Hi
> 
> On Sun, 30 Mar 2014 23:08:09 +0100
> selsinork at gmail.com wrote:
> 
> > Trying to build the u-boot master branch today from
> > 0b2da7e209f4110b7c81d578336a10330e4a4404 natively on arm gives
> > 
> > make: arm-linux-gcc: Command not found
> > /bin/sh: arm-linux-gcc: command not found
> > dirname: missing operand
> > Try 'dirname --help' for more information.
> >   CHK     include/config/uboot.release
> >   UPD     include/config/uboot.release
> >   CHK     include/generated/version_autogenerated.h
> > /bin/sh: arm-linux-gcc: command not found
> > /bin/sh: arm-linux-ld.bfd: command not found
> >   UPD     include/generated/version_autogenerated.h
> >   CHK     include/generated/timestamp_autogenerated.h
> >   UPD     include/generated/timestamp_autogenerated.h
> >   CC      lib/asm-offsets.s
> > /bin/sh: arm-linux-gcc: command not found
> > /data/linux/source/u-boot/./Kbuild:34: recipe for target
> > 'lib/asm-offsets.s' failed make[1]: *** [lib/asm-offsets.s] Error
> > 127 Makefile:997: recipe for target 'prepare0' failed
> > make: *** [prepare0] Error 2
> > 
> > ways around this appear to be to revert
> > 9b6e2c363f2686d6f7bf61fbe58b7591b71d3e8b "kbuild: fix CROSS_COMPILE
> > settings in config.mk"
> > 
> > or to start a native build with
> > 
> > make CROSS_COMPILE=
> > 
> > which seems rather counter-intuitive.
> > 
> > I'm no makefile/Kbuild expert, but wouldn't the changes to
> > arch/*/config.mk be better done like this
> > 
> > ifneq ($(HOSTARCH),$(ARCH))
> >         ifeq ($(CROSS_COMPILE),)
> >                 CROSS_COMPILE := arm-linux-
> >         endif
> > endif
> > 
> > so that we only set CROSS_COMPILE if we're actually cross compiling
> > instead of forcing it when it's intentionally empty because we're
> > building natively ?
> 
> 
> See
> http://patchwork.ozlabs.org/patch/331460/

I hope, that this patch will be included before v2014.04 release. It is
supposed to be pulled by Albert :-).

> 
> 
> 
> Best Regards
> Masahiro Yamada



-- 
Best regards,

Lukasz Majewski

Samsung R&D Institute Poland (SRPOL) | Linux Platform Group

  reply	other threads:[~2014-03-31  7:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30 22:08 [U-Boot] Native builds broken ? selsinork at gmail.com
2014-03-31  0:56 ` Masahiro Yamada
2014-03-31  7:34   ` Lukasz Majewski [this message]
2014-03-31  8:37   ` selsinork at gmail.com

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=20140331093452.463e4060@amdc2363 \
    --to=l.majewski@samsung.com \
    --cc=u-boot@lists.denx.de \
    /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.