From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin-apps@cygwin.com>
Subject: [ITA] mhash
Date: Wed, 10 Nov 2021 21:36:10 -0500 [thread overview]
Message-ID: <00b001d7d6a4$e481c750$ad8555f0$@pdinc.us> (raw)
Sigh… some old and crusty files…. - x86 - 0.9.9.9-2 (source) from 2015-02-18 22:18 does not work...
I pushed the fixed mhash
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/playground.git;a=commitdiff;h=8e7f3a747287f0263bcd1316dedf7ea974914077
https://github.com/cygwin/scallywag/actions/runs/1447027874
While trying to package AIDE for x86,
In file included from /usr/include/mhash.h:6,
from /cygdrive/c/projects/aide/aide-0.17.3-1.i686/src/aide-0.17.3/include/db_config.h:87,
from /cygdrive/c/projects/aide/aide-0.17.3-1.i686/src/aide-0.17.3/include/aide.h:27,
from /cygdrive/c/projects/aide/aide-0.17.3-1.i686/src/aide-0.17.3/src/report.c:23:
/usr/include/mutils/mincludes.h:82:10: fatal error: values.h: No such file or directory
82 | #include <values.h>
| ^~~~~~~~~~
compilation terminated.
make[1]: *** [Makefile:739: src/report.o] Error 1
make[1]: Leaving directory '/cygdrive/c/projects/aide/aide-0.17.3-1.i686/build'
make: *** [Makefile:510: all] Error 2
*** ERROR: make failed
So it looks like the x86 build and package of mhash found a windows development kit on the path…
Rebuilding and repackaging it allows
>>> Checking packages for unexpected, missing or duplicate files
>>> Creating source patches
include/util.h | 1 +
1 file changed, 1 insertion(+)
>>> Creating source package
aide-0.17.3-1.src/
aide-0.17.3-1.src/aide-0.17.3-1.src.patch
aide-0.17.3-1.src/aide-0.17.3.tar.gz
aide-0.17.3-1.src/aide-0.17.3.tar.gz.asc
aide-0.17.3-1.src/aide.cygport
>>> aide requires: cygwin libmhash2 libpcre1 zlib0 cygwin libmhash2 libpcre1 zlib0
next reply other threads:[~2021-11-11 2:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 2:36 Jason Pyeron [this message]
2021-11-11 19:08 ` 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='00b001d7d6a4$e481c750$ad8555f0$@pdinc.us' \
--to=jpyeron@pdinc.us \
--cc=cygwin-apps@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).