On Mon, Jul 13, 2009 at 9:05 PM, Regis<xu.re...@gmail.com> wrote: > Catherine Hope wrote: >> >> I can recreate the problem building from the repository trunk or the See >> branch. The difference in the command-line is (running from >> modules/portlib/src/main/native/port/unix) >> >> Running in release mode gives a compiler error with: >> cc -DLINUX -DLINUX_X86 -DHYX86 -DIPv6_FUNCTION_SUPPORT -D_REENTRANT >> -DHY_NO_THR -DHY_ZIP_API >> -I/home/cath/workspaceHarmony/Select/community-src/deploy/include >> -I/home/cath/workspaceHarmony/Select/community-src/deploy/jdk/include -I. >> -I../shared/ -DHYPORT_LIBRARY_DEFINE -Ilinux.x86 -O1 -DNDEBUG -fpic >> -march=pentium3 -Werror -c -o hyfiletext.o hyfiletext.c >> >> Running in debug mode: >> cc -DLINUX -DLINUX_X86 -DHYX86 -DIPv6_FUNCTION_SUPPORT -D_REENTRANT >> -I/home/cath/workspaceHarmony/Java6/deploy/include >> -I/home/cath/workspaceHarmony/Java6/deploy/jdk/include -I. -I../shared/ >> -DHYPORT_LIBRARY_DEFINE -Ilinux.x86 -ggdb -O0 -fpic -march=pentium3 >> -Werror -c -o hyfiletext.o hyfiletext.c >> >> Full gcc version: >> Using built-in specs. >> Target: i486-linux-gnu >> Configured with: ../src/configure -v --with-pkgversion='Ubuntu >> 4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs >> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr >> --enable-shared >> --with-system-zlib --libexecdir=/usr/lib --without-included-gettext >> --enable-threads=posix --enable-nls >> --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 >> --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc >> --enable-mpfr >> --enable-targets=all --with-tune=generic --enable-checking=release >> --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu >> Thread model: posix >> gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) >> >> I can't recreate the UnixFileTest test failure (I'm running with the IBM >> Java 6 VME): >> [junit] Running org.apache.harmony.luni.tests.java.io.UnixFileTest >> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.503 sec > > UnixFileTest is not stable for me, it failed intermittently, suppose not > related to this issue.
What Linux derivation are you running? I'm running Ubuntu 9.04 x86 and LUNI tests on trunk consistently pass for me. When I apply this patch, UnixFileTest fails every time. -Nathan > >> >> On Sun, Jul 12, 2009 at 9:17 PM, Nathan Beyer (JIRA) >> <j...@apache.org>wrote: >> >>> [ >>> >>> https://issues.apache.org/jira/browse/HARMONY-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730138#action_12730138] >>> >>> Nathan Beyer commented on HARMONY-6266: >>> --------------------------------------- >>> >>> When I apply this patch, I get a failure in the following test. >>> >>> org.apache.harmony.luni.tests.java.io.UnixFileTest >>> test_getCanonicalPath failure >>> expected:<...ild/test/luni/folder[1/folder]2> but >>> was:<...ild/test/luni/folder[]2> >>> >>>> Building in release mode fails with gcc version 4.3.3 >>>> ----------------------------------------------------- >>>> >>>> Key: HARMONY-6266 >>>> URL: https://issues.apache.org/jira/browse/HARMONY-6266 >>>> Project: Harmony >>>> Issue Type: Bug >>>> Components: Classlib >>>> Environment: Linux 32 running 2.6.28-11-generic #42-Ubuntu >>>> Reporter: Catherine Hope >>>> Assignee: Nathan Beyer >>>> Priority: Minor >>>> Attachments: patch.txt >>>> >>>> >>>> Building in release mode (the default for building Harmony Select) will >>> >>> currently fail on gcc version 4.3.3 as warnings are treated as errors and >>> that compiler version is more strict in regards to things like not >>> checking >>> return codes of library functions. The files affected are: >>>> >>>> [exec] hyfiletext.c:234: warning: ignoring return value of 'wctomb', >>> >>> declared with attribute warn_unused_result >>>> >>>> [exec] hyosdump.c:86: warning: ignoring return value of 'chdir', >>> >>> declared with attribute warn_unused_result >>>> >>>> [exec] linux/../hysl.c:306: warning: ignoring return value of >>> >>> 'mbtowc', declared with attribute warn_unused_result >>>> >>>> [exec] procimpl.c:176: warning: ignoring return value of 'write', >>> >>> declared with attribute warn_unused_result >>>> >>>> [exec] procimpl.c:180: warning: ignoring return value of 'write', >>> >>> declared with attribute warn_unused_result >>>> >>>> [exec] procimpl.c:195: warning: ignoring return value of 'write', >>> >>> declared with attribute warn_unused_result >>>> >>>> [exec] procimpl.c:215: warning: ignoring return value of 'read', >>> >>> declared with attribute warn_unused_result >>>> >>>> [exec] authnix.c:144: warning: ignoring return value of 'getgroups', >>> >>> declared with attribute warn_unused_result >>>> >>>> [exec] ../shared/SurfaceDataStructure.h:177: warning: inline >>> >>> function 'void updateCache(SURFACE_STRUCTURE*, JNIEnv*, _jobject*, bool, >>> int, int, int, int)' used but never defined >>> >>> -- >>> This message is automatically generated by JIRA. >>> - >>> You can reply to this email to add a comment to the issue online. >>> >>> >> >> > > > -- > Best Regards, > Regis. >
