All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8846] New: Orphaned/missing toolchain borks eclipse plugin
Date: Wed, 13 Apr 2016 12:21:38 +0000	[thread overview]
Message-ID: <bug-8846-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=8846

            Bug ID: 8846
           Summary: Orphaned/missing toolchain borks eclipse plugin
           Product: buildroot
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: subwooferbone at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Using latest Buildroot Eclipse plugin.

Importing CDT project from another user, all build targets are gone. Eclipse
complains "An error has occurred. See error log for more details.
java.lang.NullPointerException".

C/C++ Build and C/C++ General pages of project properties are borked, null
pointers galore. 

Same behaviour with both Mars and Luna. Uninstalling the plugin makes the C/C++
options pages work again, but it is impossible to select another toolchain for
the projects defined with buildroot toolchains. Then complains about orphaned
toolchain.

Message sent to stderr: "Managed Build system manifest file error: Option
org.buildroot.home.bob.software_PI1509.platform.buildroot.output..toolchain.base.option.path.1204713667
uses a null category that is invalid in its context. The option was ignored."

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2016-04-13 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 12:21 bugzilla at busybox.net [this message]
2016-10-15 15:25 ` [Buildroot] [Bug 8846] Orphaned/missing toolchain borks eclipse plugin 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-8846-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 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.