From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10151] New: toolchain eclipse register : fails with a custom BR2_HOST_DIR
Date: Thu, 03 Aug 2017 09:25:50 +0000 [thread overview]
Message-ID: <bug-10151-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10151
Bug ID: 10151
Summary: toolchain eclipse register : fails with a custom
BR2_HOST_DIR
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: frederic.mathieu at dualis.com
CC: buildroot at uclibc.org
Target Milestone: ---
The toolchain registering fails when a custom HOST directory is defined.
the script './support/scripts/eclipse-register-toolchain' returns message :
"Your project directory does not look like a Buildroot output"
tested with versions 2017.02.(n), 2017.05.2
in my case,
BR2_HOST_DIR="$(BASE_DIR)/../../../toolchain/2107.02.3_X86_32/host"
also tested with absolute path :
/home/dev01/data/toolchain/2107.02.3_X86_32/host"
...
./support/scripts/eclipse-register-toolchain `readlink -f
/home/dev01/data/projects/buildroot-2017.02.3_X86_32/output`
i686-buildroot-linux-gnu- "i686"
Your project directory does not look like a Buildroot output
Makefile:655: recipe for target 'target-finalize' failed
make[1]: *** [target-finalize] Error 1
Makefile:79: recipe for target '_all' failed
make: *** [_all] Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-08-03 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 9:25 bugzilla at busybox.net [this message]
2017-08-03 21:29 ` [Buildroot] [Bug 10151] toolchain eclipse register : fails with a custom BR2_HOST_DIR bugzilla at busybox.net
2017-08-04 7:03 ` bugzilla at busybox.net
2017-08-04 7:38 ` bugzilla at busybox.net
2017-08-04 16:43 ` bugzilla at busybox.net
2018-04-01 10:16 ` bugzilla at busybox.net
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=bug-10151-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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