Linux-KBuild Archive mirror
 help / color / mirror / Atom feed
From: Mirsad Todorovac <mtodorovac69@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kernel Build System <linux-kbuild@vger.kernel.org>
Subject: [PROBLEM linux-next] Error in "make olddefconfig" and "make menuconfig"
Date: Tue, 14 May 2024 20:37:10 +0200	[thread overview]
Message-ID: <b948b14b-1543-4314-9e9e-58a54cf2b734@gmail.com> (raw)

Hi, Mr. Bagas,

While bisecting a problem in linux-next tree, I came across the problem:

marvin@defiant:~/linux/kernel/linux-next$ git describe
v6.7-rc5-2761-gefc11f34e25f
marvin@defiant:~/linux/kernel/linux-next$ make olddefconfig
make[2]: *** No targets.  Stop.
make[1]: *** [/home/marvin/linux/kernel/linux-next/Makefile:621: scripts_basic] Error 2
make: *** [Makefile:234: __sub-make] Error 2
marvin@defiant:~/linux/kernel/linux-next$ make menuconfig
make[2]: *** No targets.  Stop.
make[1]: *** [/home/marvin/linux/kernel/linux-next/Makefile:621: scripts_basic] Error 2
make: *** [Makefile:234: __sub-make] Error 2
marvin@defiant:~/linux/kernel/linux-next$ 

Now, this occurred for the first time, and I don't know how to bail out.

I recall in past couple of years you have some insightful advice.

Thank you very much.

Best regards,
Mirsad Todorovac

             reply	other threads:[~2024-05-14 18:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 18:37 Mirsad Todorovac [this message]
2024-05-14 18:44 ` [PROBLEM linux-next] Error in "make olddefconfig" and "make menuconfig" Mirsad Todorovac
2024-05-15  4:17 ` Masahiro Yamada
2024-06-02 11:48   ` Mirsad Todorovac

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=b948b14b-1543-4314-9e9e-58a54cf2b734@gmail.com \
    --to=mtodorovac69@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).