public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: cygport i686/x86 library build undefined type in sys/stat.h
Date: Fri, 14 May 2021 22:16:26 -0600	[thread overview]
Message-ID: <08857c84-dbfe-8bf4-f7f8-40f64a3edda0@SystematicSw.ab.ca> (raw)

Trying to build latest libssh2 1.9.0 using cygport, works under x86_64,
but under i686/x86 fails with:

In file included from */usr/i686-pc-cygwin/include/sys/stat.h*:22,
                  from ...:
/usr/include/cygwin/stat.h:27:3: error: unknown type name ‘timestruc_t’
    27 |   timestruc_t   st_atim;
       |   ^~~~~~~~~~~

The equivalent include path to */usr/i686-pc-cygwin/include/sys/stat.h*
does not exist under 64 bit as /usr/x86_64-pc-cygwin/include,
and cygcheck -f does not come up with a hit.

The only obvious work around the timeframe of these files appears to be a
local test newlib-cygwin build and install for format_proc_cpuinfo and
format_proc_swaps testing:

$ head -v /proc/version
==> /proc/version <==
CYGWIN_NT-10.0-19042-WOW64 version 3.2.1-340.i686 (...@...) (gcc version 10.2.0 (GCC) ) 2021-04-30 12:55 UTC

Has anyone any idea, from seeing anything similar happen on their installs,
where this directory and these files may have come from,
what may have installed them, and whether it is likely to be safe to
rename or remove them?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

             reply	other threads:[~2021-05-15  4:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15  4:16 Brian Inglis [this message]
2021-05-15  6:01 ` Marco Atzeri
2021-05-15  7:55   ` Marco Atzeri
2021-05-15 13:36 ` Ken Brown

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=08857c84-dbfe-8bf4-f7f8-40f64a3edda0@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).