Skip to content
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

Merged
merged 1 commit into from
Oct 29, 2022
Merged

Conversation

Florin-Popescu
Copy link

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.

@mcuee
Copy link
Member

mcuee commented Feb 18, 2021

Which version of MSYS2 installation?

From MSYS2 I can see no patch is needed for libusb-compat-git package.
https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-libusb-compat-git/PKGBUILD

@mcuee mcuee added the Windows label Feb 18, 2021
@Florin-Popescu
Copy link
Author

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.

@mcuee
Copy link
Member

mcuee commented Feb 20, 2021

Just wondering why you need to build under MSys2 MSys subsystem.

@Florin-Popescu
Copy link
Author

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.

@Neustradamus
Copy link

Dear @libusb team,

It is possible to look this PR?

@mcuee
Copy link
Member

mcuee commented Oct 29, 2022

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
Please take a look at the configure script to see if it is acceptable or not. Thanks.

@Florin-Popescu
Copy link
Author

Cleaned it up. Should've used a branch for the PR, didn't realize that my changes were making it into here.

@mcuee
Copy link
Member

mcuee commented Oct 29, 2022

Strange that CI build failed.
Maybe we should add github action as well for Linux, macOS and MinGW.

@Florin-Popescu
Copy link
Author

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?

@mcuee
Copy link
Member

mcuee commented Oct 29, 2022

@Florin-Popescu
I have deleted the outdated Travis-CI build and created the Linux and macOS github action. Please push again to see if it triggers the github actions.

@mcuee
Copy link
Member

mcuee commented Oct 29, 2022

@Florin-Popescu
I've tested your pull request under my fork and it works fine for Linux and macOS github action build.

BTW, the failure on the msys2 build is my msys2.yml problem -- I have not figured out what the issue is.

@mcuee
Copy link
Member

mcuee commented Oct 29, 2022

It seems to be okay so I will take the liberty to merge this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants