Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@openembedded.org
Subject: Re: What is glibc-intermediate for?
Date: Sun, 09 Sep 2007 13:59:39 +0200	[thread overview]
Message-ID: <46E3E02B.22CEE170@vollmann.ch> (raw)
In-Reply-To: 74d0deb30709090150g161e6059q99f23e2ce1336e1c@mail.gmail.com

pHilipp Zabel wrote:
> glibc-initial is needed to build gcc-cross-initial, which is needed to
> build glibc-intermediate, which is needed to build gcc-cross, which is
> needed to build glibc.
Yes, this is what I expected as well, but what I don't see...

> Look at the package recipes, including
> glibc.inc to see what's going on.
Yes, I looked at all (well, most) of them.
The relevant lines are in glibc.inc:
> DEPENDS = "${@['virtual/${TARGET_PREFIX}gcc-initial', 'virtual/${TARGET_PREFIX}gcc']['nptl' in '${GLIBC_ADDONS}']} linux-libc-headers"
I have to admit that this is some magic for me (Python?), but
I interpret this that the dependency on virtual/gcc is somehow dependent
on NPTL.

> PROVIDES = "virtual/libc ${@['virtual/${TARGET_PREFIX}libc-for-gcc', '']['nptl' in '${GLIBC_ADDONS}']}"
And this looks like glibc provides libc-for-gcc (again somehow dependent
on NPTL), which means it's built first.

> The seemingly different build order you noticed is probably due to
> bitbake's fine-grained task dependencies. Maybe glibc was unpacked
> before gcc-cross, but it most certainly wasn't compiled before
> gcc-cross was staged.
In my case I don't have NPTL but linuxthreads, and interestingly
glibc is compiled before gcc-cross is compiled, but only staged after
gcc-cross is compiled, which is a strange order anyway...

Right now I still have problems with my glibc package, and I'll try
to fix those and then do a clean complete bootstrap again.
Let's see what comes out of that...

  Detlef

-- 
Detlef Vollmann   vollmann engineering gmbh
Linux and C++ for Embedded Systems    http://www.vollmann.ch/



  reply	other threads:[~2007-09-09 11:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-08 22:46 What is glibc-intermediate for? Detlef Vollmann
2007-09-09  8:50 ` pHilipp Zabel
2007-09-09 11:59   ` Detlef Vollmann [this message]
2007-09-09 12:32     ` Conditional Expressions in Python Dr. Michael Lauer
2007-09-09 18:25       ` PREFERRED_PROVIDER (was: Conditional Expressions in Python) Detlef Vollmann
2007-09-09 20:25         ` Khem Raj
2007-09-09 22:15           ` Detlef Vollmann
2007-09-09 20:28       ` Conditional Expressions in Python Khem Raj

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=46E3E02B.22CEE170@vollmann.ch \
    --to=dv@vollmann.ch \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox