From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15802] freescale_imx8qmmek_defconfig, freescale_imx8qxpmek_defconfig: Segment flags problem
Date: Sun, 24 Sep 2023 18:09:34 +0000 [thread overview]
Message-ID: <bug-15802-163-lrN5dVCzjg@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15802-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15802
--- Comment #1 from Jan-Benedict Glaw <jbglaw@lug-owl.de> ---
The same issue seems to show up for ls1028ardb_defconfig (see
http://toolchain.lug-owl.de/laminar/jobs/buildroot-ls1028ardb_defconfig/6)
--
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
next prev parent reply other threads:[~2023-09-24 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 22:48 [Buildroot] [Bug 15802] New: freescale_imx8qmmek_defconfig, freescale_imx8qxpmek_defconfig: Segment flags problem bugzilla
2023-09-24 18:09 ` bugzilla [this message]
2024-06-15 15:13 ` [Buildroot] [Bug 15802] " 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-15802-163-lrN5dVCzjg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox