From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/chntpw/
Date: Wed, 31 Jan 2024 12:55:30 +0000 (UTC) [thread overview]
Message-ID: <1706705722.68c9b8f93ff895caa7bf5aaee085e66ffb7862a4.marecki@gentoo> (raw)
commit: 68c9b8f93ff895caa7bf5aaee085e66ffb7862a4
Author: Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 31 12:48:34 2024 +0000
Commit: Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Wed Jan 31 12:55:22 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=68c9b8f9
app-crypt/chntpw: force -std=gnu90
Just a workaround for build errors for now. In the long run, I think
I'd better look at whether how useful exactly (if at all) chntpw is
against modern Windows versions, warrants all the changes required
to make the code C99-compliant.
Nb. It's gnu90 rather than c90 because of the use of // for comments.
Closes: https://bugs.gentoo.org/919172
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>
app-crypt/chntpw/chntpw-140201-r1.ebuild | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/app-crypt/chntpw/chntpw-140201-r1.ebuild b/app-crypt/chntpw/chntpw-140201-r1.ebuild
index 2aeae846a75b..8594fba742f8 100644
--- a/app-crypt/chntpw/chntpw-140201-r1.ebuild
+++ b/app-crypt/chntpw/chntpw-140201-r1.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-inherit toolchain-funcs
+inherit flag-o-matic toolchain-funcs
DESCRIPTION="Offline Windows NT Password & Registry Editor"
HOMEPAGE="https://pogostick.net/~pnh/ntpasswd/"
@@ -34,6 +34,9 @@ src_prepare() {
default
sed -i -e '/-o/s:$(CC):$(CC) $(LDFLAGS):' Makefile || die
+ # MANY changes would be required for this code to be c99-compliant
+ append-flags -std=gnu90
+
if ! use static ; then
sed -i -e "/^all:/s/ \(chntpw\|reged\).static//g" Makefile || die
fi
next reply other threads:[~2024-01-31 12:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 12:55 Marek Szuba [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-12 0:56 [gentoo-commits] repo/gentoo:master commit in: app-crypt/chntpw/ Marek Szuba
2022-11-11 3:50 Sam James
2022-11-11 3:50 Sam James
2022-11-10 18:18 Arthur Zamarin
2022-09-07 14:30 Marek Szuba
2021-12-23 23:02 Sam James
2021-12-23 16:39 Jory Pratt
2021-05-02 16:40 Mikle Kolyada
2020-03-18 17:14 Marek Szuba
2020-01-21 10:42 Agostino Sarubbo
2020-01-21 10:33 Agostino Sarubbo
2020-01-20 19:46 Agostino Sarubbo
2020-01-10 11:30 Marek Szuba
2017-02-04 1:31 Alon Bar-Lev
2016-06-12 13:41 Alon Bar-Lev
2016-06-03 8:55 Anthony G. Basile
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=1706705722.68c9b8f93ff895caa7bf5aaee085e66ffb7862a4.marecki@gentoo \
--to=marecki@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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