All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12196] New: duma package
Date: Fri, 06 Sep 2019 08:31:59 +0000	[thread overview]
Message-ID: <bug-12196-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 12196
           Summary: duma package
           Product: buildroot
           Version: unspecified
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: ioctl at ya.ru
                CC: buildroot at uclibc.org
  Target Milestone: ---

Duma package build is incorrect. Following original GNUmakefile, it should be
build with -O0, but buildroot make it with -O2, that leads to the "Illegal
instruction" problem with my program for ARM cpu. This can be fixed by adding
"CFLAGS+=-O0 \" into the DUMA_BUILD_CMDS definition in duma.mk.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-09-06  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06  8:31 bugzilla at busybox.net [this message]
2019-09-11 13:30 ` [Buildroot] [Bug 12196] duma package bugzilla at busybox.net
2019-09-17  8:32 ` bugzilla at busybox.net
2019-11-27 20:40 ` bugzilla at busybox.net
2019-12-09 10:53 ` bugzilla at busybox.net
2019-12-09 10:55 ` bugzilla at busybox.net
2019-12-09 10:55 ` bugzilla at busybox.net
2019-12-13 22:34 ` bugzilla at busybox.net
2020-05-20 14:38 ` [Buildroot] [Bug 12196] Illegal instruction in "duma" when built with -O2 bugzilla at busybox.net
2024-06-15 14:50 ` 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-12196-163@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 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.