Forgot to mentioned the link in previous mail. Link for "GCC 4.3 Release Series Porting to the New Tools"
http://gcc.gnu.org/gcc-4.3/porting_to.html Thanks Milinda On Fri, May 23, 2008 at 9:37 AM, Milinda Pathirage < [EMAIL PROTECTED]> wrote: > Hi all, > I think these build errors caused by new warnings introduced by GCC 4.3. > Here is part of their GCC 4.3 porting document. > > New warnings > > Significant changes were made to -Wconversion. In addition, improvements > to the GCC infrastructure allow improvements in the ability of several > existing warnings to spot problematic code. As such, new warnings may exist > for previously warning-free code that uses -Wuninitialized, -Wstrict-aliasing > , -Wunused-function, -Wunused-variable. Note that -Wall subsumes many of > these warning flags. > > Although these warnings will not result in compilation failure, often > -Wall is used in conjunction with -Werror and as a result, new warnings > are turned into new errors. > > As a workaround, remove -Werror until the new warnings are fixed, or for > conversion warnings add -Wno-conversion. > > > So I think we have to use correct flags which will make code compile in > both gcc older versions and new versions. I propose other than using -Wall > with -Werror, we must use following flags as necessary. > > -Wuninitialized, -Wstrict-aliasing , -Wunused-function, -Wunused-variable > > > Thanks > > Milinda > > > > > > On Thu, May 22, 2008 at 3:33 PM, Chintana Wilamuna (JIRA) <[EMAIL PROTECTED]> > wrote: > >> When -Werror is in effect build break in util/src >> ------------------------------------------------- >> >> Key: AXIS2C-1157 >> URL: https://issues.apache.org/jira/browse/AXIS2C-1157 >> Project: Axis2-C >> Issue Type: Bug >> Components: util >> Affects Versions: 1.4.0 >> Environment: Fedora Core 9. GCC 4.3.0 >> Reporter: Chintana Wilamuna >> >> >> GCC complains with the following error, >> >> hash.c:573: error: 'axutil_hash_entry_free' defined but not used >> make[5]: *** [hash.lo] Error 1 >> >> Since WSF/C uses all the modules I issued the following command to see >> where axutil_hash_entry_free is being used, >> >> find wsf_c -iname '*.c' | xargs grep 'axutil_hash_entry_free' >> >> And found out that it's not being used anywhere. If it's not being used I >> suggest at least commenting out the function since it breaks the build. >> >> -- >> This message is automatically generated by JIRA. >> - >> You can reply to this email to add a comment to the issue online. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > http://mpathirage.com > http://wso2.org "Oxygen for Web Service Developers" > http://wsaxc.blogspot.com "Web Services With Axis2/C" -- http://mpathirage.com http://wso2.org "Oxygen for Web Service Developers" http://wsaxc.blogspot.com "Web Services With Axis2/C"
