Bingo. That did the trick. Compile is successful on OS X with 1.17.21 again now. Big thanks for the hasty replies and fixes, really appreciate those!
I run a permanent Debian Virtualbox, so I guess the desire to compile dpkg on OS X for packaging is horribly lazy of me really heh. Bug reporting & fixing on Debian is so much more pleasant than OS X though, that's for sure. Thanks again, Dom Sent from OS X. If you wish to communicate more securely my PGP Public Key is 0x872524db9d74326c. On 12/11/2014 00:49, Guillem Jover wrote: > On Wed, 2014-11-12 at 00:36:42 +0000, Dominyk Tiller wrote: >> That did indeed seem to be the trick. I wondered why the build process >> was suggesting ';' were missing, but I shrugged it off as being too >> simple a fix, heh. "My bad" on that. >> >> That does indeed get me further, although I've run into a new error on >> the same fdio function: > >> ---------------------------------------------------------------------------------------- >> CCLD dpkg-deb >> Undefined symbols for architecture x86_64: >> "_fs_preallocate_setup", referenced from: >> _fd_allocate_size in libdpkg.a(fdio.o) >> ld: symbol(s) not found for architecture x86_64 >> clang: error: linker command failed with exit code 1 (use -v to see >> invocation) >> make[2]: *** [dpkg-deb] Error 1 >> make[1]: *** [all-recursive] Error 1 >> ---------------------------------------------------------------------------------------- > > Buh. :/ Just rename fs_preallocate_setup() calls to > fd_preallocate_setup(), I think it was a leftover from a refactoring, > and let's see from there. I've squashed that in the previous commit > locally. > > In any case, please do keep reporting any such problems on other non-GNU > systems, it's much appreciated. > > Thanks, > Guillem > -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5462b332.8060...@gmail.com
