From: Paul Smith <paul@mad-scientist.net>
To: Jerome Yanga <jerome.yanga@gmail.com>, libc-help@sourceware.org
Subject: Re: compile issue: configure failed
Date: Mon, 12 Sep 2022 17:27:25 -0400 [thread overview]
Message-ID: <c4a77585b15e45910c3fd8c39ebadb4a97ca7675.camel@mad-scientist.net> (raw)
In-Reply-To: <CAC0z1F81kk_O_6JtTye8fH9oQKu_mW_hdUnJ7Rv=4V9EHUxeug@mail.gmail.com>
On Mon, 2022-09-12 at 14:20 -0700, Jerome Yanga via Libc-help wrote:
> I attempted to compile GLIBC v2.36. However, I ran into an issue
> that I am not sure how to fix. Help. I have provided the output
> below.
We prefer to see a curated cut-and-paste of error messages, rather than
links to screenshots. Not everyone can follow such links, and not
everyone can easily read screenshots, and we can't easily cut-and-paste
text from a screenshot in our responses.
The issue is pretty straightforward; the error says:
checking for gnumake... no
checking for gmake... gmake
checking version of gmake... 3.82, bad
So, the configure script first looks for gnumake, then gmake, then make
(presumably) and it uses the first one it finds.
You may have a "make" command on your PATH which is new enough, but you
also have a "gmake" command on your PATH which is too old.
You can delete gmake, or change your PATH so that the directory
containing gmake is not on it anymore, or possibly there's a configure
option or variable that lets you specify exactly which make you want to
use: see the mentioned documentation or run "./configure --help" for
more info.
prev parent reply other threads:[~2022-09-12 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 21:20 Jerome Yanga
2022-09-12 21:27 ` Paul Smith [this message]
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=c4a77585b15e45910c3fd8c39ebadb4a97ca7675.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=jerome.yanga@gmail.com \
--cc=libc-help@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).