app-crypt:signify-30:20210527-073139.log

app-crypt:signify-30:20210527-073139.log (text/plain), 5.97 KB, created by Toralf Förster on 2021-05-27 08:13:15 UTC

 * Package:    app-crypt/signify-30
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

>>> Unpacking source...
>>> Unpacking signify-30.tar.gz to /var/tmp/portage/app-crypt/signify-30/work
>>> Source unpacked in /var/tmp/portage/app-crypt/signify-30/work
>>> Preparing source in /var/tmp/portage/app-crypt/signify-30/work/signify-30 ...
 * Applying signify-30-man_compress.patch ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-crypt/signify-30/work/signify-30 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-crypt/signify-30/work/signify-30 ...
make -j2 
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o crypto_api.o crypto_api.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o mod_ed25519.o mod_ed25519.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o mod_ge25519.o mod_ge25519.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o fe25519.o fe25519.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o sc25519.o sc25519.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -Wno-pointer-sign -include compat.h  -c -o bcrypt_pbkdf.o bcrypt_pbkdf.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o timingsafe_bcmp.o timingsafe_bcmp.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o blowfish.o blowfish.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o base64.o base64.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -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
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
sed -e 's/hashinc/sha2.h/g' \
    -e 's/HASH/SHA512_256/g' \
    -e 's/SHA512_256_CTX/SHA2_CTX/g' helper.c > sha512_256hl.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -Wno-pointer-sign -include compat.h  -c -o signify.o signify.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -Wno-pointer-sign -include compat.h  -c -o zsig.o zsig.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o pledge_noop.o pledge_noop.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o ohash.o ohash.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o sha256hl.o sha256hl.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o sha512hl.o sha512hl.c
x86_64-pc-linux-gnu-gcc -pipe -march=native -fno-diagnostics-color  -Og -g   -Wall -include compat.h  -c -o sha512_256hl.o sha512_256hl.c
x86_64-pc-linux-gnu-gcc -Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0  -o signify crypto_api.o mod_ed25519.o mod_ge25519.o fe25519.o sc25519.o bcrypt_pbkdf.o timingsafe_bcmp.o blowfish.o base64.o sha2.o sha256hl.o sha512hl.o sha512_256hl.o signify.o zsig.o pledge_noop.o ohash.o -lbsd 
>>> Source compiled.
>>> Test phase [not enabled]: app-crypt/signify-30

>>> Install app-crypt/signify-30 into /var/tmp/portage/app-crypt/signify-30/image
make -j2 DESTDIR=/var/tmp/portage/app-crypt/signify-30/image PREFIX=/usr install 
install -m 755 -d /var/tmp/portage/app-crypt/signify-30/image/usr/bin
install -m 755 -t /var/tmp/portage/app-crypt/signify-30/image/usr/bin signify
install -m 755 -d /var/tmp/portage/app-crypt/signify-30/image/usr/share/man/man1
install -m 644 -t /var/tmp/portage/app-crypt/signify-30/image/usr/share/man/man1 signify.1
>>> Completed installing app-crypt/signify-30 into /var/tmp/portage/app-crypt/signify-30/image

 * Final size of build directory: 1272 KiB (1.2 MiB)
 * Final size of installed tree:   356 KiB

strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version
   /usr/bin/signify
 * checking 4 files for package collisions
 * 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 https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://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-30' NOT merged due to file collisions. If
 * necessary, refer to your elog messages for the whole content of the
 * above message.