Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] libfakeroot problem
Date: Fri, 12 May 2017 17:06:26 +0000	[thread overview]
Message-ID: <f672b599-946e-6bdc-236a-7508df02dc30@ou.edu> (raw)

I've got an embedded project I would like to update from 2016.05 to 
2017.05 so I pulled the latest snapshot late last night.
The 64-bit build always gets an error with libfakeroot. Is this a known 
issue? I just resubscribed, but I did not see anything obvious in the 
archives.

My development box runs Ubuntu and to make testing easier I try to use a 
compatible kernel/headers, hence the 4.4

hdi at hdi-H110N:~/updatetest/buildroot-2017.05$ uname -a
Linux hdi-H110N 4.4.0-72-generic #93~14.04.1-Ubuntu SMP Fri Mar 31 
15:05:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Here is what I have for a stripped down defconfig after "make savedefconfig"

hdi at hdi-H110N:~/updatetest/buildroot-2017.05$ more defconfig
BR2_x86_64=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_KERNEL_HEADERS_4_4=y

Here are the last few lines after "make olddefconfig; make"

ERROR: ld.so: object 'libfakeroot.so' from LD_PRELOAD cannot be 
preloaded (cannot open shared object file): ignored.
/usr/bin/install -m 0644 support/misc/target-dir-warning.txt 
/home/hdi/updatetest/buildroot-2017.05/output/target/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM

Any thoughts?

Steve Kenton

             reply	other threads:[~2017-05-12 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 17:06 Steve Kenton [this message]
2017-05-12 23:40 ` [Buildroot] libfakeroot problem - solved Steve Kenton
2017-05-15 21:39   ` 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=f672b599-946e-6bdc-236a-7508df02dc30@ou.edu \
    --to=skenton@ou.edu \
    --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