Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: a <anushka.parashar@tesco.com>
To: buildroot@busybox.net
Subject: [Buildroot] lshw package not getting added to the resulting image
Date: Thu, 14 Nov 2019 23:13:39 -0600 (CST)	[thread overview]
Message-ID: <1573794819086-0.post@n4.nabble.com> (raw)
In-Reply-To: <20191114202532.7bdd338b@gmx.net>

Hi!

I'm using buildroot-2019.02.6

PFA .config file and build.log

*.config file* is the file before I set BR2_PACKAGE_LSHW=y, and

*build.log file* is the log after I set BR2_PACKAGE_LSHW=y and now it's
showing the following error while building lshw B.02.18 package:
make[1]:
/root/buildroot-hello/output/host/bin/x86_64-buildroot-linux-uclibc-g++:
Command not found
make[1]: *** [lshw.o] Error 127
make[1]: *** Waiting for unfinished jobs....
make[2]: Entering directory
`/root/buildroot-hello/output/build/lshw-B.02.18/src/core'
/root/buildroot-hello/output/host/bin/x86_64-buildroot-linux-uclibc-g++ -g
-Wall -g -I./core/ -DPREFIX=\"/usr\" -DSBINDIR=\"/usr/sbin\"
-DMANDIR=\"/usr/share/man\" -DDATADIR=\"/usr/share\" -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Os   -c hw.cc -o hw.o
make[2]:
/root/buildroot-hello/output/host/bin/x86_64-buildroot-linux-uclibc-g++:
Command not found
make[2]: *** [hw.o] Error 127
make[2]: Leaving directory
`/root/buildroot-hello/output/build/lshw-B.02.18/src/core'
make[1]: *** [core] Error 2
make[1]: Leaving directory
`/root/buildroot-hello/output/build/lshw-B.02.18/src'
make: *** [/root/buildroot-hello/output/build/lshw-B.02.18/.stamp_built]
Error 2




--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

  reply	other threads:[~2019-11-15  5:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 11:41 [Buildroot] lshw package not getting added to the resulting image a
2019-11-13 20:58 ` Peter Seiderer
2019-11-14  7:29   ` a
2019-11-14 19:25     ` Peter Seiderer
2019-11-15  5:13       ` a [this message]
2019-11-15 16:28         ` Peter Seiderer
2019-11-15 17:01           ` Carlos Santos
2019-11-16  8:53             ` Peter Seiderer
2019-11-18  6:41             ` a

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=1573794819086-0.post@n4.nabble.com \
    --to=anushka.parashar@tesco.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