app-crypt:signify-17-r1:20160422-222524.log

app-crypt:signify-17-r1:20160422-222524.log (text/plain), 6.09 KB, created by Toralf Förster on 2016-04-23 09:18:37 UTC

 * Package:    app-crypt/signify-17-r1
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking signify-17.tar.gz to /var/tmp/portage/app-crypt/signify-17-r1/work
>>> Source unpacked in /var/tmp/portage/app-crypt/signify-17-r1/work
>>> Preparing source in /var/tmp/portage/app-crypt/signify-17-r1/work/signify-17 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-crypt/signify-17-r1/work/signify-17 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-crypt/signify-17-r1/work/signify-17 ...
make -j1 
fatal: Not a git repository (or any parent up to mount point /var/tmp/portage)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o crypto_api.o crypto_api.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o mod_ed25519.o mod_ed25519.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o mod_ge25519.o mod_ge25519.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o fe25519.o fe25519.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o sc25519.o sc25519.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o smult_curve25519_ref.o smult_curve25519_ref.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o bcrypt_pbkdf.o bcrypt_pbkdf.c
bcrypt_pbkdf.c: In function ‘bcrypt_pbkdf’:
bcrypt_pbkdf.c:122:21: warning: pointer targets in passing argument 2 of ‘SHA512Update’ differ in signedness [-Wpointer-sign]
  SHA512Update(&ctx, pass, passlen);
                     ^
In file included from bcrypt_pbkdf.c:23:0:
sha2.h:123:6: note: expected ‘const u_int8_t * {aka const unsigned char *}’ but argument is of type ‘const char *’
 void SHA512Update(SHA2_CTX *, const u_int8_t *, size_t)
      ^
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o timingsafe_bcmp.o timingsafe_bcmp.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o explicit_bzero.o explicit_bzero.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o blowfish.o blowfish.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o base64.o base64.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o sha2.o sha2.c
sed -e 's/hashinc/sha2.h/g' \
    -e 's/HASH/SHA256/g' \
    -e 's/SHA[0-9][0-9][0-9]_CTX/SHA2_CTX/g' helper.c > sha256hl.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o sha256hl.o sha256hl.c
sed -e 's/hashinc/sha2.h/g' \
    -e 's/HASH/SHA512/g' \
    -e 's/SHA[0-9][0-9][0-9]_CTX/SHA2_CTX/g' helper.c > sha512hl.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o sha512hl.o sha512hl.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o signify.o signify.c
signify.c: In function ‘verifyembedded’:
signify.c:477:33: warning: pointer targets in passing argument 2 of ‘parseb64file’ differ in signedness [-Wpointer-sign]
  siglen = parseb64file(sigfile, msg, &sig, sizeof(sig), sigcomment);
                                 ^
signify.c:127:1: note: expected ‘char *’ but argument is of type ‘uint8_t * {aka unsigned char *}’
 parseb64file(const char *filename, char *b64, void *buf, size_t buflen,
 ^
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o pledge_noop.o pledge_noop.c
cc -march=native -O2 -pipe   -Wall -include compat.h  -c -o ohash.o ohash.c
cc -Wl,-O1 -Wl,--as-needed  -o signify crypto_api.o mod_ed25519.o mod_ge25519.o fe25519.o sc25519.o smult_curve25519_ref.o bcrypt_pbkdf.o timingsafe_bcmp.o explicit_bzero.o blowfish.o base64.o sha2.o sha256hl.o sha512hl.o signify.o pledge_noop.o ohash.o -lbsd
>>> Source compiled.
>>> Test phase [not enabled]: app-crypt/signify-17-r1

>>> Install signify-17-r1 into /var/tmp/portage/app-crypt/signify-17-r1/image/ category app-crypt
make -j1 install 
fatal: Not a git repository (or any parent up to mount point /var/tmp/portage)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
gzip -9c signify.1 > signify.1.gz
install -m 755 -d /var/tmp/portage/app-crypt/signify-17-r1/image//usr/bin
install -m 755 -t /var/tmp/portage/app-crypt/signify-17-r1/image//usr/bin signify
install -m 755 -d /var/tmp/portage/app-crypt/signify-17-r1/image//usr/share/man/man1
install -m 644 -t /var/tmp/portage/app-crypt/signify-17-r1/image//usr/share/man/man1 signify.1.gz
>>> Completed installing signify-17-r1 into /var/tmp/portage/app-crypt/signify-17-r1/image/

 * Final size of build directory: 884 KiB
 * Final size of installed tree: 192 KiB

strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment -R .GCC.command.line -R .note.gnu.gold-version
   usr/bin/signify
ecompressdir: bzip2 -9 /usr/share/man
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at http://bugs.gentoo.org unless you report exactly which
 * two packages install the same file(s). See
 * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to
 * solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/usr/share/man/man1/signify.1.bz2
 * 	/usr/bin/signify
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * net-mail/signify-1.14:0::gentoo
 * 	/usr/bin/signify
 * 	/usr/share/man/man1/signify.1.bz2
 * 
 * Package 'app-crypt/signify-17-r1' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.