mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mirsad Todorovac <mtodorovac69@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kernel Build System <linux-kbuild@vger.kernel.org>
Subject: Re: [PROBLEM linux-next] Error in "make olddefconfig" and "make menuconfig"
Date: Sun, 2 Jun 2024 13:48:11 +0200	[thread overview]
Message-ID: <47e101e6-fbd2-4373-854a-db9431bf0d74@gmail.com> (raw)
In-Reply-To: <CAK7LNASTaxPDH4_wozMc9G6NE+HwFXgLiUAM5Ki9mc-Gwf4vmA@mail.gmail.com>

On 5/15/24 06:17, Masahiro Yamada wrote:
> On Wed, May 15, 2024 at 3:37 AM Mirsad Todorovac <mtodorovac69@gmail.com> wrote:
>>
>> Hi, Mr. Bagas,
>>
>> While bisecting a problem in linux-next tree, I came across the problem:
> 
> 
> I checked out v6.7-rc5-2761-gefc11f34e25f
> but 'make olddefconfig' worked fine with me.
> 
> 
> If this issue occurs only during 'git bisect',
> I need full steps to reproduce it because I do not
> know what you did before v6.7-rc5-2761-gefc11f34e25f.
> 
> 
>   $ git checkout <some commit>
>   $ [ do something ]
>   $ git v6.7-rc5-2761-gefc11f34e25f
>   $ make olddefconfig
> 
> 
> If I am able to reproduce the issue that way,
> maybe I can have more insight.

Just to report that fresh cloning eliminated the error.

Best regards,
Mirsad Todorovac

>> 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-06-02 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 18:37 Mirsad Todorovac
2024-05-14 18:44 ` Mirsad Todorovac
2024-05-15  4:17 ` Masahiro Yamada
2024-06-02 11:48   ` Mirsad Todorovac [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=47e101e6-fbd2-4373-854a-db9431bf0d74@gmail.com \
    --to=mtodorovac69@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@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

all inboxes | Powered by JetHome®