diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2012-03-17 12:31:07 +0100 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2012-03-17 12:31:07 +0100 |
| commit | 3bf27c93ac4de57623809b71517116d51465f0e1 (patch) | |
| tree | ec3edc96d8a3639651e722b401bf677bc9505c68 /open_issues/glibc_madvise_vs_static_linking.mdwn | |
| parent | 88ade4a03928041ad710594f3281b883528bc8ec (diff) | |
IRC bits.
Diffstat (limited to 'open_issues/glibc_madvise_vs_static_linking.mdwn')
| -rw-r--r-- | open_issues/glibc_madvise_vs_static_linking.mdwn | 15 |
1 files changed, 14 insertions, 1 deletions
diff --git a/open_issues/glibc_madvise_vs_static_linking.mdwn b/open_issues/glibc_madvise_vs_static_linking.mdwn index 6238bc77..7b5963d3 100644 --- a/open_issues/glibc_madvise_vs_static_linking.mdwn +++ b/open_issues/glibc_madvise_vs_static_linking.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2010, 2011 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2010, 2011, 2012 Free Software Foundation, +Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -24,3 +25,15 @@ to ignore the advice.* (`man madvise`), so we may simply want to turn it into a no-op in glibc, avoiding the link-time warning. 2011-07: This is what Samuel has done for Debian glibc. + + +# IRC, freenode, #hurd, 2012-02-16 + + <tschwinge> youpi: With Roland's fix the situation will be that just using + gcc -static doesn't emit the stub warning, but still will do so in case + that the source code itself links in madvise. Is this acceptable for + you/Debian/...? + <youpi> packages with -Werror will still bug out + <youpi> not that I consider -Werror to be a good idea, though :) + <tschwinge> youpi: Indeed. Compiler warnings can be caused by all kinds of + things. -Werror is good for development, but not for releases. |