On 13/06/2017 01:18, Chris Johnson wrote:
Hi.
Never run into this before. Running Win7 and installing cygwin via
setup-x86_64 v2.879.
I kept running into categories I couldn't install due to a missing
libUSB-W32 driver. Some of the categories are
Devel
Math
Net
Publishing
Python
I get an er
Hi.
Never run into this before. Running Win7 and installing cygwin via
setup-x86_64 v2.879.
I kept running into categories I couldn't install due to a missing
libUSB-W32 driver. Some of the categories are
Devel
Math
Net
Publishing
Python
I get an error about libusb0, says I need to insta
libusb-win32 package has been
split into separate runtime and devel packages. libusb1.0 has been
switched to the libusbx fork, following the lead of several Linux
distros, as development of the original upstream has seemingly ceased.
--
Yaakov
Cygwin/X
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO
Version 1.2.5.0-1 of "libusb-win32" has been uploaded.
This is a new upstream release, the filter installer is not shipped any
more as it does not build on cygwin any more.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win9
At 02:37 2009-07-10 +0200, you wrote:
>At 00:08 2009-07-10 +0100, you wrote:
>>> During Cygwin Setup noticed system crash, while setup screen displayed
>>> something like:
>>> Running preremove script libusb-win32
>>> Attempting to isolate the problem I
At 00:08 2009-07-10 +0100, you wrote:
>> During Cygwin Setup noticed system crash, while setup screen displayed
>> something like:
>> Running preremove script libusb-win32
>> Attempting to isolate the problem I told setup to keep the current version
>> of li
Larry Hall (Cygwin) wrote:
> On 07/09/2009, Arend-Jan Westhoff wrote:
>> 3. Who drove Igor Peshansky away? (So we may lynch him and bring Igor
>> back.)
>
> That would be me but I won't tell you my name or where to find me...
>
> Oh rats! Looks like I'm going to have to go hide with Igor.
> But
On 07/09/2009, Arend-Jan Westhoff wrote:
3. Who drove Igor Peshansky away? (So we may lynch him and bring Igor back.)
That would be me but I won't tell you my name or where to find me...
Oh rats! Looks like I'm going to have to go hide with Igor.
But wait, where's Igor?... Now I'm really scr
Arend-Jan Westhoff wrote:
> During Cygwin Setup noticed system crash, while setup screen displayed
> something like:
> Running preremove script libusb-win32
> Attempting to isolate the problem I told setup to keep the current version
> of libusb-win32 and setup installed
On 08/07/2009 04:20, Samuel Thibault wrote:
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP).
What about 64-bit Windows? Is a 64-bit driver available somewhere?
It is derived from and fully API compatible to l
Version 0.1.12.2-1 of "libusb-win32" has been uploaded.
This is a new upstream release, handles composite device interfaces.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP).
It is derived from and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Apparently the linux version of libusb ships with a libusb.pc pkg-config
file. Packages use it to determine if libusb is installed, but
libusb-win32 package is missing it.
Could something like the attached be added to libusb-win32?
Yaakov
On 4/22/07, Samuel Thibault wrote:
Dave Korn, le Mon 23 Apr 2007 02:43:41 +0100, a écrit :
> Or you could follow the model of the ioperm package, which requires you to
> manually run "ioperm -i" to install the .sys file.
>
Brian Dessent, le Sun 22 Apr 2007 18:44:50 -0700, a écrit :
> I think i
Dave Korn, le Mon 23 Apr 2007 02:43:41 +0100, a écrit :
> Or you could follow the model of the ioperm package, which requires you to
> manually run "ioperm -i" to install the .sys file.
>
Brian Dessent, le Sun 22 Apr 2007 18:44:50 -0700, a écrit :
> I think it would be very bad to install a (ker
Samuel Thibault wrote:
> Yes of course (I actually call the uninstallation script at preremove).
> But the question is "do we dare installing a driver just because the
> user asked for package installation?".
>
> The problem is that libusb-win32 might be pulled as
On 23 April 2007 02:33, Samuel Thibault wrote:
> Yes of course (I actually call the uninstallation script at preremove).
> But the question is "do we dare installing a driver just because the
> user asked for package installation?".
>
> The problem is that libusb-w
stall script,
> for example.
Yes of course (I actually call the uninstallation script at preremove).
But the question is "do we dare installing a driver just because the
user asked for package installation?".
The problem is that libusb-win32 might be pulled as a dependency of
anot
Samuel Thibault wrote:
> Hi,
>
> Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit :
>> A good reason for this division is to allow for user input during the
>> configuration step, which "setup.exe" doesn't have support for.
>
> It doesn't need user input.
>
>> If running your libu
On 23 April 2007 00:16, Morgan Gangwere wrote:
> On 4/22/07, Samuel Thibault wrote:
On 22 April 2007 14:49, Morgan Gangwere wrote:
> On 4/22/07, Brian Dessent wrote:
On 22 April 2007 15:45, Morgan Gangwere wrote:
> On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
:-) Thank you Morgan!
/
well, heres a bright idea.
why not simply have a second package like "libusb-win32-autoinstall"
that was just a postinstall script that ran the install?
just a thought :D
--
Morgan gangwere
"Space does not reflect society, it expresses it." -- Castells, M.,
Space of Flow
Samuel Thibault wrote:
> Hi,
>
> Installing my libusb-win32 package doesn't automatically install the USB
> driver, the user has to run /usr/sbin/libusb-install. I preferred to go
> this way for safety.
>
> However, some user reported that it would be better
Hi,
Installing my libusb-win32 package doesn't automatically install the USB
driver, the user has to run /usr/sbin/libusb-install. I preferred to go
this way for safety.
However, some user reported that it would be better that the
installation is automatically performed (since if one ins
Hi,
Larry Hall (Cygwin), le Sun 22 Apr 2007 11:14:07 -0400, a écrit :
> A good reason for this division is to allow for user input during the
> configuration step, which "setup.exe" doesn't have support for.
It doesn't need user input.
> If running your libusb-install is more like a configuratio
Hi,
Morgan Gangwere, le Sun 22 Apr 2007 08:44:55 -0600, a écrit :
> On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
> >Installing my libusb-win32 package doesn't automatically install the USB
> >driver, the user has to run /usr/sbin/libusb-install. I preferred to go
On 4/22/07, Samuel Thibault ens-lyon.org> wrote:
Hi,
Installing my libusb-win32 package doesn't automatically install the USB
driver, the user has to run /usr/sbin/libusb-install. I preferred to go
this way for safety.
However, some user reported that it would be better that the
inst
Maurits Kooiman wrote:
> I used your libusb-win32 (the testlibusb worked).
> mine linker couldnt find the usb functions.
>
> Do you have any idea where to look?
>
> Regards
> Maurits Kooiman
>
> Result of the make-file:
>
> make -k all
> Building
Dear Reader,
I used your libusb-win32 (the testlibusb worked).
mine linker couldnt find the usb functions.
Do you have any idea where to look?
Regards
Maurits Kooiman
Result of the make-file:
make -k all
Building file: ../main.cpp
Invoking: GCC C++ Compiler
g++ -O3 -Wall -c -fmessage
Dear Reader,
I used your libusb-win32 (the testlibusb worked).
mine linker couldnt find the usb functions.
Do you have any idea where to look?
Regards
Maurits Kooiman
Result of the make-file:
make -k all
Building file: ../main.cpp
Invoking: GCC C++ Compiler
g++ -O3 -Wall -c -fmessage
Samuel,
Just confirming that this release solves my problem reported in
http://cygwin.com/ml/cygwin/2007-03/msg00718.html .
Many thanks for fixing this.
Ton van Overbeek
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Doc
Version 0.1.12.1-2 of "libusb-win32" has been uploaded.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP).
It is derived from and fully API compatible to libusb available at
http://libusb.sourceforge.ne
t; > > libusb-install, to just copy it into c:\windows\system32\drivers\ and
> > > > then use the usual libusb-win32 filter setup? That works fine and
> > > > actually makes the patch simpler...
> > >
> > > I am pretty sure that would solve
On Mar 24 20:21, Samuel Thibault wrote:
> > > Actually, I'm wondering: instead of trying to make libusb0.sys work
> > > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in
> > > libusb-install, to just copy it into c:\windows\system32\drivers\ and
>
ying to make libusb0.sys work
> > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in
> > libusb-install, to just copy it into c:\windows\system32\drivers\ and
> > then use the usual libusb-win32 filter setup? That works fine and
> > actually makes the patch simple
uclass.sys
> Actually, I'm wondering: instead of trying to make libusb0.sys work
> from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in
> libusb-install, to just copy it into c:\windows\system32\drivers\ and
> then use the usual libu
ual discovery fails.
Actually, I'm wondering: instead of trying to make libusb0.sys work
from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in
libusb-install, to just copy it into c:\windows\system32\drivers\ and
then use the usual libusb-win32 filter setup? That works fine and
act
I believe I found the cause of the problem.
When running cygcheck on /usr/lib/libusb/libusb0.sys I get this:
$ cygcheck /usr/lib/libusb/libusb0.sys
c:/Cygwin/lib/libusb/libusb0.sys
Error: could not find usbd.sys <
C:\WINDOWS\system32\ntoskrnl.exe
C:\WINDOWS\system32\BOOTVID.dll
Ton van Overbeek, le Fri 23 Mar 2007 16:56:48 +0100, a écrit :
> Yes, Installed 0.1.10.1-3 after removing 0.1.12.1-1 and it works fine.
Ok, so people can use that one instead for the few coming days until I
fix the issue.
> Also there is now an /usr/lib/libusb/install-filter.exe which did not
> e
On Fri, 23 Mar 2007, Samuel Thibault wrote:
> Hi,
>
> Ton van Overbeek, le Fri 23 Mar 2007 15:18:24 +0100, a écrit :
> > I have problems with the libusb-win32-0.1.12.1-1 Cygwin package.
>
> Just to make sure, does the old 0.1.10.1-3 work fine?
>
Yes, Installed 0.1.10.1-3
Hi,
Ton van Overbeek, le Fri 23 Mar 2007 15:18:24 +0100, a écrit :
> I have problems with the libusb-win32-0.1.12.1-1 Cygwin package.
Just to make sure, does the old 0.1.10.1-3 work fine?
> My guess is that /usr/sbin/libusb-install omits some crucial step
> (registry? kernel servic
I have problems with the libusb-win32-0.1.12.1-1 Cygwin package.
Installation went fine. After running /usr/sbin/libusb-install the test
program worked OK and also my own libusb based program worked fine.
The real problem started after the following reboot.
The /usr/sbin/libusb-install installs
Version 0.1.12.0-1 of "libusb-win32" has been uploaded.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP).
It is derived from and fully API compatible to libusb available at
http://libusb.sourceforge.ne
Version 0.1.10.1-3 of "libusb-win32" has been uploaded.
It is a library that allows userspace application to access USB
devices on Windows operation systems (Win98SE, WinME, Win2k, WinXP).
It is derived from and fully API compatible to libusb available at
http://libusb.sourceforge.ne
42 matches
Mail list logo
