From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] apparmor: update to 3.1.2.
Date: Sat, 17 Dec 2022 15:05:15 +0100 [thread overview]
Message-ID: <20221217140515.RasLPjwYv1Wixvaa0HHpIx_J8EBYI4IfvKdx4NIk0hg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40965@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]
New review comment by mhmdanas on void-packages repository
https://github.com/void-linux/void-packages/pull/40965#discussion_r1051402851
Comment:
`which` still seems to be required, as the build fails with this error without it:
```
config.status: error: in `/builddir/apparmor-3.1.2/libraries/libapparmor':
config.status: error: Something went wrong bootstrapping makefile fragments
for automatic dependency tracking. If GNU make was not used, consider
re-running the configure script with MAKE="gmake" (or whatever is
necessary). You can also try re-running configure with the
'--disable-dependency-tracking' option to at least be able to build
the package (albeit without support for automatic dependency tracking).
See `config.log' for more details
```
Opening `masterdir/builddir/apparmor-3.1.2/libraries/libapparmor/config.log` and searching for `which` then brings me to this:
```
config.status:1302: cd src && sed -e '/# am--include-marker/d' Makefile | make -f - am--depfiles
make: which: No such file or directory
../../../common//Make.rules:40: *** awk utility required for build but not available. Stop.
config.status:1307: $? = 2
config.status:1302: cd testsuite && sed -e '/# am--include-marker/d' Makefile | make -f - am--depfiles
make: which: No such file or directory
../../../common/Make.rules:40: *** awk utility required for build but not available. Stop.
config.status:1307: $? = 2
config.status:1311: error: in `/builddir/apparmor-3.1.2/libraries/libapparmor':
config.status:1313: error: Something went wrong bootstrapping makefile fragments
for automatic dependency tracking. If GNU make was not used, consider
re-running the configure script with MAKE="gmake" (or whatever is
necessary). You can also try re-running configure with the
'--disable-dependency-tracking' option to at least be able to build
the package (albeit without support for automatic dependency tracking).
See `config.log' for more details
```
next prev parent reply other threads:[~2022-12-17 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 22:52 [PR PATCH] " mhmdanas
2022-12-15 17:22 ` CameronNemo
2022-12-16 18:48 ` [PR REVIEW] " paper42
2022-12-17 14:05 ` mhmdanas [this message]
2022-12-17 14:11 ` paper42
2022-12-18 22:29 ` mhmdanas
2022-12-18 23:04 ` paper42
2022-12-18 23:20 ` mhmdanas
2022-12-18 23:55 ` [PR PATCH] [Updated] " mhmdanas
2022-12-24 23:38 ` [PR PATCH] [Merged]: " paper42
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=20221217140515.RasLPjwYv1Wixvaa0HHpIx_J8EBYI4IfvKdx4NIk0hg@z \
--to=mhmdanas@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).