From: Jeroen Hofstee <jeroen@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] recent tools on FreeBSD
Date: Thu, 05 Feb 2015 20:51:45 +0100 [thread overview]
Message-ID: <54D3C9D1.6030905@myspectrum.nl> (raw)
In-Reply-To: <CAF=5bWceguR_vLGt_0dAn+TmXGUu_PVBCg-tMR5n72JktFJyHg@mail.gmail.com>
Hello Guilherme,
Thanks for commenting on this,
On 02/05/15 13:27, Guilherme Maciel Ferreira wrote:
> Hi Jeroen,
>
> My apologies, I didn't test the tools on BSD. The answers are inline.
>
> Best regards,
> Guilherme
>
> Am 04.02.2015 19:37 schrieb "Jeroen Hofstee" <jeroen@myspectrum.nl>:
>> Hello Guilherme / Simon,
>>
>> It seems that commit f86ed6a8d52c99bb2d17d3cac1647edca0c4399c,
>> "tools: moved code common to all image tools to a separated module."
> I guess the culprit is commit a93648d197df48fa46dd55f925ff70468bd81c71,
> "imagetool: replace image registration function by linker_lists feature".
> Because that commit introduced the linker script to imagetools.
>
Likely, since some patches depend on each other I was unable to revert
a single commit.
Anyway as far as I am concerned there are two separate
build targets, the bare u-boot having an (almost) naked compiler, beside
stdarg and stdbool? without any other host includes or objects (well with
CONFIG_USE_PRIVATE_LIBGCC=y). U-boot provides linker scripts for them,
and we have fine grained control over them and an excuse to throw any
trick at them if it makes things faster / smaller etc. It is still nice
if this
compiles anywhere though..
On the other hand there are "tools" for the host / target userland, which
should build against the host / targets "std*". Those things should be
buildable
on any decent host / target and be straightforward (and _not_ define KERNEL
etc, since it are userland tools). There is no linker for them afaik, so
tweaking
them seems like a bad idea. Hence I am tempted to remove the use of
linker generated lists from tools...
>> - and really last, how do I test if it works..
> There are two scripts to test the image tools, test-imagetools.sh and
> test-fit.py. Running those scripts you make sure the linker list is
> properly setup, because it is required by the imagetools to find the image
> type.
>
> $ make O=sandbox clean
> $ make O=sandbox sandbox_config
> $ make mrproper
> $ make O=sandbox
> $ ./test/image/test-imagetools.sh
> $ ./test/image/test-fit.py -u sandbox/u-boot
Sandbox used to build on FreeBSD, but it is quite a mess at the moment.
But a I said, I think the best solution for tools is not to use linker
generated
list in the first place for tools.
Regards,
Jeroen
next prev parent reply other threads:[~2015-02-05 19:51 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 [this message]
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
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=54D3C9D1.6030905@myspectrum.nl \
--to=jeroen@myspectrum.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox