All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] recent tools on FreeBSD
Date: Tue, 10 Feb 2015 07:52:59 -0700	[thread overview]
Message-ID: <CAPnjgZ0kgPttnVt0-o_Q3-rDRApe5AWGjwvoK6g8_D8U8CnTqQ@mail.gmail.com> (raw)
In-Reply-To: <54D73485.90101@myspectrum.nl>

Hi Jeroen,

On 8 February 2015 at 03:03, Jeroen Hofstee <jeroen@myspectrum.nl> wrote:
> Hello Simon,
>
>
> On 07-02-15 22:02, Simon Glass wrote:
>>>
>>> If this still fails, you can always build it from source, but needs a bit
>>> of
>>> patience.
>>> Somthing like this should always work:
>>>
>>> portsnap fetch
>>> portsnap extract
>>>
>>> cd /usr/ports/devel/git
>>> make config-recursive
>>> make
>>> make install
>>>
>>> Let me know if you still have issues.
>>>
>>> Regards,
>>> Jeroen
>>>
>>>
>>> [1] (as root)
>>>
>>> pkg install nano git
>>> git clone git://git.denx.de/u-boot.git
>>> git checkout v2015.01 -b b2015.01
>>> cd u-boot
>>> pkg install arm-gnueabi-binutils gmake
>>>
>>> gmake CC="clang -target arm-freebsd-eabi -no-integrated-as -mllvm
>>> -arm-use-movt=0" rpi_defconfig
>>> gmake CROSS_COMPILE=arm-gnueabi-freebsd- CC="clang -target
>>> arm-freebsd-eabi
>>> -no-integrated-as -mllvm -arm-use-movt=0
>>> -B/usr/local/bin/arm-gnueabi-freebsd-" CONFIG_USE_PRIVATE_LIBGCC=y
>>>
>> Is this for using an ARM cross-compiler? What should I do for building
>> the tools? I keep seeing 'gcc not found'.
>
>
> Yes it is for cross building. So the host clang / host ld do the native
> build, the host clang with some help from arm-gnueabi-freebsd-as and
> arm-gnueabi-freebsd-ld do the cross build.
>
> If you only want  to build tools for the host you need something like:
>
> gmake CC=cc sandbox_config tools
>
> Since CC is defined to $(CROSS_COMPILE)gcc it ends up being gcc when
> CROSS_COMPILE is not set, hence you get the 'gcc not found' errors.

Thanks for your help. I have a FreeBSD running now and can build the
tools with your patch.

Regards,
Simon

  reply	other threads:[~2015-02-10 14:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 19:37 [U-Boot] recent tools on FreeBSD Jeroen Hofstee
2015-02-05  3:34 ` Simon Glass
2015-02-05  7:07   ` Jeroen Hofstee
2015-02-05 12:37   ` Guilherme Maciel Ferreira
2015-02-05 12:27 ` Guilherme Maciel Ferreira
2015-02-05 19:51   ` Jeroen Hofstee
2015-02-06  3:05     ` Simon Glass
2015-02-06 19:56       ` Jeroen Hofstee
2015-02-06 20:40         ` Andreas Bießmann
2015-02-06 21:00           ` Simon Glass
2015-02-07 10:04             ` Jeroen Hofstee
2015-02-07 15:10               ` Simon Glass
2015-02-07 16:23                 ` Andreas Bießmann
2015-02-07 16:29                   ` Simon Glass
2015-02-07 17:08                     ` Andreas Bießmann
2015-02-07 17:19                       ` Simon Glass
2015-02-07 21:19                       ` [U-Boot] [RFC PATCH] tools/imagetool: remove linker generated list Andreas Bießmann
2015-02-07 21:38                         ` Jeroen Hofstee
2015-02-08  0:05                         ` Guilherme Maciel Ferreira
2015-02-10 15:01                         ` Simon Glass
2015-02-07 20:17                 ` [U-Boot] recent tools on FreeBSD Jeroen Hofstee
2015-02-07 21:02                   ` Simon Glass
2015-02-08 10:03                     ` Jeroen Hofstee
2015-02-10 14:52                       ` Simon Glass [this message]
2015-02-09 23:20                 ` [U-Boot] sandbox " Jeroen Hofstee
2015-02-10 15:34                   ` Simon Glass

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=CAPnjgZ0kgPttnVt0-o_Q3-rDRApe5AWGjwvoK6g8_D8U8CnTqQ@mail.gmail.com \
    --to=sjg@chromium.org \
    --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.