From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13021] New: Minor code error when building granite-0.4.1
Date: Tue, 23 Jun 2020 01:59:48 +0000 [thread overview]
Message-ID: <bug-13021-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13021
Bug ID: 13021
Summary: Minor code error when building granite-0.4.1
Product: buildroot
Version: 2020.05
Hardware: Macintosh
OS: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: testosdevsteam at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
The problem stems specifically when building granite gets to
/lib/Services/Settings.vala and crashes the compilation.
FYI: This bug is hard to reproduce.
How to reproduce:
1) Get a longterm support version of buildroot.
2) Make a linux config with granite enabled
3) Get the 2020.05 version of buildroot and install it on the latest version of
Ubuntu with dependencies installed.
2) Copy over longterm config to 2020.5
3) do sudo make or make on 2020.5
What actually happened:
Granite throws 5 compilation errors then crashes the distro building process.
Expected behavior:
No errors and smooth compilation.
Build 2020.05 on MacBook Pro mid-2017 Hardware (running a Ubuntu VM)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-23 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 1:59 bugzilla at busybox.net [this message]
2020-06-23 2:03 ` [Buildroot] [Bug 13021] Minor code error when building granite-0.4.1 bugzilla at busybox.net
2020-06-23 13:21 ` 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-13021-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox