From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4171] New: makedevs-unused-but-set-variable.patch
Date: Fri, 9 Sep 2011 23:17:00 +0000 (UTC) [thread overview]
Message-ID: <bug-4171-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=4171
Summary: makedevs-unused-but-set-variable.patch
Product: buildroot
Version: 2010.11
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: hector.oron at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Hello,
makedevs package in buildroot fails to build when `-Wunused-but-set-variable'
is set in the compiler. The following patch attempts to fix this issue:
Index: buildroot-2010.11/package/makedevs/makedevs.c
===================================================================
--- buildroot-2010.11.orig/package/makedevs/makedevs.c 2011-09-09
22:33:32.948124813 +0100
+++ buildroot-2010.11/package/makedevs/makedevs.c 2011-09-09
22:33:55.044124824 +0100
@@ -531,5 +531,5 @@
if (system("/bin/sync"))
bb_error_msg("sync failed, continuing anyway");
- return 0;
+ return ret;
}
Best regards,
-- Hector Oron
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-09-09 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 23:17 bugzilla at busybox.net [this message]
2011-10-09 21:27 ` [Buildroot] [Bug 4171] makedevs-unused-but-set-variable.patch bugzilla at busybox.net
2011-10-23 17:50 ` 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-4171-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