Re: [pdf-devel] "Hello" and questions

[Aleksander Morgado]

Hi Pablo,

> Looking at FS#85 in the tasks list, started trying to reproduce the
> issue, but haven't even got it to cleanly cross-compile to w32.
> First, I would like to know if that's the way to go, I mean, compiling
> through mingw32 and using wine. At least it seems so according to
> http://lists.gnu.org/archive/html/pdf-devel/2009-01/msg00023.html.
> I've downloaded, compiled and installed w32 versions of libgcrypt and
> libgpg-error with prefix /usr/i586-mingw32msvc.
> Created a w32build dir in trunk and in there:
> 
> ../configure --host=i586-mingw32msvc
> --with-libgcrypt-prefix=/usr/i586-mingw32msvc
> --with-zlib=/usr/i586-mingw32msvc

In order to compiler support for unit tests in w32, you need to pass an
additional argument to ./configure: --enable-nocheck

That will enable using the built-in `check' replacement. I know that
guys developing check already added (some) compatibility with w32
(fork-less, as our no-check), but not sure if it's already in the latest
stable or just in their repo.


> 
> Running make brings
> 
> [...]
> /bin/sh ../libtool --tag=CC   --mode=compile i586-mingw32msvc-gcc
> -DHAVE_CONFIG_H -I. -I../../src  -I../../lib -I../../src/base
> -I../../src/object -I../../src/document -I/usr/i586-mingw32msvc/include
> -Wall -fno-strict-aliasing   -g -O2 -MT pdf-fsys-disk.lo -MD -MP -MF
> .deps/pdf-fsys-disk.Tpo -c -o pdf-fsys-disk.lo `test -f
> 'base/pdf-fsys-disk.c' || echo '../../src/'`base/pdf-fsys-disk.c
>  i586-mingw32msvc-gcc -DHAVE_CONFIG_H -I. -I../../src -I../../lib
> -I../../src/base -I../../src/object -I../../src/document
> -I/usr/i586-mingw32msvc/include -Wall -fno-strict-aliasing -g -O2 -MT
> pdf-fsys-disk.lo -MD -MP -MF .deps/pdf-fsys-disk.Tpo -c
> ../../src/base/pdf-fsys-disk.c  -DDLL_EXPORT -DPIC -o .libs/pdf-fsys-disk.o
> ../../src/base/pdf-fsys-disk.c: In function
> '__pdf_fsys_disk_get_status_from_errno':
> ../../src/base/pdf-fsys-disk.c:1442: error: 'EOVERFLOW' undeclared
> (first use in this function)
> ../../src/base/pdf-fsys-disk.c:1442: error: (Each undeclared identifier
> is reported only once
> ../../src/base/pdf-fsys-disk.c:1442: error: for each function it appears
> in.)
> ../../src/base/pdf-fsys-disk.c:1451: error: 'ETXTBSY' undeclared (first
> use in this function)
> make[2]: *** [pdf-fsys-disk.lo] Error 1
> make[2]: Leaving directory `/home/code/lignupdf/w32/src'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/code/lignupdf/w32/src'
> make: *** [all-recursive] Error 1
> [...]
> 
> Which I "hotfixed" commenting lines 1442 and 1451 of
> src/base/pdf-fsys-disk.c just to go on.

Instead of commenting them, I would include them between host-based macros.
#ifndef PDF_HOST_WIN32
whatever here
#endif

Well, that is only if W32 is the only architecture without those errno
errors. There should be a more clean way of doing it, I guess.


> 
> [SEVERAL MORE LIBGCRYPT UNDEFINED REFERENCES]
> 
> collect2: ld returned 1 exit status
> make[2]: *** [libgnupdf.la <http://libgnupdf.la>] Error 1
> make[2]: Leaving directory `/home/code/lignupdf/w32/src'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/code/lignupdf/w32/src'
> make: *** [all-recursive] Error 1
> 
> Which I "hotfixed" running 
> 
> make LDFLAGS=-lgcrypt
> 
> And building finished successfully, so to speak.

Humm.. why is this happening?

> 
> So, are these issues known or is there something wrong with my environment?
> Is something else required to build the tests correctly?
> How was libgnupdf built in the report citated in FS#85?

Yes, the --enable-nocheck option that I told before. You need it to
compile the unit tests. Then you can follow the steps given in the email
referred in FS#85 to try to reproduce it.

Cheers and welcome!

-Aleksander