Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Interesting circular dependency, how to solve?
Date: Thu, 7 Jul 2016 19:33:14 +0200	[thread overview]
Message-ID: <20160707173314.GC3827@free.fr> (raw)
In-Reply-To: <20160707163322.GA3827@free.fr>

Thomas, Paul, All,

On 2016-07-07 18:33 +0200, Yann E. MORIN spake thusly:
> On 2016-07-06 17:56 +0200, Thomas Petazzoni spake thusly:
> > Today, Paul (in Cc) reported on IRC an interesting problem: on a
> > configuration with systemd enabled (and acting as udev provider),
> > pciutils would fail to build due to libudev.h being missing.
> > 
> > After some investigation, "make graph-depends" revealed the origin of
> > the problem: a very interesting circular dependency. Here is what make
> > graph-depends thinks of the situation:
> > 
> > Recursion detected for  : systemd
> > which is a dependency of: udev
> > which is a dependency of: pciutils
> > which is a dependency of: linux
> > which is a dependency of: cryptodev-linux
> > which is a dependency of: openssl
> > which is a dependency of: libcurl
> > which is a dependency of: systemd
> 
> Hmmm... make itself should have spit a warning of its own. However, I
> could not see a way to have make error out; it is a mere warning... :-(

Indeed it does catch it. But not until it is time for it to actuall
build openssl:

    make[1]: Circular /home/ymorin/dev/buildroot/O/build/openssl-1.0.2h/.stamp_configured <- cryptodev-linux dependency dropped.
    >>> openssl 1.0.2h Downloading

DAng. Why doesn't it detect it at the beginning of the build? And why
can't we tell make to consider it an error rather than a warning?

Damn... :-/

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2016-07-07 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 15:56 [Buildroot] Interesting circular dependency, how to solve? Thomas Petazzoni
2016-07-06 17:54 ` ANDY KENNEDY
2016-07-06 18:20   ` Thomas Petazzoni
2016-07-06 19:25     ` ANDY KENNEDY
2016-07-07 17:00     ` Yann E. MORIN
2016-07-07 19:26       ` Thomas Petazzoni
2016-07-07 23:25         ` Yann E. MORIN
2016-07-07 16:33 ` Yann E. MORIN
2016-07-07 17:33   ` Yann E. MORIN [this message]
2016-07-07 19:31   ` Thomas Petazzoni

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=20160707173314.GC3827@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