Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7010] New: jamvm builds and runs fine under mips (be)
Date: Tue,  1 Apr 2014 09:09:56 +0000 (UTC)	[thread overview]
Message-ID: <bug-7010-163@https.bugs.busybox.net/> (raw)

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

           Summary: jamvm builds and runs fine under mips (be)
           Product: buildroot
           Version: 2014.02
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: alex at digriz.org.uk
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created attachment 5324
  --> https://bugs.busybox.net/attachment.cgi?id=5324
patch to buildroot to allow mips(be) build of jamvm

Although the website does not include this platform as 'supported', it seems to
work fine and can run the Netalyzr CLI tool[1] with no problems.

Attached a patch that gets it building and running.

[1] http://netalyzr.icsi.berkeley.edu/cli.html

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2014-04-01  9:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  9:09 bugzilla at busybox.net [this message]
2014-04-29 18:59 ` [Buildroot] [Bug 7010] jamvm builds and runs fine under mips (be) bugzilla at busybox.net
2014-05-07 17:15 ` bugzilla at busybox.net
2014-05-08 11:57 ` bugzilla at busybox.net
2014-05-16  8:01 ` bugzilla at busybox.net
2014-08-19 14:30 ` bugzilla at busybox.net
2014-09-02  8:43 ` bugzilla at busybox.net
2014-09-27 18:18 ` 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-7010-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