From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: a9m2440_defconfig failed to compile
Date: Tue, 7 Sep 2010 15:31:00 +0200 [thread overview]
Message-ID: <20100907133100.GF30509@game.jcrosoft.org> (raw)
In-Reply-To: <AANLkTinym9bzzP8J7OmY=kauzEHdOVgVsMJ78Yyph2-t@mail.gmail.com>
On 14:59 Tue 07 Sep , Belisko Marek wrote:
> On Tue, Sep 7, 2010 at 2:01 PM, Juergen Beisert <jbe@pengutronix.de> wrote:
> > Belisko Marek wrote:
> >> Hi,
> >>
> >> following steps lead to compilation error (barebox v2010.09.0):
> >>
> >> 1. make a9m2440_defconfig ARCH=arm
> >> 2. make CROSS_COMPILE=arm-linux- ARCH=arm
> >>
> >> error: arch/arm/boards/a9m2440/built-in.o: In function `nand_boot':
> >> /home/open-nandra/projects/barebox/arch/arm/boards/a9m2440/a9m2440.c:183:
> >> undefined reference to `s3c24x0_nand_load_image'
> >>
> >> It seems in Kconfig for mach-s3c24xx is selected NAND_S3C24X0 but
> >> missing CONFIG_MTD and CONFIG_NAND to properly compile
> >> nand driver for s3c24xx.
> >>
> >> Could I send a patch with updated defconfig or exist better solution?
> >
> > Should be repaired in the menu and the source files. The defconfig is not the
> > correct location to fix it. There are dependencies between these components
> > that must be part of the menu.
> Not sure which menu type do you think?
Kconfig file
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-09-07 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 10:58 Belisko Marek
2010-09-07 12:01 ` Juergen Beisert
2010-09-07 12:59 ` Belisko Marek
2010-09-07 13:31 ` Jean-Christophe PLAGNIOL-VILLARD [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=20100907133100.GF30509@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=marek.belisko@gmail.com \
/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