From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] dependency issue
Date: Thu, 25 Oct 2012 16:09:56 +0200 [thread overview]
Message-ID: <20121025140956.GF23204@pengutronix.de> (raw)
In-Reply-To: <loom.20121025T150846-83@post.gmane.org>
On Thu, Oct 25, 2012 at 01:25:24PM +0000, Steve Schefter wrote:
> I'm having an issue with ptxdist building one of the components out of order.
> Mesalib depends on host-makedepend, but it is building Mesalib first.
>
> rules/mesalib.in starts off with:
> menuconfig MESALIB
> tristate
> prompt "mesa "
> select HOST_MESALIB
> select LIBDRM
> select HOST_MAKEDEPEND
>
> There's no circular dependency causing problems: I've tried removing the one
> select statement from rules/host-makedepend.in so that it has no dependencies.
> That had no effect.
>
> ptxdist seems to be aware of Mesalib/host-makedepend dependency as
> state/ptx_map_deps.sh contains the line:
> 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
>
> Any suggestions on what I might have set up incorrectly to cause ptxdist to
> build out of order? Or what, beyond the select statement, can force it to build
> host-makedepend first when I run "ptxdist go"?
You can try to run 'ptxdist --debug go', which prints out the make
deductions. Maybe that gives you a hint why Mesalib is built first.
rsc
--
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-25 14:09 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 [this message]
2012-10-26 13:07 ` Steve Schefter
2012-10-28 17:13 ` Michael Olbrich
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=20121025140956.GF23204@pengutronix.de \
--to=r.schwebel@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