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 387] New: Tremor not installed to toolchain
Date: Tue,  9 Jun 2009 15:22:03 +0000 (UTC)	[thread overview]
Message-ID: <bug-387-163@https.bugs.busybox.net/> (raw)

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

              Host: linux
            Target: mipsel-linux
           Summary: Tremor not installed to toolchain
           Product: buildroot
           Version: unspecified
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: evan.zelkowitz at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


When selecting tremor usage for vorbis it installs into the root fs properly
but it is not being installed into the toolchain, so everything still gets
built against libvorbis instead of tremor.


-- 
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:[~2009-06-09 15:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 15:22 bugzilla at busybox.net [this message]
2009-07-16 19:49 ` [Buildroot] [Bug 387] Tremor not installed to toolchain bugzilla at busybox.net
2009-07-21 12:00 ` bugzilla at busybox.net
2009-07-22  6:02 ` bugzilla at busybox.net
2009-07-22 10:22 ` bugzilla at busybox.net
2009-07-22 15:02 ` bugzilla at busybox.net
2009-07-22 15:04 ` bugzilla at busybox.net
2010-02-21 18:51 ` bugzilla at busybox.net
2010-04-09 14:54 ` bugzilla at busybox.net
2010-07-18 20:35 ` 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-387-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