All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Waterman <awaterman@dawning.com>
To: openembedded-devel@lists.openembedded.org
Subject: Build fail for eglibc
Date: Thu, 07 Jul 2011 08:55:46 -0400	[thread overview]
Message-ID: <4E15ACD2.4010104@dawning.com> (raw)


Hello List,

I have been trying to compile cacao for a development platform using 
openembedded. I have built a tool chain using crosstool-ng targeting
arm-none-linux-gnueabi, and have set up openembedded following the getting
started page on the wiki.

However, I run into an issue with eglibc. I get a make error during the compile
for eglibc:

... snip ...
| make[2]: Entering directory `/home/alex/bb-build/tmp/work/armv5te-none-linux-gnueabi/eglibc-2.12-r21.8+svnr13230/eglibc-2_12/libc/nss'
| Makefile:85: *** OPTION_EGLIBC_NSSWITCH_FIXED_CONFIG variable left unset.  Stop.
| make[2]: Leaving directory `/home/alex/bb-build/tmp/work/armv5te-none-linux-gnueabi/eglibc-2.12-r21.8+svnr13230/eglibc-2_12/libc/nss'
| make[1]: *** [nss/subdir_lib] Error 2
... snip ...

I am using the latest git tree, as of 15 minutes ago.

Any help or advice would be greatly appreciated. Are there any work arounds?
Or fixes?

Oh, and my local.conf file:

---
# Source directory.
DL_DIR = "${HOME}/bitbake-sources"

# BB files...
BBFILES = "/usr/openembedded/recipes/*/*.bb"

# Our machine in question...
MACHINE = "at91sam9m10g45ek"
TARGET_ARCH = "arm"

# Target operating system.
TARGET_OS = "linux"
DISTRO = "minimal"

# Tool chain ralated stuff.
TOOLCHAIN_VENDOR = "-none"
TOOLCHAIN_TYPE = "external"
TOOLCHAIN_BRAND = "x-tool"
TOOLCHAIN_PATH = "/usr/alex-embeded"

# Output image type.
IMAGE_FSTYPES = "jffs2"

# Other things
BBINCLUDELOGS = "yes"

SRCPV = "${@bb.fetch.get_srcrev(d)}"
---

Best Regards,
Alex

-- 
Alex Waterman
Computer Engineer
Phone: 215-896-4920
Email: awaterman@dawning.com




                 reply	other threads:[~2011-07-07 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4E15ACD2.4010104@dawning.com \
    --to=awaterman@dawning.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.