All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Sedat Dilek <sedat.dilek@gmail.com>
Subject: linux-next: build failure after merge of the compiler-attributes tree
Date: Fri, 30 Aug 2019 08:52:27 +1000	[thread overview]
Message-ID: <20190830085227.01676c93@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

Hi all,

After merging the compiler-attributes tree, today's linux-next build
(powerpc ppc64_defconfig) failed like this:

arch/powerpc/boot/main.c:153:45: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__section'
  153 | static char cmdline[BOOT_COMMAND_LINE_SIZE] __section(__builtin_cmdline);
      |                                             ^~~~~~~~~
arch/powerpc/boot/main.c: In function 'prep_cmdline':
arch/powerpc/boot/main.c:166:6: error: 'cmdline' undeclared (first use in this function)
  166 |  if (cmdline[0] == '\0')
      |      ^~~~~~~
arch/powerpc/boot/main.c:166:6: note: each undeclared identifier is reported only once for each function it appears in
arch/powerpc/boot/main.c: In function 'start':
arch/powerpc/boot/main.c:196:40: error: 'cmdline' undeclared (first use in this function)
  196 |  if ((loader_info.cmdline_len > 0) && (cmdline[0] == '\0'))
      |                                        ^~~~~~~

Caused by commit

  e81c903fb9e2 ("powerpc: prefer __section and __printf from compiler_attributes.h")

I have reverted that commit for today.

gcc v9.2.1 (in case that matters)

The above error is from the PowerPC boot wrapper that is built without
the kernel headers (mainly, I think).

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-08-29 22:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 22:52 Stephen Rothwell [this message]
2019-08-29 22:53 ` linux-next: build failure after merge of the compiler-attributes tree Nick Desaulniers
2019-08-29 22:54 ` Miguel Ojeda
2019-08-29 22:58   ` Miguel Ojeda
  -- strict thread matches above, loose matches on Subject: below --
2019-02-06 21:30 Stephen Rothwell
2019-02-06 21:48 ` Miguel Ojeda

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=20190830085227.01676c93@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=sedat.dilek@gmail.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.