From: Matt Darland <mdarland@pager.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libusb and libusb-compat: conflict
Date: Wed, 10 Sep 2008 11:18:55 -0500 [thread overview]
Message-ID: <200809101118.55264.mdarland@pager.net> (raw)
In-Reply-To: <48C7CA95.2040708@dls.net>
FYI, libusb1 is broken on 2.6.26 kernels. If it tries to use sysfs, then it
will expect every USB device to have a 'descriptors' file in sysfs, but that
isn't necessarily the case in recent kernels.
http://sourceforge.net/mailarchive/message.php?msg_name=20080731112725.55310%40gmx.net
On Wednesday 10 September 2008 08:24:37 am Mike (mwester) wrote:
> Koen Kooi wrote:
> ...
>
> > Some background: libusb1 is the rewrite of libusb which brings up
> > goodness as better performance and more powersaving, but its ABI is
> > incompatible with libusb. That is why the libusb people create
> > libusb-compat, it's a drop-in replacement for libusb.
> >
> > When I added it to OE I made sure the runtime situation worked and
> > changed all packages to libusb-compat. It seems I missed a few.
>
> Grep comes up with a bunch, but probably a lot of those are just older
> recipes -- dfu-util and openocd are definitely broken, though.
>
> > It should be safe to change everything over to libusb-compat, unless
> > your favourite apps abuses private libusb API (as gnuradio does).
>
> I encountered simple linker failures (symbols not found). I'll get rid
> of libusb out of staging entirely and see if dfu-util and openocd will
> link correctly against libusb-compat. I can test dfu-util, but I hope
> someone else can test openocd.
>
> > And there's no such thing as CONFLICTS in OE, only RCONFLICTS.
>
> Bummer. That would mean that we would need to switch to
> "virtual/libusb" I guess. That seems a lot of effort for something
> that's obsolete -- it might be better to warn people if libusb is being
> built instead of libusb-compat. I wonder if this might be a use case
> for a "WARNING" metadata item in a bitbake recipe.
>
> I will do nothing with any metadata then except attempt to build
> dfu-util and openocd with libusb-compat.
>
> > regards,
> >
> > Koen
>
> Mike (mwester)
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2008-09-10 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 1:22 libusb and libusb-compat: conflict Mike (mwester)
2008-09-10 2:30 ` Philip Balister
2008-09-10 8:47 ` Koen Kooi
2008-09-10 11:24 ` Philip Balister
2008-09-10 13:24 ` Mike (mwester)
2008-09-10 16:18 ` Matt Darland [this message]
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=200809101118.55264.mdarland@pager.net \
--to=mdarland@pager.net \
--cc=openembedded-devel@lists.openembedded.org \
/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