All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16012] New: Cannot compile image for imx8mqevk_defconfig
Date: Fri, 29 Mar 2024 14:08:12 +0000	[thread overview]
Message-ID: <bug-16012-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=16012

            Bug ID: 16012
           Summary: Cannot compile image for imx8mqevk_defconfig
           Product: buildroot
           Version: 2024.02
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: yocto.develop@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

There are 2 problems:
1. Cannot compile hab.c. We got this error: 
error: array subscript 0 is outside array bounds of ‘uint32_t[0]’ {aka
‘unsigned int[]’} [-Werror=array-bounds]
   71 | #define HAB_RVT_REPORT_STATUS_ARM64             ((unsigned
long)*(uint32_t *)(HAB_RVT_BASE + 0x48))

2. We changed the hab.c code to avoid the error but we got this linker error:
error: array subscript 0 is outside array bounds of ‘uint32_t[0]’ {aka
‘unsigned int[]’} [-Werror=array-bounds]
   71 | #define HAB_RVT_REPORT_STATUS_ARM64             ((unsigned
long)*(uint32_t *)(HAB_RVT_BASE + 0x48))

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-03-29 14:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 14:08 bugzilla [this message]
2024-06-15 15:22 ` [Buildroot] [Bug 16012] Cannot compile image for imx8mqevk_defconfig bugzilla

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-16012-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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 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.