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

Bug#1034006: marked as done (libowfat FTCBFS: builds for the build architecture)



Your message dated Fri, 05 Apr 2024 14:35:05 +0000
with message-id <E1rsken-00FNFa-2a@fasolo.debian.org>
and subject line Bug#1034006: fixed in libowfat 0.32-5
has caused the Debian Bug report #1034006,
regarding libowfat FTCBFS: builds for the build architecture
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1034006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034006
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libowfat
Version: 0.32-4
Tags: patch
User: debian-cross@lists.debian.org
Usertags: ftcbfs

libowfat fails to cross build from source, because it builds for the
build architecture. To cross build libowfat one is supposed to supply
either CCC or CROSS. Beyond that, it fails to use CCC for the linker
step. I'm attaching a patch for your convenience.

Helmut
diff --minimal -Nru libowfat-0.32/debian/changelog libowfat-0.32/debian/changelog
--- libowfat-0.32/debian/changelog	2022-11-10 16:32:49.000000000 +0100
+++ libowfat-0.32/debian/changelog	2023-04-06 09:31:10.000000000 +0200
@@ -1,3 +1,11 @@
+libowfat (0.32-5) UNRELEASED; urgency=medium
+
+  * Fix FTCBFS: (Closes: #-1)
+    + Pass CCC to make.
+    + cross.patch: Use CCC for linking as well.
+
+ -- Helmut Grohne <helmut@subdivi.de>  Thu, 06 Apr 2023 09:31:10 +0200
+
 libowfat (0.32-4) unstable; urgency=high
 
   * QA upload
diff --minimal -Nru libowfat-0.32/debian/patches/cross.patch libowfat-0.32/debian/patches/cross.patch
--- libowfat-0.32/debian/patches/cross.patch	1970-01-01 01:00:00.000000000 +0100
+++ libowfat-0.32/debian/patches/cross.patch	2023-04-06 09:31:10.000000000 +0200
@@ -0,0 +1,9 @@
+--- libowfat-0.32.orig/GNUmakefile
++++ libowfat-0.32/GNUmakefile
+@@ -394,5 +394,5 @@
+ 	ln -sf $< $@
+ 
+ libowfat.so.0: $(ALL_OBJS)
+-	$(CC) -shared -Wl,-soname=$@ $(LDFLAGS) $^ -o $@
++	$(CCC) -shared -Wl,-soname=$@ $(LDFLAGS) $^ -o $@
+ 
diff --minimal -Nru libowfat-0.32/debian/patches/series libowfat-0.32/debian/patches/series
--- libowfat-0.32/debian/patches/series	2022-11-10 16:31:16.000000000 +0100
+++ libowfat-0.32/debian/patches/series	2023-04-06 09:31:10.000000000 +0200
@@ -6,3 +6,4 @@
 07-fix-FD_CLOEXEC.patch
 08-clang-ftbfs.diff
 fix_gcc10.patch
+cross.patch
diff --minimal -Nru libowfat-0.32/debian/rules libowfat-0.32/debian/rules
--- libowfat-0.32/debian/rules	2022-11-10 16:31:16.000000000 +0100
+++ libowfat-0.32/debian/rules	2023-04-06 09:31:10.000000000 +0200
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+include /usr/share/dpkg/buildtools.mk
+
 CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)
 CFLAGS:=$(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS) -I.
 CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS) $(CPPFLAGS)
@@ -9,9 +11,9 @@
 	dh $@
 
 override_dh_auto_build:
-	$(MAKE) -f $(CURDIR)/GNUmakefile CFLAGS="$(CFLAGS) -fPIC" DIET='' libowfat.so
+	$(MAKE) -f $(CURDIR)/GNUmakefile CCC=$(CC) CFLAGS="$(CFLAGS) -fPIC" DIET='' libowfat.so
 	$(MAKE) -f $(CURDIR)/GNUmakefile clean
