> From: Pablo Vasquez <[email protected]> > To: [email protected] > Sent: Sunday, 2 August, 2009 3:52:10 AM > Subject: Re: [pdf-devel] Build Error - unit test cases > > In fact this isn't the main issue in the mail I mentioned. I wasn't > talking about the errors I got. I was talking about something Jose > said there. > In that mail Jose says: > > >The compilation of the unit tests fails when compiling > >torture/unit/base/stm/pdf-stm-write.c, due to the usage of check > >fixtures introduced by a recent patch. Currently nocheck is not > >supporting fixtures. >
Oops..it seems I missed this information earlier. Thanks for pointing it out :). > And then comes some talking about check and nocheck. > Please read the mail again. > Sorry if I wasn't clear enough. > > Pablo. > > > > On Sat, Aug 1, 2009 at 4:27 PM, Gaurav Aggarwal wrote: > > > > >From: Pablo Vasquez > > >To: [email protected] > > >Sent: Saturday, 1 August, 2009 3:36:59 PM > > >Subject: Re: [pdf-devel] Build Error - unit test cases > > > > > > > > >I don't have check library installed on my system. But I am pretty sure > > >this > error has nothing to do with this option. As long as someone is building the > test binaries, person will face this problem. > > >> > > >> > > >> > > >In fact, it does have something to do with it. The builtin "nocheck" > > >doesn't > support libcheck's fixtures. This issue was brought to my attention by Jose, > please see > > > > > >http://lists.gnu.org/archive/html/pdf-devel/2009-07/msg00011.html > > > > > >for some info on this and what's being done about it. > > > > > >> > > >Pablo. > > > > > Still I don't think that this is because of the absence of the check > > library. > I followed the mail thread mentioned above, but as per my understanding both > of > them are different problems. In the above discussed mail, problem is coming > mainly because of the fact some of the library symbols are not available > during > build time, thats also on the different platform (for windows) but in my > case, > its one of the pdf library test function, that is missing. Since, because of > the top mailings this mail no longer contains the original problem reported > by > me, I am attaching the build error and my system configuration once again. > > > > ========================================================================== > > System Configuration > > -------------------------------- > > Architecture : Intel Pentium (i686) > > Operating System : Linux 2.6.26 > > Compiler used : gcc 4.1.2 > > > > > > Build Error > > --------------------- > > >gcc -DHAVE_CONFIG_H -I. -I../../src -I../../lib > > -I../../src -I../../src/base -I../../src/object > > -I../../torture/tortutils -DTEST_DATA_PATH=\"../../torture/testdata\" > > -Inocheck/ -g -g -MT pdf-stm-write.o -MD -MP -MF > > .deps/pdf-stm-write.Tpo -c -o pdf-stm-write.o `test -f > > 'base/stm/pdf-stm-write.c' || echo './'`base/stm/pdf-stm-write.c > > >base/stm/pdf-stm-write.c: In function 'mem_stm_fixture_setup': > > >base/stm/pdf-stm-write.c:52: error: 'test_name' undeclared (first use in > > >this > function) > > >base/stm/pdf-stm-write.c:52: error: (Each undeclared identifier is > > >reported > only once > > >base/stm/pdf-stm-write.c:52: error: for each function it appears in.) > > >make[2]: *** > > > [pdf-stm-write.o] Error 1 > > >make[2]: Leaving directory `/home/GNU-pdf/gnupdf.gaurav/torture/unit' > > >make[1]: *** [all-recursive] Error 1 > > >make[1]: Leaving directory `/home/GNU-pdf/gnupdf.gaurav/torture' > > >make: *** [all-recursive] Error 1 > > > > > >FYI, I used the following command during configure time: > > >./configure > > -prefix=/home/GNU-pdf/inst --enable-debug-base --enable-debug-object > > --enable-debug-document --enable-debug-page --enable-nocheck CFLAGS=-g > > > > > Problem Analysis - > > ------------------------------ > > After looking at the source code, it seems to me that in > > "torture/unit/base/stm/pdf-stm-write.c" file, "fail_if()" is used > > inside the mem_stm_fixture_setup() function which is NOT a valid usage > > scenario. fail_if() macro used a variable 'test_name' but this variable > > is initialized only in the START_TEST macro which is not getting called > > in this particular case. I double check it, and currently this function ( > 'mem_stm_fixture_setup') is the only place where we are > > calling the fail_if without invoking the START_TEST earlier. Also, > > function "tcase_add_checked_fixture" used in the same file i.e. in > > pdf-stm-write.c file is not defined anywhere. So, even if you fix the > > first problem, person will get the undefined function error for this > > during linking time. I would suggest that the author of this file take > > a relook at this file and do the necessary changes. > > > > > >Let me know in case you guys need more information regarding this. Hope, > > >this > will help. > > > > > >-- > > >Regards, > > >Gaurav Aggarwal > > > > > > > > > > > Yahoo! recommends that you upgrade to the new and safer Internet > > Explorer > 8. http://downloads.yahoo.com/in/internetexplorer/ See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. http://in.buzz.yahoo.com/
