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 755] New: Add Boost libraries as a package
Date: Wed,  2 Dec 2009 08:00:56 +0000 (UTC)	[thread overview]
Message-ID: <bug-755-163@https.bugs.busybox.net/> (raw)

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

           Summary: Add Boost libraries as a package
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: jpihl at nevion.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=787)
 --> (https://bugs.busybox.net/attachment.cgi?id=787)
Boost 1.35 package for buildroot

The attached package builds Boost 1.35, which is getting rather old. Boost uses
a rather tricky build system for the compiled libraries (most are headers only,
i.e. no problem), so updating the package to a later version may not be
straight ahead.

Known issues: atomic_add32() and atomic_cas32() are set to abort if called on
ARM, we have never seen them be called.


-- 
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-12-02  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02  8:00 bugzilla at busybox.net [this message]
2010-02-21 22:33 ` [Buildroot] [Bug 755] Add Boost libraries as a package bugzilla at busybox.net
2012-02-03 13:34 ` 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-755-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.