From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001582]: libusb tries to build c++ library even if compiler not available
Date: Fri, 9 Nov 2007 01:28:14 -0800 [thread overview]
Message-ID: <d0a4c8762bf35ac7181e3d4bb3690915@busybox.net> (raw)
The following issue has been CLOSED
======================================================================
http://busybox.net/bugs/view.php?id=1582
======================================================================
Reported By: hmoffatt
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1582
Category: Other
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 11-08-2007 19:03 PST
Last Modified: 11-09-2007 01:28 PST
======================================================================
Summary: libusb tries to build c++ library even if compiler
not available
Description:
libusb tries to build a C++ library (libusbpp) even if cross-g++ is not
available. It actually tries to use the host compiler, then complains
about mixing objects from the host and target platforms at link time.
My fix was to disable the C++ library and also the test suite which uses
it, in the attached patch. There doesn't seem to be a configure option in
libusb to disable that more cleanly.
======================================================================
----------------------------------------------------------------------
vanokuten - 11-09-07 01:27
----------------------------------------------------------------------
Applied, thanks! in r20389
----------------------------------------------------------------------
vanokuten - 11-09-07 01:28
----------------------------------------------------------------------
fixed in r20389
Issue History
Date Modified Username Field Change
======================================================================
11-08-07 19:03 hmoffatt New Issue
11-08-07 19:03 hmoffatt Status new => assigned
11-08-07 19:03 hmoffatt Assigned To => buildroot
11-08-07 19:03 hmoffatt File Added: br-libusb-cpp.mk
11-09-07 01:27 vanokuten Note Added: 0002899
11-09-07 01:28 vanokuten Status assigned => closed
11-09-07 01:28 vanokuten Note Added: 0002900
======================================================================
next reply other threads:[~2007-11-09 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 9:28 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-09 9:27 [Buildroot] [buildroot 0001582]: libusb tries to build c++ library even if compiler not available bugs at busybox.net
2007-11-09 3:03 bugs 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=d0a4c8762bf35ac7181e3d4bb3690915@busybox.net \
--to=bugs@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