All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] MTD build failing: undefined ref's  to bcopy, bcmp
Date: Thu, 7 Jan 2010 06:08:43 +0000 (UTC)	[thread overview]
Message-ID: <hi3tpb$k7d$1@ger.gmane.org> (raw)
In-Reply-To: hi377d$1i5$1@ger.gmane.org

On 2010-01-06, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> The u-boot-env-tools-on-target build was failing because mtd.h
> wasn't found, so in an attempt to fix that I tried selecting
> BR2_PACKAGE_MTD and BR2_PACKAGE_MTD_UTILS.  Now that's failing
> to build because of undefined references to bcopy, bcmp, bzero
> (make output below).
>
> Is there a trick to get mtd stuff to build?

Found it:

https://bugs.uclibc.org/show_bug.cgi?id=841

I'm getting the feeling tht I should have stuck with the last
release instead of using HEAD.  So far the number of packages
that won't build cleanly is at 4 and counting.

> Is BR2_PACKAGE_MTD/BR2_PACKAGE_MTD_UTILS actually what I need
> to provide mtd.h for building the u-boot env set/get target
> tools, or does mtd.h come from somewhere else?

Still working on that one.

-- 
Grant

  reply	other threads:[~2010-01-07  6:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 23:43 [Buildroot] MTD build failing: undefined ref's to bcopy, bcmp Grant Edwards
2010-01-07  6:08 ` Grant Edwards [this message]
2010-01-07  6:46   ` Grant Edwards
2010-01-07 17:02 ` Grant Edwards
2010-01-07 17:37   ` Thomas Petazzoni
2010-01-07 17:57     ` Grant Edwards
2010-01-07 22:30       ` Grant Edwards
2010-01-08  7:57         ` Thomas Petazzoni
2010-01-17 23:29 ` Peter Korsgaard

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='hi3tpb$k7d$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.