From: Keith M. <kei...@us...> - 2009-07-06 16:52:58
|
On Tuesday 23 June 2009 01:25:19 Charles Wilson wrote: > >> zlib > >> bzip2 > >> xz > > > > I was planning to do these myself; (already have them built, and > > just the split, packaging and distribution to complete). Do you > > want to take them over, or shall I continue with them? > > It's probably better if I take over xz just for synergy. I'm > already bouncing patches back and forth with Lasse Collin > concerning the build issues. One of them, perhaps, being: .../mingw32/bin/as: BFD (GNU Binutils) 2.19.1 assertion fail .../bfd/coff-i386.c:583 .../src/liblzma/check/crc32_x86.S: Assembler messages: .../src/liblzma/check/crc32_x86.S:117: Error: cannot represent relocation type BFD_RELOC_386_GOTPC make[4]: *** [libcheck_la-crc32_x86.lo] Error 1 make[4]: Leaving directory `/home/keith/sandbox/xz-4.999.8beta/mingw32/src/liblzma/check' This is xz-4.999.8beta configured with --disable-nls --disable-rpath (in addition to --build=i686-pc-linux --host=mingw32); if I also add --disable-shared, I can successfully build and deploy as a completely static library. > I also maintain the cygwin builds of zlib, mingw-zlib [*], bzip2, > and mingw-bzip2 [*], so I could do those two as well, but in the > interests of preserving my sanity, how about you go ahead with > zlib and bzip2? Ok, I'll go ahead with that. FWIW, I have bzip2 ready to deploy; (I autoconfiscated it, to make cross-compilation easier -- <sigh> why do some developers assume that their package needs are too modest to justify using autoconf? Hand crafted configure scripts, or no configure scripts at all, are a total pain for those of us who have build requirements differing from those of the original developer). I'm in two minds, whether or not to repeat the exercise for zlib; the proliferation of make variables which need manual reassignment to achieve a successful cross-build are, again, a total pain with their non-standard, hand-crafted configure script. -- Regards, Keith. |