-	$(MAKE) -f $(CURDIR)/GNUmakefile CFLAGS="$(CFLAGS)" DIET=''
+	$(MAKE) -f $(CURDIR)/GNUmakefile CCC=$(CC) CFLAGS="$(CFLAGS)" DIET=''
 	rm entities.h
 
 override_dh_installchangelogs:

--- End Message ---
--- Begin Message ---
Source: libowfat
Source-Version: 0.32-5
Done: Bastian Germann <bage@debian.org>

We believe that the bug you reported is fixed in the latest version of
libowfat, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1034006@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated libowfat package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 05 Apr 2024 15:36:02 +0200
Source: libowfat
Architecture: source
Version: 0.32-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 932446 1034006 1045772
Changes:
 libowfat (0.32-5) unstable; urgency=medium
 .
   * QA upload
   * Remove mkfifo and opendir from description (Closes: #932446)
   * Adopt dpkg-build-api
   * Clean additional files (Closes: #1045772)
   * Move headers to their own namespace (Closes: #1045772)
 .
   [ Helmut Grohne ]
   * cross.patch: Use CCC for linking
   * Pass CCC to make (Closes: #1034006)
Checksums-Sha1:
 7c2add1d88a28a6971322d8729ebc58d528af6e4 1780 libowfat_0.32-5.dsc
 4fa94c781352455710e0adb7a1220bc3cd5fb18c 15016 libowfat_0.32-5.debian.tar.xz
 9a7953b23545ba1a1547e3cf07bb47ef153b6cd6 5500 libowfat_0.32-5_source.buildinfo
Checksums-Sha256:
 1f9b4690cd45e71af7ef76f69283810669f65e8fb1a8e7d942670bafa5fa63f8 1780 libowfat_0.32-5.dsc
 95c35b4fda43be8a26ffbc3399859eb42f6aa6217d85bdefed64323e68146326 15016 libowfat_0.32-5.debian.tar.xz
 decaae38247efe524e2819ba982aa097f064f84cdd216bee434cb54a16360545 5500 libowfat_0.32-5_source.buildinfo
Files:
 8d55d348292de4e392db44143136725c 1780 libs optional libowfat_0.32-5.dsc
 4e02b0ffb5b9034eb6ed6ab1082795a8 15016 libs optional libowfat_0.32-5.debian.tar.xz
 4cc29a254b817859c19202c8b22cd38f 5500 libs optional libowfat_0.32-5_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYQA1AQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFCELC/492R8KZ37Kr+EghPEPZWWqCyyy0DYZyHcH
7uJtHzRLx9QnEX86BY9VnZYPYL+Cmm46npiCFVZCAtJCBn+7oe/3Wz4RI4gDurzq
8JXJ8OQs/1gV6vKQEvfpevzrMHl6BzEHus7gQIN8X/svZNm8b58mCFZfADYtCulT
oI8aE+U9CcIFd34lAKbvCaMMy4jvz5ezJYO2WGi92r0a0pg3bH3Y3mlhcSN0K1VA
7i3YQWHdqCJVMMDdg4TJdxockUDqBYneYXVySPs8/09iF4KP5CzCi8gNcZGtW8OM
AycryiIJZDQF0C/awgeuDYJWXAGnxWm1/pUs8cSv9rYV5o1wc5xVwkizE+PgGeTH
PZclNBBwXf9fOJiUhWBkBd711fjib1o/Es7O4BlZl0Wj9nRA1Cr5l4AoZHXsm02/
l/Oz5h9ELcFvszdjjkr0eVF7YWHLOmgJddM/h9jQSZIYYK7eVkGM/soIOuz4HMs5
JcYGSoWfR4vj1R9akqb2cadY8JA8Fzw=
=ORcS
-----END PGP SIGNATURE-----

Attachment: pgpVpKdFPuTIW.pgp
Description: PGP signature


--- End Message ---

Reply to: