http://bugzilla.suse.com/show_bug.cgi?id=967437 http://bugzilla.suse.com/show_bug.cgi?id=967437#c3 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |schwab@suse.com Resolution|INVALID |--- Assignee|schwab@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #3 from Dr. Werner Fink --- (In reply to Andreas Schwab from comment #2) I do not use them! Why should I enforce this and ahow could this be done? (In reply to Marcus Meissner from comment #1) The build of blogd *was* poisoned. Then I've added the line %define __filter_GLIBC_PRIVATE 1 in the spec file and the problem was gone. As this had worked I also had added this line now in the project configuration of Base:System to protect all other packages to be poisoned. Btw: IMHO this is not a bug of the glibc but of the build system! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=967437 http://bugzilla.suse.com/show_bug.cgi?id=967437#c6 --- Comment #6 from Dr. Werner Fink --- (In reply to Andreas Schwab from comment #5) Ahh .. thanks for spotting ;) Now then how to I avoid the message: warning: the use of `mktemp' is dangerous, better use `mkstemp' or I have to use explicit the "/dev/shm/" prefix and mkstemp() instead of the official shm_open() API as there is no secure shm_mkstemp() ala openBSD http://resin.csoft.net/cgi-bin/man.cgi?section=3&topic=shm_open -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=967437 Chenzi Cao changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |adrian@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.