From: Mark Constable <markc@renta.net>
To: buildroot@busybox.net
Subject: [Buildroot] x86_64 error2
Date: Fri, 31 Jul 2009 14:19:03 +1000 [thread overview]
Message-ID: <4A7270B7.3000308@renta.net> (raw)
Continuing on from the previous error with a manual make, uclibc
and gcc apparently built but the build ended with this error...
...
/home/sources/srcpkgs/eth-os/cli/buildroot/src/buildroot-2009.05/build_x86_64/makedevs-host
/usr/bin/gcc -Wall -Werror -O2 /home/sources/srcpkgs/eth-os/cli/buildroot/src/buildroot-2009.05/build_x86_64/makedevs-host/makedevs.c -o /home/sources/srcpkgs/eth-os/cli/buildroot/src/buildroot-2009.05/build_x86_64/makedevs-host/makedevs
/usr/bin/install -m 755 /home/sources/srcpkgs/eth-os/cli/buildroot/src/buildroot-2009.05/build_x86_64/makedevs-host/makedevs /home/sources/srcpkgs/eth-os/cli/buildroot/src/buildroot-2009.05/build_x86_64/host_dir/usr/bin/makedevs
make: /usr/bin/install: Command not found
make: *** [/home/sources/srcpkgs/eth-os/cli/buildroot/src/buildroot-2009.05/build_x86_64/host_dir/usr/bin/makedevs] Error 127
My Archlinux based hosts coreutils package installs "install"
as /bin/install. Sure I can make a softlink, but shouldn't the
buildroot procedure just use "install" from the $PATH?
--markc
next reply other threads:[~2009-07-31 4:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 4:19 Mark Constable [this message]
2009-07-31 6:49 ` [Buildroot] x86_64 error2 Thomas Petazzoni
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=4A7270B7.3000308@renta.net \
--to=markc@renta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.