public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Building libusb1.0 from source fails (Attn maintainer)
Date: Sun, 02 Feb 2020 01:23:00 -0000	[thread overview]
Message-ID: <CAJ1FpuNQPc1F_haEmF5Jdd4q5MZ6si4adhUMjYBujNKmZYdkHw@mail.gmail.com> (raw)

Windows 10 Home
10.0.17763 Build 17763

$ uname -a
CYGWIN_NT-10.0 mars 3.1.2(0.340/5/3) 2019-12-21 15:25 x86_64 Cygwin

fully patched as of today (no test versions or snapshots installed)


Building libusb1.0 from source using

$ cygport libusb1.0.cygport download
$ cygport libusb1.0.cygport prep
$ cygport libusb1.0.cygport compile

fails with:

/usr/src/libusb1.0-1.0.21-1.src/libusb1.0-1.0.21-1.x86_64/src/libusb-1.0.21/libusb/io.c:
In function ‘usbi_io_init’:
/usr/src/libusb1.0-1.0.21-1.src/libusb1.0-1.0.21-1.x86_64/src/libusb-1.0.21/libusb/io.c:1167:2:
error: implicit declaration of function ‘close’; did you mean
‘_lclose’? [-Werror=implicit-function-declaration]
  close(ctx->timerfd);
  ^~~~~
  _lclose
cc1: some warnings being treated as errors

I also built with the latest upstream release, but that generates a
great many warnings, which I have not attempted to resolve.

Any guidance to resolve this is appreciated.

Doug

-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2020-02-02  1:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-02  1:23 Doug Henderson [this message]
2020-02-02  5:38 ` Marco Atzeri

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=CAJ1FpuNQPc1F_haEmF5Jdd4q5MZ6si4adhUMjYBujNKmZYdkHw@mail.gmail.com \
    --to=djndnbvg@gmail.com \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).