Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas <tokant@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot-2010.05-rc2, problem with binutils-2.20.1
Date: Mon, 24 May 2010 20:10:09 +0200	[thread overview]
Message-ID: <1274724609.13140.8.camel@bernd-desktop> (raw)
In-Reply-To: <20100522145508.10c885e7@surf>

On Sat, 2010-05-22 at 14:55 +0200, Thomas Petazzoni wrote:
> On Sat, 22 May 2010 10:33:24 +0200
> Thomas <tokant@gmx.net> wrote:
> 
> > > -HOST_CFLAGS+=-Wl,-rpath -Wl,$(HOST_DIR)/usr/lib
> > > +HOST_LDFLAGS+=-Wl,-rpath -Wl,$(HOST_DIR)/usr/lib
> > 
> > yes it works :-)
> 
> Ok, I will try to see if it still fixes the problem that the commit was
> originally fixing.

I noticed the same problem, as described in bug report 1789: When it
comes to root file generation (rootfs.ext2), buildroot terminates with
the following messages:

rm -f /media/disk/br1005rc2/buildroot-2010.05-rc2/output/build/_fakeroot.fs
touch /media/disk/br1005rc2/buildroot-2010.05-rc2/output/build/.fakeroot.00000
cat /media/disk/br1005rc2/buildroot-2010.05-rc2/output/build/.fakeroot* > /media/disk/br1005rc2/buildroot-2010.05-rc2/output/build/_fakeroot.fs
echo "chown -R 0:0 /media/disk/br1005rc2/buildroot-2010.05-rc2/output/target" >> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/build/_fakeroot.fs
echo "/media/disk/br1005rc2/buildroot-2010.05-rc2/output/host/usr/bin/makedevs -d target/device/Atmel/root/device_table.txt /media/disk/br1005rc2/buildroot-2010.05-rc2/output/target" >> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/build/_fakeroot.fs
echo "	PATH="/media/disk/br1005rc2/buildroot-2010.05-rc2/output/toolchain/bin:/media/disk/br1005rc2/buildroot-2010.05-rc2/output/host/bin:/media/disk/br1005rc2/buildroot-2010.05-rc2/output/host/usr/bin:/media/disk/br1005rc2/buildroot-2010.05-rc2/output/host/usr/sbin/:/media/disk/br1005rc2/buildroot-2010.05-rc2/output/staging/bin:/media/disk/br1005rc2/buildroot-2010.05-rc2/output/staging/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" fs/ext2/genext2fs.sh -d /media/disk/br1005rc2/buildroot-2010.05-rc2/output/target  -U /media/disk/br1005rc2/buildroot-2010.05-rc2/output/images/rootfs.ext2" >> /media/disk/br1005rc2/buildroot-2010.05-rc2/output/build/_fakeroot.fs
chmod a+x /media/disk/br1005rc2/buildroot-2010.05-rc2/output/build/_fakeroot.fs
/media/disk/br1005rc2/buildroot-2010.05-rc2/output/host/usr/bin/fakeroot -- /media/disk/br1005rc2/buildroot-2010.05-rc2/output/build/_fakeroot.fs
fakeroot: preload library not found, aborting.
make: *** [/media/disk/br1005rc2/buildroot-2010.05-rc2/output/images/rootfs.ext2] Error 1

Thanks, Thomas.

      reply	other threads:[~2010-05-24 18:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21  6:19 [Buildroot] buildroot-2010.05-rc2, problem with binutils-2.20.1 Thomas
2010-05-21  9:09 ` Ludger Keilig
2010-05-21  9:53   ` Thomas Petazzoni
2010-05-21 10:25 ` Thomas Petazzoni
     [not found]   ` <1274479497.25288.3.camel@bernd-desktop>
2010-05-21 22:30     ` Thomas Petazzoni
2010-05-22  8:33       ` Thomas
2010-05-22 12:55         ` Thomas Petazzoni
2010-05-24 18:10           ` Thomas [this message]

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=1274724609.13140.8.camel@bernd-desktop \
    --to=tokant@gmx.net \
    --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