Ticket #1872 (closed defect: fixed)
Build fixups (unused variables, etc)
Reported by: | metux | Owned by: | metux |
---|---|---|---|
Priority: | blocker | Milestone: | |
Component: | mc-core | Version: | 4.7.0-pre4 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Branch state: | Votes for changeset: |
Description (last modified by metux) (diff)
Branch:1872_build_fixups
changeset:393a08fac876097259f1587d4e278ce63f347c68
passed all tests, please vote asap as it's critical.
Change History
comment:4 Changed 15 years ago by angel_il
- Status changed from new to closed
- Resolution set to fixed
- Blocking 1845 removed
comment:5 Changed 15 years ago by metux
- Status changed from closed to reopened
- Resolution fixed deleted
- Description modified (diff)
- severity changed from no branch to on review
comment:6 Changed 15 years ago by metux
The branch also fixes some more things (eg. building w/o vfs).
comment:19 Changed 15 years ago by metux
rebased to current master, now running through testfarm ...
comment:20 follow-up: ↓ 25 Changed 15 years ago by slavazanko
In changeset:413432283c22c38a5211176f4cca5e14b558189a present some MVFS stuff. Is these need to apply in this branch? May be better to move this stuff into special branch?
comment:25 in reply to: ↑ 20 Changed 15 years ago by metux
Replying to slavazanko:
In changeset:413432283c22c38a5211176f4cca5e14b558189a present some MVFS stuff. Is these need to apply in this branch? May be better to move this stuff into special branch?
It's needed to fix problems w/ already present (but yet unused) mvfs stuff.
comment:28 in reply to: ↑ 26 Changed 15 years ago by metux
Replying to angel_il:
What exactly does that change mean ?
Please keep in mind that we should merge it asap, as it's critical to get MC cleanly built at all.
comment:29 Changed 15 years ago by metux
- Blocking 1843 added
comment:30 Changed 15 years ago by metux
- Blocking 1906 added
comment:31 Changed 15 years ago by metux
- Blocking 1767 added
comment:33 Changed 15 years ago by andrew_b
- Blocking 1906 removed
comment:34 Changed 15 years ago by slyfox
I propose to move
Ticket #1897: Fix compiler warnings/breaks on ignored result values which shouldnt be ignored Glibc marks several functions, whose returns values should not be ignore, with warn_unused_resultwarn_unused_result. Unfortunately we've got a lot of places where exactly these return values *are* ignored (eg. read(), write(), dup(), ... calls), so the compiler *breaks* when building w/ -Werror (which ought to be a MUST for any production build ;-o). Actually, we should have a closer look on it all, whether some results probably have to be handled (eg. to prevent possible leaks).
away from this branch to related #1897 and fix it in a better way: suppress silly warnings and really fix the rest.
Sprinkling 'if () {}' is very hard to read in the end result. I'd like to try another solution, like introducting
/* somewhere in global.h */ #ifdef __GNUC__ /* or something */ #define__mc_unused __attribute__((unused)) #else #define__mc_unused #endif /* __GNUC__ */ system("i don't care") __mc_unused;
I'm not sure if it will work though, but it would be ideal, as it's easily grepable and looks exactly the way glibc introduces wur :]
vfsdummy.h removal should contain 2 phases (as it's hard to review real changes in current state):
- blind code move from vfsdummy.h to vfs.h
and
- patching it.
(or the reverse, as it's easier to do right)
Then patch will look very small and I'll be happy to place a vote here.
comment:36 Changed 15 years ago by andrew_b
- Blocking 1843 removed
(In #1843) Rebased to current master.
changeset:39ddea87eef200a064e418d7da0b3ac72c7b7649
changeset:b881a7b9ad1cac57d087bbae8e21fe323d199207
comment:38 Changed 15 years ago by slavazanko
- severity changed from on review to on rework
Branch have lot of conflicts when rebased on current master
comment:40 Changed 14 years ago by slavazanko
- Status changed from accepted to testing
- Resolution set to fixed
- Blocking 1812 removed
Already in master
comment:41 Changed 14 years ago by slavazanko
- Status changed from testing to closed
- Milestone 4.7 deleted
comment:42 Changed 14 years ago by andrew_b
- Blocking 1812 added
(In #1812) Replying to slavazanko:
Branch incompatible with current master
Partially commits of this branch are in the master one.