From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/graph-depends: detect circular dependencies
Date: Sat, 23 Jan 2016 23:31:12 +0100 [thread overview]
Message-ID: <20160123223112.GD3363@free.fr> (raw)
In-Reply-To: <20160123232121.10d1ffe3@free-electrons.com>
Thomas, All,
On 2016-01-23 23:21 +0100, Thomas Petazzoni spake thusly:
> On Sat, 23 Jan 2016 23:04:45 +0100, Yann E. MORIN wrote:
[--SNIP--]
> Isn't kconfig already detecting such situations ? It normally spits out
> a warning when you have a circular dep, no ?
No, because the ones I'm concerned with are optional dependencies:
libgtk2 and libgtk3 have an optional dependency on cups, like so;
ifeq ($(BR2_PKG_CUPS),y)
FOO_DEPENDENCIES += cups
endif
And this is not caught at the Kconfig level, because there is actually
no circular deps there.
> > +# This function will check that there is no loop in the dependency chain
> > +# As a side effect, it builds up the dependency cache.
> > +def check_circular_deps(deps):
> > + def recurse(pkg):
> > + if not pkg in list(deps.keys()):
> > + return
> > + chain.append(pkg)
> > + for p in deps[pkg]:
> > + if p in chain:
> > + sys.stderr.write("\nRecursion detected for : %s\n" % (p))
> > + while True:
> > + _p = chain.pop()
> > + sys.stderr.write("which is a dependency of: %s\n" % (_p))
> > + if p == _p:
> > + sys.exit(1)
> > + recurse(p)
> > + chain.pop()
> > +
> > + chain = []
> > + for pkg in list(deps.keys()):
> > + recurse(pkg)
>
> I am a bit worried about the algorithmic complexity of this new
> function. As you know, we had issues with other parts of graph-depends
> having a too high algorithmic complexity to handle large
> configurations, or configurations having specific patterns of
> dependencies.
>
> Have you measured the time impact of this new check on a very large
> configuration (like allyespackageconfig) ?
I have an allyespackageconfig with an recent toolchain so I get a lot
of packages, and I tweaked the config to disable a few to enable others.
And no, the speed impact is not measurable for me. I'll come up with
numbers (of course, when there's no loop!) a bit later.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-01-23 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 22:04 [Buildroot] [PATCH] support/graph-depends: detect circular dependencies Yann E. MORIN
2016-01-23 22:21 ` Thomas Petazzoni
2016-01-23 22:31 ` Yann E. MORIN [this message]
2016-01-23 23:00 ` Yann E. MORIN
2016-01-24 1:04 ` Arnout Vandecappelle
2016-01-24 11:56 ` Yann E. MORIN
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=20160123223112.GD3363@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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