From: Sascha Hauer <s.hauer@pengutronix.de>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: next branch compilation errors
Date: Sun, 27 Nov 2011 11:57:40 +0100 [thread overview]
Message-ID: <20111127105740.GK27267@pengutronix.de> (raw)
In-Reply-To: <CAAfyv345QDLnUt4n7vTyBqmt-y5E9mOLuOgrb0VYBBENofwA=w@mail.gmail.com>
On Fri, Nov 25, 2011 at 10:42:33PM +0100, Belisko Marek wrote:
> Hi,
>
> today I update next branch and run MAKEALL for arm gives result that
> most of board aren't compilable because of:
>
> barebox/common/memory.c:66:14: warning: 'sbrk' defined but not used
> common/built-in.o: In function `memalign':
> memsize.c:(.text.memalign+0xc): undefined reference to `sbrk'
> make[1]: *** [barebox] Error 1
> make: *** [_all] Error 2
>
> or:
>
> barebox/common/memory.c:66:14: warning: 'sbrk' defined but not used
> common/built-in.o: In function `malloc':
> memsize.c:(.text.malloc+0x3e4): undefined reference to `sbrk'
> memsize.c:(.text.malloc+0x474): undefined reference to `sbrk'
> make[1]: *** [barebox] Error 1
> make: *** [_all] Error 2
>
> Not sure if I'm doing something wrong or miss something?
Works for me. This 'defined but not used' and then the linker error
looks like sbrk would be static, but it isn't.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-11-27 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 21:42 Belisko Marek
2011-11-27 10:57 ` Sascha Hauer [this message]
2011-11-27 12:11 ` Belisko Marek
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=20111127105740.GK27267@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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