Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Pham <andrew2007vn@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] Could not compile buildroot
Date: Thu, 10 May 2007 14:35:06 -0700 (PDT)	[thread overview]
Message-ID: <945223.44926.qm@web57415.mail.re1.yahoo.com> (raw)

Hello everybody,

I was trying to compile buildroot packages but it failed with error messages as below:

which: no sed in (/usr/bin)
which: no sed in (/usr/bin)
which: no sed in (/usr/bin)
if [ ! -e "/Development/buildroot/toolchain_build_arm_nofpu/bin/sed" ] ; then \
        mkdir -p "/Development/buildroot/toolchain_build_arm_nofpu/bin"; \
        rm -f "/Development/buildroot/toolchain_build_arm_nofpu/bin/sed"; \
        ln -sf "/bin/sed" "/Development/buildroot/toolchain_build_arm_nofpu/bin/sed"; \
fi

Checking build system dependencies:
CC clean:                                       Ok
CXX clean:                                      Ok
CPP clean:                                      Ok
CFLAGS clean:                                   Ok
INCLUDES clean:                                 Ok
CXXFLAGS clean:                                 Ok
which installed:                                Ok
which: no sed in (/usr/bin)
sed works:                                      Ok (/bin/sed)
GNU make version '3.80':                        Ok
C compiler '/usr/bin/gcc'
C compiler version '4.1.0':                     Ok
C++ compiler '/usr/bin/c++'
C++ compiler version '4.1.0':                   Ok
bison installed:                                Ok
flex installed:                                 Ok
gettext installed:                              Ok
makeinfo installed:                             Ok
Build system dependencies:                      Ok

make MAKE="make -j1" -C /Development/buildroot/toolchain_build_arm_nofpu/uClibc \
        PREFIX= \
        DEVEL_PREFIX=/ \
        RUNTIME_PREFIX=/ \
        HOSTCC="gcc" \
        all
arm-linux-uclibc-gcc: Y: No such file or directory
make[1]: Entering directory `/Development/buildroot/toolchain_build_arm_nofpu/uClibc'
arm-linux-uclibc-gcc: Y: No such file or directory
make[2]: `conf' is up to date.
arm-linux-uclibc-gcc: Y: No such file or directory
  AS ldso/ldso/arm/resolve.oS
arm-linux-uclibc-gcc: Y: No such file or directory
make[1]: *** [ldso/ldso/arm/resolve.oS] Error 1
make[1]: Leaving directory `/Development/buildroot/toolchain_build_arm_nofpu/uClibc'
make: *** [/Development/buildroot/toolchain_build_arm_nofpu/uClibc/lib/libc.a] Error 2

Have any of you seen this before? What should I do to fix it?

Thanks,
Andrew.

       
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20070510/ffda3a72/attachment.htm 

             reply	other threads:[~2007-05-10 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 21:35 Andrew Pham [this message]
2007-05-11 12:52 ` [Buildroot] Could not compile buildroot Bernhard Fischer
  -- strict thread matches above, loose matches on Subject: below --
2007-05-11 22:43 Jackie Pham

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=945223.44926.qm@web57415.mail.re1.yahoo.com \
    --to=andrew2007vn@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