From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] build root error with nofpu
Date: Wed, 17 Jan 2007 19:18:55 +0100 [thread overview]
Message-ID: <20070117181855.GB29900@aon.at> (raw)
In-Reply-To: <005501c739d4$a189ef90$0696a8c0@Thomas>
On Wed, Jan 17, 2007 at 09:03:13AM +0800, thomas.luo wrote:
>[root at localhost buildroot]# make
>
>Checking build system dependencies:
>CC clean: Ok
>CXX clean: Ok
>CPP clean: Ok
>CFLAGS clean: Ok
>CXXFLAGS clean: Ok
>sed works: Ok
>which installed: Ok
>GNU make version '3.80': Ok
>C compiler '/usr/bin/gcc'
>C compiler version '3.4.6': Ok
>bison installed: Ok
>flex installed: Ok
>gettext installed: Ok
>Build system dependencies: Ok
>
>make -C /mnt/rootbb/buildroot/toolchain_build_arm_nofpu/uClibc \
> PREFIX= \
> DEVEL_PREFIX=/mnt/rootbb/buildroot/build_arm_nofpu/staging_dir/ \
> RUNTIME_PREFIX=/mnt/rootbb/buildroot/build_arm_nofpu/staging_dir/ \
> install_runtime install_dev
>make[1]: Entering directory
>`/mnt/rootbb/buildroot/toolchain_build_arm_nofpu/uClibc'
>install -d /mnt/rootbb/buildroot/build_arm_nofpu/staging_dir/lib
>install -m 644 lib/lib*-0.9.29.so \
> /mnt/rootbb/buildroot/build_arm_nofpu/staging_dir/lib
>install: cannot stat `lib/lib*-0.9.29.so': No such file or directory
do a rm -rf build_arm_nofpu/* toolchain_build_arm_nofpu/*
then make sure that your BR2_JLEVEL=1 and invoke "make" again and paste
the first error you get.
Providing your .config and the uclibc.config would help, too.
next prev parent reply other threads:[~2007-01-17 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 1:03 [Buildroot] build root error with nofpu thomas.luo
2007-01-17 18:18 ` Bernhard Fischer [this message]
2007-01-19 6:56 ` thomas.luo
-- strict thread matches above, loose matches on Subject: below --
2007-01-19 6:57 thomas.luo
2007-01-19 14:41 ` Bernhard Fischer
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=20070117181855.GB29900@aon.at \
--to=rep.dot.nop@gmail.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