From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12761] Buildroot fails when building GCNano binaries for the STM32MP1
Date: Tue, 07 Apr 2020 00:30:20 +0000 [thread overview]
Message-ID: <bug-12761-163-QiKVyj5gif@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12761-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12761
--- Comment #2 from Aaron Decker <adecker246@gmail.com> ---
I gave that a shot using the tarball from the ST github. I get a different
error:
https://pastebin.com/UL4vfkNG
In file included from
/home/ajdecker/projects/buildroot/output/build/gcnano-binaries-c01642ed5e18cf09ecd905af193e935cb3be95ed/./hal/os/linux/kernel/gc_hal_kernel_linux.h:61,
from
/home/ajdecker/projects/buildroot/output/build/gcnano-binaries-c01642ed5e18cf09ecd905af193e935cb3be95ed/./hal/os/linux/kernel/gc_hal_kernel_driver.c:62:
./include/linux/module.h:133:6: error: ?init_module? specifies less restrictive
attribute than its target ?gpu_init?: ?cold? [-Werror=missing-attributes]
133 | int init_module(void) __attribute__((alias(#initfn)));
| ^~~~~~~~~~~
/home/ajdecker/projects/buildroot/output/build/gcnano-binaries-c01642ed5e18cf09ecd905af193e935cb3be95ed/./hal/os/linux/kernel/gc_hal_kernel_driver.c:1267:1:
note: in expansion of macro ?module_init?
1267 | module_init(gpu_init);
| ^~~~~~~~~~~
/home/ajdecker/projects/buildroot/output/build/gcnano-binaries-c01642ed5e18cf09ecd905af193e935cb3be95ed/./hal/os/linux/kernel/gc_hal_kernel_driver.c:1224:19:
note: ?init_module? target declared here
1224 | static int __init gpu_init(void)
| ^~~~~~~~
In file included from
/home/ajdecker/projects/buildroot/output/build/gcnano-binaries-c01642ed5e18cf09ecd905af193e935cb3be95ed/./hal/os/linux/kernel/gc_hal_kernel_linux.h:61,
from
/home/ajdecker/projects/buildroot/output/build/gcnano-binaries-c01642ed5e18cf09ecd905af193e935cb3be95ed/./hal/os/linux/kernel/gc_hal_kernel_driver.c:62:
./include/linux/module.h:139:7: error: ?cleanup_module? specifies less
restrictive attribute than its target ?gpu_exit?: ?cold?
[-Werror=missing-attributes]
139 | void cleanup_module(void) __attribute__((alias(#exitfn)));
| ^~~~~~~~~~~~~~
/home/ajdecker/projects/buildroot/output/build/gcnano-binaries-c01642ed5e18cf09ecd905af193e935cb3be95ed/./hal/os/linux/kernel/gc_hal_kernel_driver.c:1268:1:
note: in expansion of macro ?module_exit?
1268 | module_exit(gpu_exit);
| ^~~~~~~~~~~
/home/ajdecker/projects/buildroot/output/build/gcnano-binaries-c01642ed5e18cf09ecd905af193e935cb3be95ed/./hal/os/linux/kernel/gc_hal_kernel_driver.c:1255:20:
note: ?cleanup_module? target declared here
1255 | static void __exit gpu_exit(void)
| ^~~~~~~~
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-07 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 15:09 [Buildroot] [Bug 12761] New: Buildroot fails when building GCNano binaries for the STM32MP1 bugzilla at busybox.net
2020-04-06 15:10 ` [Buildroot] [Bug 12761] " bugzilla at busybox.net
2020-04-06 19:47 ` bugzilla at busybox.net
2020-04-07 0:30 ` bugzilla at busybox.net [this message]
2020-05-17 18:47 ` bugzilla at busybox.net
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=bug-12761-163-QiKVyj5gif@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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