From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] igep0030_nand_defconfig compile is broken
Date: Mon, 25 Apr 2016 07:18:56 -0400 [thread overview]
Message-ID: <20160425111856.GF3732@bill-the-cat> (raw)
In-Reply-To: <571DFBE4.6060806@suse.de>
On Mon, Apr 25, 2016 at 01:13:40PM +0200, Alexander Graf wrote:
> On 04/25/2016 11:36 AM, Heiko Schocher wrote:
> >Hello
> >
> >on current HEAD of mainline code, compile for "igep0030_nand_defconfig"
> >is broken:
> >
> >arm-linux-gnueabi-ld.bfd: u-boot-spl section `.data' will not fit
> >in region `.sram'
> >arm-linux-gnueabi-ld.bfd: region `.sram' overflowed by 1176 bytes
> >scripts/Makefile.spl:247: recipe for target 'spl/u-boot-spl' failed
> >make[1]: *** [spl/u-boot-spl] Error 1
> >Makefile:1334: recipe for target 'spl/u-boot-spl' failed
> >make: *** [spl/u-boot-spl] Error 2
> >
> >a git bisect shows:
> >
> >$ git bisect bad
> >578ec3b1fb3f4e85d8243d442f66f308c94b791d is the first bad commit
> >commit 578ec3b1fb3f4e85d8243d442f66f308c94b791d
> >Author: Alexander Graf <agraf@suse.de>
> >Date: Mon Apr 11 16:16:21 2016 +0200
> >
> > distro: Enable iso partition code
> >
> > Now that we can properly boot EFI payloads from iso el torito
> > images, let's enable support for isos by default in the distro
> > header.
> >
> > Signed-off-by: Alexander Graf <agraf@suse.de>
> >
> >:040000 040000 ba4615980d26ef80e9b9e5ce9fc2440456c556cb
> >6d0ba56e5ed81ea54d37566763f3f225bd2d00ad M include
> >pollux:u-boot hs [(kein Branch, bin?re Suche begonnen bei master)] $
> >
> >buildman show 3 boards:
> >
> > arm: + igep0030_nand
> >+arm-linux-gnueabi-ld.bfd: u-boot-spl section `.data' will not fit
> >in region `.sram'
> >+arm-linux-gnueabi-ld.bfd: region `.sram' overflowed by 1236 bytes
> >+make[2]: *** [spl/u-boot-spl] Error 1
> >+make[1]: *** [spl/u-boot-spl] Error 2
> >+make: *** [sub-make] Error 2
> > arm: + duovero
> >+arm-linux-gnueabi-ld.bfd: u-boot-spl section `.data' will not fit
> >in region `.sram'
> >+arm-linux-gnueabi-ld.bfd: region `.sram' overflowed by 816 bytes
> >+make[2]: *** [spl/u-boot-spl] Error 1
> >+make[1]: *** [spl/u-boot-spl] Error 2
> >+make: *** [sub-make] Error 2
> > arm: + igep0020_nand
> >+arm-linux-gnueabi-ld.bfd: u-boot-spl section `.data' will not fit
> >in region `.sram'
> >+arm-linux-gnueabi-ld.bfd: region `.sram' overflowed by 1220 bytes
> >+make[2]: *** [spl/u-boot-spl] Error 1
> >+make[1]: *** [spl/u-boot-spl] Error 2
> >+make: *** [sub-make] Error 2
> > 517 0 40 /557 q8_a13_tablet
> >
> >Could somebody provide a fix for this boards?
>
> Ouch, I didn't realize that distro defconfigs flow into SPL as well.
> Is there any streamlined way to only select default config options
> for SPL?
As much as anything else it's also how gcc (prior to 6) combines strings
prior to -fdata-sections/-ffunction-sections. Just need to find
something or another that can come out of igep, most likely.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160425/5b4ee133/attachment.sig>
prev parent reply other threads:[~2016-04-25 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 9:36 [U-Boot] igep0030_nand_defconfig compile is broken Heiko Schocher
2016-04-25 11:13 ` Alexander Graf
2016-04-25 11:18 ` Tom Rini [this message]
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=20160425111856.GF3732@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox