All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-core@lists.openembedded.org
Subject: eglibc-2.17 build breaks with nptl #include nested too deeply
Date: Wed, 05 Jun 2013 12:04:37 -0400	[thread overview]
Message-ID: <20130605160437.GA10298@denix.org> (raw)

Has anyone seen this issue before - my builds are failing with the following:

                  from ../ports/sysdeps/arm/sysdeps/../nptl/pthread_spin_lock.c:23,
                  from ../ports/sysdeps/arm/sysdeps/../nptl/pthread_spin_lock.c:23,
                  from ../ports/sysdeps/arm/nptl/pthread_spin_lock.c:23:
../ports/sysdeps/arm/sysdeps/../nptl/pthread_spin_lock.c:23:47: error: #include nested too deeply

Google only returns a recent discussion on the Cygwin list:

http://cygwin.1069669.n5.nabble.com/BUG-Ability-to-access-nonexistent-directories-td98708.html

But, I'm building this on Ubuntu 12.04, not Cygwin. Any pointers, while I 
keep digging? Thanks.

-- 
Denys


             reply	other threads:[~2013-06-05 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 16:04 Denys Dmytriyenko [this message]
2013-06-05 19:59 ` eglibc-2.17 build breaks with nptl #include nested too deeply Denys Dmytriyenko

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=20130605160437.GA10298@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@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.