Bug#989391: phnxdeco FTCBFS -- uses the build architecture compiler
Package: phnxdeco
Version: 0.33-3
Severity: normal
Tags: patch
User: debian-cross@lists.debian.org
Usertags: ftcbfs
X-Debbugs-Cc: nilesh@debian.org, debian-cross@lists.debian.org
Dear Maintainer,
phnxdeco Fails to cross build because it hardcodes gcc as build
compiler,
Simply replacing such invocations with $(CC) fixes it. Please consider
applying the patch attached.
PS: Since this package hasn't been uploaded for more than 13 years,
which is a *really really* long time, I intend to NMU it post bullseye
release, with this patch applied - if not uploaded on time ofcourse.
Nilesh
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages phnxdeco depends on:
ii libc6 2.31-3
phnxdeco recommends no packages.
phnxdeco suggests no packages.
diff -Nur -x '*.orig' -x '*~' phnxdeco-0.33/src/Makefile phnxdeco-0.33.new/src/Makefile
--- phnxdeco-0.33/src/Makefile 2021-06-02 19:32:33.394649634 +0530
+++ phnxdeco-0.33.new/src/Makefile 2021-06-02 19:33:24.941634732 +0530
@@ -9,17 +9,17 @@
phnxdeco: phnxfunc kernel
DEMO=""
- gcc -DDEBUG $(DEMO) phnxdeco.c phnxfunc.o kernel.o -fpack-struct -o phnxdeco
+ $(CC) -DDEBUG $(DEMO) phnxdeco.c phnxfunc.o kernel.o -fpack-struct -o phnxdeco
phnxdeco-demo:
DEMO=1
- gcc -DDEBUG=$(DEMO) phnxdeco.c phnxfunc.o kernel.o -fpack-struct -o phnxdeco-demo
+ $(CC) -DDEBUG=$(DEMO) phnxdeco.c phnxfunc.o kernel.o -fpack-struct -o phnxdeco-demo
phnxfunc:
- gcc phnxfunc.c -c -o phnxfunc.o -fpack-struct
+ $(CC) phnxfunc.c -c -o phnxfunc.o -fpack-struct
kernel:
- gcc kernel.c -c -o kernel.o -fpack-struct
+ $(CC) kernel.c -c -o kernel.o -fpack-struct
clean:
rm -f *.o
Reply to: