Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Mark <oilehus@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem to add DConf in buildroot
Date: Fri, 10 Dec 2010 22:24:05 -0800 (PST)	[thread overview]
Message-ID: <200580.42715.qm@web111101.mail.gq1.yahoo.com> (raw)

Hi

When I tried to add DConf into buildroot, I got the following error:

../client/libdconf.so.0: undefined reference to `posix_fallocate'
collect2: ld returned 1 exit status

but I can build DConf without any problems outside of buildroot. 

In the Makefile.am, there's a line 

dconf_LDADD = $(gio_LIBS) ../client/libdconf.so.0

It seems to me that a dependency of "../client/libdconf.so.0" is not in the path when I built under buildroot, if so, anyone has an idea how to patch the makefile, so I can build Dconf and link with libdconf.so.0

Many Thanks,
Justin


  



      

             reply	other threads:[~2010-12-11  6:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-11  6:24 Justin Mark [this message]
2010-12-11  8:51 ` [Buildroot] Problem to add DConf in buildroot Lionel Landwerlin
2010-12-12  3:37   ` Justin Mark
2010-12-12 10:15     ` Thomas Petazzoni
2010-12-13  7:14       ` Justin Mark

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=200580.42715.qm@web111101.mail.gq1.yahoo.com \
    --to=oilehus@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox