public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] sunxi configs break with CONFIG_API in v2015.10-rc4
Date: Sun, 4 Oct 2015 18:27:49 +0200	[thread overview]
Message-ID: <56115385.8010607@suse.de> (raw)

Hi,

For at least Bananapi, Cubieboard, Cubieboard2, Cubietruck, Mele_A1000,
A10-OLinuXino-Lime, A13-OLinuXino, A20-OLinuXino-Lime2 and probably
other sunxi boards, enabling CONFIG_API in the distro defaults header
leads to build failures like this one:

[  105s]   CC      api/api_net.o
[  105s] api/api_net.c: In function 'dev_enum_net':
[  105s] api/api_net.c:61:35: warning: initialization from incompatible
pointer type [-Wincompatible-pointer-types]
[  105s]   struct eth_device *eth_current = eth_get_dev();
[  105s]                                    ^
[  105s] api/api_net.c:68:39: error: dereferencing pointer to incomplete
type 'struct eth_device'
[  105s]   memcpy(di->di_net.hwaddr, eth_current->enetaddr, 6);
[  105s]                                        ^
[  105s] scripts/Makefile.build:277: recipe for target 'api/api_net.o'
failed
[  105s] make[1]: *** [api/api_net.o] Error 1
[  105s] Makefile:1191: recipe for target 'api' failed
[  105s] make: *** [api] Error 2

Could you please check on why that is?

By comparison, this is working fine for jetson-tk1; arndale, snow and
possibly others are lacking a define for the maximum number of MMCs
(preparing a patch).

Thanks,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N?rnberg)

             reply	other threads:[~2015-10-04 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 16:27 Andreas Färber [this message]
2015-10-04 17:28 ` [U-Boot] sunxi configs break with CONFIG_API in v2015.10-rc4 Hans de Goede

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=56115385.8010607@suse.de \
    --to=afaerber@suse.de \
    --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