[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 1.17.21 on OS X

Hello Dominyk!

Dominyk Tiller <dominyktiller@gmail.com> (2014-11-11):
> Hey all,
> Hopefully this email reaches the group, the Debian spam filter can be a
> little overzealous at the best of times.
> I'm trying to compile the latest dpkg, 1.17.21 on OS X, but keep running
> into this persistent error. It could be expected given the relative
> newness of this release, but thought I'd kick the configure process
> upstream for a better insight.
> Using a patch to fix the Perl location on OS X, and the MD5/SHA1/SHA256
> tool use, but nothing that should halt or interfere drastically with
> compile as far as I can see. The error seems to be unrelated.
> Shall attach the build process and the patch, both of which are
> hopefully some use.
> If anyone is particularly jumpy about email attachments, the error is:
> ----------------------------------------------------------------------------------------
>   CC       fdio.lo
> fdio.c:113:36: error: expected ';' after expression
>         rc = fcntl(fd, F_PREALLOCATE, &fs)
>                                           ^
>                                           ;
> fdio.c:118:37: error: expected ';' after expression
>                 rc = fcntl(fd, F_PREALLOCATE, &fs)
>                                                   ^
>                                                   ;
> 2 errors generated.
> make[4]: *** [fdio.lo] Error 1
> make[4]: *** Waiting for unfinished jobs....
>   CC       file.lo
> make[3]: *** [all-recursive] Error 1
> ----------------------------------------------------------------------------------------

There's a ";" character missing at the end of the line indeed;
introduced in this commit:
| commit 87b0b20b86407baf1deb4e91b3fd839e01228ac8
| Author: Guillem Jover <guillem@debian.org>
| Date:   Tue Jul 15 21:00:52 2014 +0200
|     dpkg: Try to preallocate the disk size for extracted files
|     This might help in avoiding filesystem fragmentation, and possibly
|     improve performance on some filesystems.
|     We use the system specific methods if available, and only use
|     posix_fallocate() if nothing else is available, because on some systems
|     its semantics are counter to what we want to obtain here, as the libc
|     library will fallback to manually writing '\0' to each block to force
|     the preallocation, instead of just failing and leaving the application
|     to do so if desired.

Adding one should help you get further. ;)


Attachment: signature.asc
Description: Digital signature

Reply to: