From: Sedat Dilek <sedat.dilek@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 5.11-rc1
Date: Mon, 28 Dec 2020 09:04:36 +0100 [thread overview]
Message-ID: <CA+icZUWHiCu9=+80Z8OV+Q3r-TJ4Vm0t62P_Qgck5bRzjrtaWg@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUUQRKuZzN0ZbaG6vprRWcKPKYVYTryiMFac7q_PRcBvgA@mail.gmail.com>
On Mon, Dec 28, 2020 at 8:30 AM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>
> [ Please CC me I am not subscribed to LKML and linux-kbuild ML ]
>
> Hi Linus, Hi Mashiro,
>
> thanks for the Linux v5.11-rc1 release.
>
> With a new release I always do my first builds with my distro's
> default compiler and linker (GCC v10.2.1 and GNU/ld BFD v2.35.1).
> ( It's approx. 40% faster than LLVM toolchain v11.0.1-rc2 here on
> Debian/testing AMD64. )
>
> The only warning I see for the first time (with v5.10.3 not observed):
>
> sh ./scripts/depmod.sh depmod 5.11.0-rc1-1-amd64-gcc10-bfd
> Warning: 'make modules_install' requires depmod. Please install it.
> This is probably in the kmod package.
>
> The only change I see in this area is:
>
> 436e980e2ed5 kbuild: don't hardcode depmod path
>
> depmod from kmod Debian package is placed and I have no /sbin in my
> user's path (and not before?):
>
> $ dpkg -L kmod | grep bin | grep depmod
> /sbin/depmod
>
> $ which depmod
> [ empty ]
>
> $ echo $PATH
> /opt/proxychains-ng/bin:/home/dileks/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>
> OK, this is a warning, but might confuse other users.
>
> Please, let me know if you need further information and keep me CCed.
>
> Thanks.
>
> Regards,
> - Sedat -
>
> [1] https://git.kernel.org/linus/436e980e2ed526832de822cbf13c317a458b78e1
[ Correct email-address of linux-kbuild ML ]
This might be distro-specific:
[ /etc/login.defs ]
99:# *REQUIRED* The default PATH settings, for superuser and normal users.
100:#
101:# (they are minimal, add the rest in the shell startup files)
102:ENV_SUPATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
103:ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
What is your recommendation?
- Sedat -
next prev parent reply other threads:[~2020-12-28 8:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 7:30 Linux 5.11-rc1 Sedat Dilek
2020-12-28 8:04 ` Sedat Dilek [this message]
2020-12-28 15:18 ` Sedat Dilek
2020-12-28 19:40 ` Linus Torvalds
2020-12-28 20:05 ` Sedat Dilek
2021-01-01 16:14 ` Pavel Machek
2021-01-01 18:55 ` Sedat Dilek
2021-01-01 22:31 ` Sedat Dilek
2021-01-02 7:51 ` Masahiro Yamada
2021-01-02 9:13 ` Sedat Dilek
2021-01-02 11:05 ` Bernd Petrovitsch
2021-01-02 11:26 ` Sedat Dilek
2021-01-02 11:57 ` Bernd Petrovitsch
2021-01-02 12:11 ` Sedat Dilek
2021-01-03 17:39 ` David Laight
2021-01-02 15:30 ` Masahiro Yamada
2020-12-28 15:25 ` Sedat Dilek
2020-12-28 19:45 ` Linus Torvalds
2020-12-28 20:08 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2021-01-02 23:26 Ilkka Prusi
2021-01-03 17:45 ` David Laight
2021-01-04 1:47 ` Adam Borowski
2020-12-28 0:04 Linus Torvalds
2020-12-28 15:51 ` Guenter Roeck
2020-12-28 18:59 ` Linus Torvalds
2020-12-28 19:37 ` Kalesh Singh
2020-12-28 20:02 ` Guenter Roeck
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='CA+icZUWHiCu9=+80Z8OV+Q3r-TJ4Vm0t62P_Qgck5bRzjrtaWg@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=torvalds@linux-foundation.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).