From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: [scallywag] libksba-1.6.5-1 install anomaly
Date: Tue, 19 Dec 2023 06:29:29 +0100 [thread overview]
Message-ID: <e2e0eb82-a9b1-4f32-a2d1-7ede57507b41@gmail.com> (raw)
Hi Jon
on jobs 7426 and (rerun) 7428 I see that a file is built
but not installed
------------------------------------------
config.status: creating src/ksba-config
...
>>> libksba-devel-1.6.5-1.tar.xz
tar: usr/bin/ksba-config: Cannot stat: No such file or directory
------------------------------------------
but if I run exacly the same jobs locally, the file is installed and
packed as expected
$ find libksba-1.6.5-1.x86_64 -name ksba-config
libksba-1.6.5-1.x86_64/build/src/ksba-config
libksba-1.6.5-1.x86_64/inst/usr/bin/ksba-config
$ grep -H ksba-config libksba-1.6.5-1.x86_64/log/*
libksba-1.6.5-1.x86_64/log/libksba-1.6.5-1-compile.log:config.status:
creating src/ksba-config
libksba-1.6.5-1.x86_64/log/libksba-1.6.5-1-install.log: /usr/bin/install
-c ksba-config '/pub/devel/libksba/libksba-1.6.5-1.x86_64/inst/usr/bin'
libksba-1.6.5-1.x86_64/log/libksba-1.6.5-1-pkg.log:usr/bin/ksba-config
Any clue if I should add something to the
BUILD_REQUIRES="libgpg-error-devel pkg-config"
the only difference between system I can think about is
case Sensitive file system.
But I can not test it as my system loses some functionality
like network if I turn all the file system to be case sensitive
$ uname -svr
CYGWIN_NT-10.0-19045 3.4.10-1.x86_64 2023-11-29 12:12 UTC
Regards
Marco
next reply other threads:[~2023-12-19 5:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 5:29 Marco Atzeri [this message]
2023-12-19 11:24 ` Jon Turney
2023-12-19 18:15 ` Marco Atzeri
2023-12-19 16:01 ` [Attn. MAINTAINER] gpg2 ASSI
2023-12-19 18:12 ` Marco Atzeri
2023-12-19 21:38 ` [scallywag] libksba-1.6.5-1 install anomaly Brian Inglis
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=e2e0eb82-a9b1-4f32-a2d1-7ede57507b41@gmail.com \
--to=marco.atzeri@gmail.com \
--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).