-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix empty else in configure script #16
Conversation
Which version of MSYS2 installation? From MSYS2 I can see no patch is needed for libusb-compat-git package. |
I'm using msys2-x86_64-20210105. It may be due to me building in MSYS2 MSYS system, which I understand is more POSIX than mingw-w64 and has a different compiler toolchain. |
Just wondering why you need to build under MSys2 MSys subsystem. |
I am building a fork of AVARICE, GDB debug server for AVR micros. It uses termios.h and maybe some other POSIX APIs which are not available under Windows without MSYS or Cygwin. It also uses the old libusb 0.1 APIs so the cleanest way that I found to get everything working is to build libusb 1.0 and this compatibility layer from source under MSYS2, after which avarice itself can be built. |
Dear @libusb team, It is possible to look this PR? |
As it is this pull request can not be accepted. @Florin-Popescu Can you remove the Debian stuff and update the pull request. Thanks. @tormodvolden and @hjelmn |
7ca89c0
to
e322761
Compare
Cleaned it up. Should've used a branch for the PR, didn't realize that my changes were making it into here. |
Strange that CI build failed. |
It failed on macOS from what I remember because of an error finding some tool with homebrew. But it looks like it can't retrieve the build logs anymore. It was a long time ago... Is it possible to retrigger the CI build? |
@Florin-Popescu |
@Florin-Popescu BTW, the failure on the msys2 build is my msys2.yml problem -- I have not figured out what the issue is. |
It seems to be okay so I will take the liberty to merge this one. |
Hello!
After running bootstrap.sh on my MSYS2 installation, the configure script couldn't be run due to a syntax error with an empty else.
I tracked it down to the $5 which I removed in this commit. With it removed, it builds for me successfully.
Don't know how this was supposed to be used. If it's in fact needed please tell me how to fix it and remove this pull request.