From: rudzik8 <rudzik8@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] GNU Make package doesn't make a symlink for /usr/bin/gmake
Date: Thu, 13 Jun 2024 08:08:38 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50812@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
New issue by rudzik8 on void-packages repository
https://github.com/void-linux/void-packages/issues/50812
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.32_1 x86_64 AuthenticAMD notuptodate rFFF
### Package(s) Affected
make-4.4.1_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Since our `make` implementation is GNU Make, it is really weird for it to not include a symlink for `gmake`.
For example, this is the output of `ls -l /usr/bin/ | grep "make"` on an Ubuntu system with `make` package installed is:
```
lrwxrwxrwx 1 root root 4 Feb 15 2022 gmake -> make
-rwxr-xr-x 1 root root 255696 Feb 15 2022 make
-rwxr-xr-x 1 root root 4905 Feb 15 2022 make-first-existing-target
```
And all `gmake` commands resolve without any problems there.
### Actual behaviour
CMake checks for `gmake` don't pass, its "simple test program" to verify `cc` doesn't compile (because it expects `gmake` to exist, and doesn't find it), and nobody's happy. :(
This is, however, easily fixed by doing `sudo ln -s /usr/bin/make /usr/bin/gmake`.
### Steps to reproduce
Try CMake'ing anything on a new Void install with `make` and `gcc` installed. [In my case, it was Minetest (+ its deps ofc)](https://github.com/minetest/minetest/issues/14746)
next reply other threads:[~2024-06-13 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 6:08 rudzik8 [this message]
2024-06-14 0:25 ` ahesford
2024-06-14 0:27 ` ahesford
2024-06-14 1:18 ` classabbyamp
2024-06-14 1:41 ` classabbyamp
2024-06-14 2:08 ` sgn
2024-06-14 3:37 ` [ISSUE] [CLOSED] " ahesford
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50812@inbox.vuxu.org \
--to=rudzik8@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).