Building libnettle on MS-Windows

Niels Möller nisse at lysator.liu.se
Tue Jan 17 14:37:11 CET 2012


Simon Josefsson <simon at josefsson.org> writes:

> With MinGW-64 I got the following error when building:

For clarity: Is this MinGW-64 *natively* on a windows machine, or a
cross compiler?

> make[1]: Entering directory `/home/jas/src/nettle-2.5-pre/testsuite'
> i686-w64-mingw32-g++ -g -O2 -L..  cxx-test.o testutils.o  -lnettle  -o cxx-test.exe
> /home/jas/src/mingw-w64-32/build/root/lib/gcc/i686-w64-mingw32/4.5.1/../../../../i686-w64-mingw32/bin/ld: cannot find -lgcc_s
> make[1]: *** [cxx-test.exe] Fel 1
>
> It may be that my MinGW-64 g++ installation is not working properly.

Seems likely; I can't see any reason why the compilation command line
should give that error.

> FAIL: ./teardown-env
> make[1]: *** [check] Fel 1
>
> The call to find in teardown-env turns out empty.

Ooops. I should replace that backtick expression with an -exec argument
to find.

> This seems to be the case when I build with --enable-shared as well --
> then there is only one hit (./.lib/libnettle-4-3.dll), but it is not
> under testsuite/. Should there be more *.dll files?

For a native build: That's how it should be. The .lib directory is added
to PATH, which should be sufficient for running the testprograms. The
additional symlinks in the testsuite and example directories should be
there only when cross compiling (detected by $EMULATOR matching wine*).

Regards,
/Niels

-- 
Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26.
Internet email is subject to wholesale government surveillance.


More information about the nettle-bugs mailing list