From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] dependency issue
Date: Sun, 28 Oct 2012 18:13:15 +0100 [thread overview]
Message-ID: <20121028171315.GD22246@pengutronix.de> (raw)
In-Reply-To: <loom.20121026T144703-422@post.gmane.org>
On Fri, Oct 26, 2012 at 01:07:58PM +0000, Steve Schefter wrote:
> I tried that, but it just seems to confirm that it isn't considering
> host-makedpend. Details below.
>
> First, it reports that it needs to build libdrm. That is consistent with the
> state/ptx_map_deps.sh line I quoted earlier:
> PTX_MAP_DEP_MESALIB=HOST_MESALIB:LIBDRM:HOST_MAKEDEPEND:DRI2PROTO:XORG_LIB_X11:
> XORG_LIB_XEXT:XORG_LIB_XXF86VM:XORG_LIB_XDAMAGE:XORG_LIB_XFIXES:XORG_PROTO_GL:
> EXPAT:GCCLIBS
>
> But then it moves on to building Mesalib without considering host-makedepend.
> Even though there are no state/host-makedepend... files.
>
> All of the other state files needed by the above map_deps line are in place (eg
> state/xorg-lib-x11..., state/xorg-lib-xxf86vm...) so it rightly doesn't need to
> do anything with those (has already done those). It just seems to be
> host-makedepend that it isn't considering.
Strange, I'm not seeing this here. Take a look at the generated dependencies:
$ grep host-makedepend platform-<some-platform>/state/ptx_dgen_deps.post
What does this say?
Michael
--
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 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-10-28 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 13:25 Steve Schefter
2012-10-25 14:09 ` Robert Schwebel
2012-10-26 13:07 ` Steve Schefter
2012-10-28 17:13 ` Michael Olbrich [this message]
2012-10-29 20:33 ` Steve Schefter
2012-10-29 21:26 ` Michael Olbrich
2012-10-30 0:27 ` Steve Schefter
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=20121028171315.GD22246@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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