unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: 57959@debbugs.gnu.org
Subject: bug#57959: 29.0.50; build error on gnulinux
Date: Thu, 22 Sep 2022 22:03:50 +0000	[thread overview]
Message-ID: <c614892c6dd06bc47ab4@heytings.org> (raw)
In-Reply-To: <87tu5011pb.fsf@codeisgreat.org>


>> What's the exact "make" command you type?  Can you try "git clean -fdx" 
>> followed by "make" (without any other arguments, except -j<some 
>> number>)?
>
> Yes. If I run just "make -j`nproc`" after "git clean -fdx", it builds 
> fine. Following is my observation now,
>
> # bad
> git clean -fdx
> make -j`nproc` configure="--prefix=$HOME/.local" install
>
> # bad
> ./autogen.sh
> ./configure --prefix=$HOME/.local
> make -j`nproc` install
>
> # good
> ./autogen.sh
> ./configure --prefix=$HOME/.local
> make -j`nproc`
> make install
>
> It appears that the "install" target has some issues with "-j`nproc`" if 
> the emacs is not already built.
>

This should now be fixed on master.  Can you please check, and tell us if 
it's indeed fixed?

(Note that "make install" works, but is not recommended.  It is better to 
do "make && make install", to actually proceed with the install only if 
the build succeeded.)





  reply	other threads:[~2022-09-22 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 18:27 bug#57959: 29.0.50; build error on gnulinux Pankaj Jangid
2022-09-20 19:12 ` Lars Ingebrigtsen
2022-09-20 23:17 ` Gregory Heytings
2022-09-21  3:51   ` Pankaj Jangid
2022-09-21  8:23     ` Gregory Heytings
2022-09-22  4:18       ` Pankaj Jangid
2022-09-22 22:03         ` Gregory Heytings [this message]
2022-09-30 14:41           ` Pankaj Jangid
2022-09-30 15:26             ` Gregory Heytings

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c614892c6dd06bc47ab4@heytings.org \
    --to=gregory@heytings.org \
    --cc=57959@debbugs.gnu.org \
    --cc=pankaj@codeisgreat.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).