From: Alexander Kurz <akurz@blala.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v4 2/3] add basic ELF parser
Date: Fri, 15 Jun 2018 18:20:10 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.20.1806151813280.24953@blala.de> (raw)
In-Reply-To: <20180606075912.2470-3-o.rempel@pengutronix.de>
Hi Oleksij,
when compiling for some random arm platform, next currently rasises this
warning: (BOOTM) selects ELF which has unmet direct dependencies (MIPS)
Neither ELF nor BOOTM are MIPS specific.
This issue was resolved with v3, and with v4 it's back?
Regards, Alexander
On Wed, 6 Jun 2018, Oleksij Rempel wrote:
> This parser is needed for kernel boot support on MIPS
> and can potentially reused on other platforms.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
...
> diff --git a/common/Kconfig b/common/Kconfig
> index b7000c4d7..b9adc4c39 100644
> --- a/common/Kconfig
> +++ b/common/Kconfig
> @@ -46,6 +46,10 @@ config BLOCK
> config BLOCK_WRITE
> bool
>
> +config ELF
> + bool
> + depends on MIPS
> +
> config FILETYPE
> bool
>
> @@ -548,6 +552,7 @@ config TIMESTAMP
> automatically enabled when you select CFG_CMD_DATE .
>
> menuconfig BOOTM
> + select ELF
> select UIMAGE
> default y if COMMAND_SUPPORT
> bool "bootm support"
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-06-15 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 7:59 [PATCH v4 0/3] MIPS: provide basic ELF support Oleksij Rempel
2018-06-06 7:59 ` [PATCH v4 1/3] filetype: add ELF type Oleksij Rempel
2018-06-06 7:59 ` [PATCH v4 2/3] add basic ELF parser Oleksij Rempel
2018-06-15 18:20 ` Alexander Kurz [this message]
2018-06-16 8:12 ` Oleksij Rempel
2018-06-06 7:59 ` [PATCH v4 3/3] MIPS: bootm: add ELF handler Oleksij Rempel
2018-06-08 5:59 ` [PATCH v4 0/3] MIPS: provide basic ELF support Sascha Hauer
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=alpine.DEB.2.20.1806151813280.24953@blala.de \
--to=akurz@blala.de \
--cc=barebox@lists.infradead.org \
--cc=o.rempel@pengutronix.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