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

Bug#964645: isakmpd: FTBFS: cc: error: Entering: No such file or directory



Source: isakmpd
Version: 20041012-9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -O2 -g -Wall -DNEED_SYSDEP_APP -I/<<PKGBUILDDIR>> -I/<<PKGBUILDDIR>>/sysdep/linux -I.  -DHAVE_GETNAMEINFO -DUSE_OLD_SOCKADDR -DHAVE_PCAP -DNEED_SYSDEP_APP -DMP_FLAVOUR=MP_FLAVOUR_GMP -DUSE_AES -I/<<PKGBUILDDIR>>/sysdep/linux/include -I/<<PKGBUILDDIR>>/sysdep/common -I/usr/include/openssl  -DUSE_DEBUG  -DUSE_TRIPLEDES  -DUSE_BLOWFISH  -DUSE_CAST  -DUSE_EC  -DUSE_AGGRESSIVE  -DUSE_X509  -DUSE_DPD  -DUSE_NAT_TRAVERSAL  -DUSE_ISAKMP_CFG  -DUSE_AES -DUSE_PF_KEY_V2 -I/<<PKGBUILDDIR>>/apps/certpatch/../.. -I/<<PKGBUILDDIR>>/apps/certpatch/../../sysdep/linux -Imake[2]: Entering directory '/<<PKGBUILDDIR>>' /<<PKGBUILDDIR>> make[2]: Leaving directory '/<<PKGBUILDDIR>>' -Wall -DMP_FLAVOUR=MP_FLAVOUR_GMP -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro  certpatch.c -lcrypto -lssl -lgmp  -o certpatch
> cc: error: Entering: No such file or directory
> cc: error: directory: No such file or directory
> cc: error: make[2]:: No such file or directory
> cc: error: Leaving: No such file or directory
> cc: error: directory: No such file or directory
> make[2]: *** [<builtin>: certpatch] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/isakmpd_20041012-9_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


Reply to: