On 06/29/2015 02:40 PM, Anoop C S wrote: > > > On 06/29/2015 11:56 PM, Kaleb S. KEITHLEY wrote: >> On 06/29/2015 02:04 PM, Anoop C S wrote: >>> >>> Reading through gcc docs I could see that with gcc v5, it >>> defaults to C99 semantics and compiling with -fgnu89-inline >>> solves the above issue. I'm wondering how glusterfs compiled >>> successfully without providing this flag. > >> Well, it didn't originally. > >> Most of the bugs were fixed before Fedora 22 arrived with gcc-5. ^^^^^^^^^^^^^^^^ I didn't say all of them had been fixed. ;-) > >> E.g. by building on Fedora Rawhide last year, reporting the bugs, >> and getting them fixed before Rawhide turned into Fedora 22. > > > Immediately after the Fedora 22 release, we had a similar issue > reported from a user with gcc v5 and was fixed through [1]. > Yes, there were still some, and/or some had crept (back) in, when Fedora22 was released. I think we're still finding some more. Not all of the developers are using Fedora 22 yet. I know a few that are still on Fedora 19! Niels and I had a brief chat a while back about adding a Fedora 22 VM to Jenkins to catch these. I don't think anything ever happened though. -- Kaleb _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
