From: Nicolas Schier <nicolas@fjasle.eu>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: con3270.o is built twice, leading to errors
Date: Fri, 14 Jul 2023 22:01:48 +0200 [thread overview]
Message-ID: <ZLGprFmL8iDz0jbH@fjasle.eu> (raw)
In-Reply-To: <7b663b86-4df0-c3df-18a7-e4f47f900be4@kernel.org>
On Fri, Jul 14, 2023 at 08:33:46AM +0200 Jiri Slaby wrote:
> Hi,
>
> if I create an s390 defconfig:
> mkdir /tmp/s390/
> make O=/tmp/s390/ ARCH=s390 CROSS_COMPILE=s390x-suse-linux- defconfig
>
> And then if I try for a couple times:
> make O=/tmp/s390/ -j17 ARCH=s390 CROSS_COMPILE=s390x-suse-linux-
> drivers/s390/char/con3270.o
>
> Most of the time, I get:
> make[1]: Entering directory '/tmp/s390'
> GEN Makefile
> CALL /home/latest/linux/scripts/checksyscalls.sh
> CC drivers/s390/char/con3270.o
> CC drivers/s390/char/con3270.o
>
> I.e. it is built twice.
>
> Sometimes, I also get an error:
> fixdep: error opening file: drivers/s390/char/.con3270.o.d: No such file or
> directory
> make[4]: *** [/home/latest/linux/scripts/Makefile.build:243:
> drivers/s390/char/con3270.o] Error 2
> make[4]: *** Deleting file 'drivers/s390/char/con3270.o'
> make[3]: *** [/home/latest/linux/scripts/Makefile.build:477: drivers]
>
> Obviously due to some race.
>
> Any ideas what is going on?
Which reason does compiling with V=2 reveal?
Kind regards,
Nicolas
next prev parent reply other threads:[~2023-07-14 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 6:33 con3270.o is built twice, leading to errors Jiri Slaby
2023-07-14 20:01 ` Nicolas Schier [this message]
2023-07-15 5:04 ` Masahiro Yamada
2023-07-17 8:30 ` Jiri Slaby
2023-07-19 8:30 ` arch/um's ssl.o [was: con3270.o] " Jiri Slaby
2023-07-21 13:37 ` Masahiro Yamada
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=ZLGprFmL8iDz0jbH@fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=jirislaby@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.