| To: | Greg Banks <gnb@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Filestreams (and 64bit inodes) |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Thu, 12 Jun 2008 22:46:59 -0500 |
| Cc: | markgw@xxxxxxx, Timothy Shimmin <tes@xxxxxxx>, Richard Scobie <richard@xxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <4851EC2D.6010504@melbourne.sgi.com> |
| References: | <484B15A3.4030505@sauce.co.nz> <484CA425.3080606@sandeen.net> <484DDDB3.70000@sgi.com> <484F0998.90306@sauce.co.nz> <484F2CD7.9070506@sgi.com> <484F452A.8090909@sandeen.net> <48512A34.1020604@sandeen.net> <4851CD32.7080106@melbourne.sgi.com> <4851E774.2070401@sgi.com> <4851EC2D.6010504@melbourne.sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.14 (Macintosh/20080421) |
Greg Banks wrote: >> (and the plan for statically linked apps? ...) > > Perhaps Fedora could enable the glibc magic for issuing warnings at link > time when those symbols are used, like what happens today if you use the > old unsafe gets() function: > > gnb@inara 1058> gcc -o fmeh x.c > /tmp/ccQhxIIo.o: In function `main': > x.c:(.text+0x18): warning: the `gets' function is dangerous and should not be > used. It wouldn't help the automated builds (nobody'd see it) but for normal user compilations that might be an option... -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Filestreams (and 64bit inodes), Eric Sandeen |
|---|---|
| Next by Date: | Re: Filestreams (and 64bit inodes), Greg Banks |
| Previous by Thread: | Re: Filestreams (and 64bit inodes), Greg Banks |
| Next by Thread: | Re: Filestreams (and 64bit inodes), Greg Banks |
| Indexes: | [Date] [Thread] [Top] [All Lists] |