All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot] libdrm tries to compile before cairo
Date: Sat, 19 Mar 2011 08:22:40 +0100	[thread overview]
Message-ID: <20110319082240.7757e09c@surf> (raw)
In-Reply-To: <AANLkTinJmH7Jsb25KJY6WN5YZaHHKqRJO0ctNA3NmKog@mail.gmail.com>

Hello Barry,

On Fri, 18 Mar 2011 18:40:17 +0800
Barry Kauler <bkauler@gmail.com> wrote:

> Hi, I am a first-time user of Buildroot. It has been chugging along
> nicely, but libdrm has failed to compile.
> 
> It reports that 'cairo.h' is missing. Which it is, cairo has not yet
> been compiled in the target.
> 
> So, using my own reasoning, I added "cairo" onto LIBDRM_DEPENDENCIES
> variable in file 'libdrm.mk'. I also deleted
> output/build/libdrm-2.4.19.
> 
> However, running 'make' again, it tries to compile libdrm again, and
> fails.
> 
> How do I make it compile cairo (and its deps) before libdrm?

Adding "cairo" to LIBDRM_DEPENDENCIES is enough to get it compiled
before libdrm. Something else is wrong in your setup, because that's
really enough.

However, Cairo is not required by libdrm. It seems that the problem is
that since you have Cairo installed on your host, libdrm ./configure
script thinks that Cairo is available. Such "information leakage" from
the host environment to the target environment is common and is one of
the major challenge an embedded Linux build system such as Buildroot
faces.

However, as libdrm uses pkg-config to detect the presence or absence of
cairo, it sounds strange to me that it detects the host version. Could
you please pastebin somewhere the output of the
output/build/libdrm-2.4.9/config.log case in the case of a failing
compilation ?

(I couldn't reproduce here in my test environment, since I don't have
Cairo development files installed on the host)

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2011-03-19  7:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 10:40 [Buildroot] [buildroot] libdrm tries to compile before cairo Barry Kauler
2011-03-18 11:38 ` bruce bushby
2011-03-18 12:37   ` Barry Kauler
2011-03-19  7:22 ` Thomas Petazzoni [this message]
2011-03-19  9:30   ` Barry Kauler
2011-03-19  9:58     ` Thomas Petazzoni
     [not found]       ` <AANLkTi=bFZ5MepDorK_6i1soraZGqw7B2T25HRZcH6D-@mail.gmail.com>
2011-03-19 11:29         ` Barry Kauler
2011-03-19 12:04           ` bruce bushby
2011-07-25 12:19 ` [Buildroot] " Peter Korsgaard

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=20110319082240.7757e09c@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.