From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Cezary Rojewski <cezary.rojewski@intel.com>
Subject: Re: [broonie-sound:for-5.19 88/98] sound/soc/soc-acpi.c:58:36: warning: initialization of 'struct acpi_device *' from 'int' makes pointer from integer without a cast
Date: Tue, 26 Apr 2022 09:25:30 +0200 [thread overview]
Message-ID: <62af4093-a4ff-62b1-10db-585235c06747@linux.intel.com> (raw)
In-Reply-To: <202204261004.8OOIWobj-lkp@intel.com>
On 4/26/2022 4:54 AM, kernel test robot wrote:
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash sound/soc/
/home/xxxxxxxx/0day/gcc-11.3.0-nolibc/arceb-elf/bin/arceb-elf-gcc:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found
(required by
/home/xxxxxxxx/0day/gcc-11.3.0-nolibc/arceb-elf/bin/arceb-elf-gcc)
/home/xxxxxxxx/0day/gcc-11.3.0-nolibc/arceb-elf/bin/arceb-elf-gcc:
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found
(required by
/home/xxxxxxxx/0day/gcc-11.3.0-nolibc/arceb-elf/bin/arceb-elf-gcc)
SYNC include/config/auto.conf.cmd
GEN Makefile
/home/xxxxxxxx/0day/gcc-11.3.0-nolibc/arceb-elf/bin/arceb-elf-gcc:
unknown compiler
scripts/Kconfig.include:44: Sorry, this compiler is not supported.
Having a "nolibc" in compiler path I find it confusing that it seems to
require glibc...?
I guess I will be able to figure what's going on without reproduction,
but would be probably easier with reproducer ;) .
next prev parent reply other threads:[~2022-04-26 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 2:54 [broonie-sound:for-5.19 88/98] sound/soc/soc-acpi.c:58:36: warning: initialization of 'struct acpi_device *' from 'int' makes pointer from integer without a cast kernel test robot
2022-04-26 7:25 ` Amadeusz Sławiński [this message]
2022-04-26 7:49 ` Chen, Rong A
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=62af4093-a4ff-62b1-10db-585235c06747@linux.intel.com \
--to=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/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