On Thu, May 3, 2012 at 6:56 PM, Pete Batard wrote:
> On 2012.05.03 02:47, Xiaofan Chen wrote:
>> Also Tim's view on this topic in the OSR mailing list / forum.
>> http://www.osronline.com/showthread.cfm?link=223812
>> +++
>> One can also argue that this is a security measure. The USB spec
>>
Somehow there is no source command by default under
OpenBSD. I am wondering maybe it is better just use
"./bootstrap.sh" than "source bootstrap.sh".
bash-4.2$ ./autogen.sh
./autogen.sh[2]: source: not found
./autogen.sh[3]: ./configure: not found
--
Xiaofan
-
On Thu, 3 May 2012 23:32:22 +0100, Pete Batard said:
>>> +#elif defined(__APPLE__)
>>> + ret = mach_thread_self();
>>> + mach_port_deallocate(mach_task_self(), ret);
>>
>> Perhaps I missed an earlier discussion, but why drop to the mach
>level? Wouldn't pthread_self() be more portable?
>
>The
2012/5/4 Xiaofan Chen :
> Somehow there is no source command by default under
> OpenBSD. I am wondering maybe it is better just use
> "./bootstrap.sh" than "source bootstrap.sh".
>
> bash-4.2$ ./autogen.sh
> ./autogen.sh[2]: source: not found
> ./autogen.sh[3]: ./configure: not found
source looks
script is valid for bash but not any /bin/sh
Thanks to Xiaofan Chen for the bug report
http://sourceforge.net/mailarchive/message.php?msg_id=29217871
---
autogen.sh |2 +-
libusb/version.h |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/autogen.sh b/autogen.sh
Some fixes for autogen.sh and bootstrap.sh
Ludovic Rousseau (3):
Do not use source to call an another script
Use "set -e" to exit on the first error
Use "$@" instead of $* to avoid spaces problems
autogen.sh |7 +--
bootstrap.sh |2 ++
libusb/version.h |2 +-
3 fi
The script will not continue if something fails (like a command not found)
---
autogen.sh |3 +++
bootstrap.sh |2 ++
libusb/version.h |2 +-
3 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/autogen.sh b/autogen.sh
index a4b87e4..906251a 100755
--- a/autogen.sh
"$@" will correctly handle arguments with spaces
---
autogen.sh |2 +-
libusb/version.h |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/autogen.sh b/autogen.sh
index 906251a..1a4c75f 100755
--- a/autogen.sh
+++ b/autogen.sh
@@ -3,4 +3,4 @@
set -e
./bootstrap
2012/5/1 Pete Batard :
> By the way, do you still consider the update of version.h and the
> running of autotools that results as something you want to see fixed? As
> I said, we can move the nano into its own nano.h to avoid the issue, but
> I'm not sure of how important you or anybody else sees t
Janko Kolar wrote:
> I am new to libusbx and I have one basic question
>
> I would like to determine to which usb port particular device is attached.
Why? Of what possible use is this information? USB hubs are not
externally labeled. If I tell you "you are in port 3", what good does
that do you
On 4 May 2012 17:25, Ludovic Rousseau wrote:
> It is impossible to apply (using git am) a
> serie of patches if the LIBUSB_NANO has been modified between the
> patch serie generation and the patch serie applying.
Well, the idea is that unless a libusbx maintainer was the one who
created the patch
On 4 May 2012 15:29, Sean McBride wrote:
> Do you necessarily need an integer to display?
I meant integer in the mathematical sense, not the C sense (else I
would have used "int").
> You could also print the address of the pthread_t struct
Which would be an integer alright, so why not... Not s
On Fri, 4 May 2012 23:17:21 +0100, Pete Batard said:
>> or use pthread_getname_np() to get a string name of the thread (though
>that's only available on 10.6 and later, and the 'np' means 'not portable').
>
>Wouldn't that mean that OS-X would have different logging from other
>platforms?
Seems it
Now pushed to mainline.
Regards,
/Pete
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
wil
On 2012.05.04 23:44, Sean McBride wrote:
>> Wouldn't that mean that OS-X would have different logging from other
>> platforms?
>
> Seems it already does, no? Not all platforms have mach threads after all.
I'm talking about the log output. With the proposal, all platforms
return an int => the lib
15 matches
Mail list logo
