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

Bug#901265: marked as done (libkarma FTCBFS: relinks with the build architecture compiler during make install)

Your message dated Wed, 02 Jan 2019 00:06:09 +0000
with message-id <E1geU2z-000979-TG@fasolo.debian.org>
and subject line Bug#901265: fixed in libkarma 0.1.2-4
has caused the Debian Bug report #901265,
regarding libkarma FTCBFS: relinks with the build architecture compiler during make install
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.)


-- 
901265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901265
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libkarma
Version: 0.1.2-2.5
Tags: patch upstream
User: helmutg@debian.org
Usertags: rebootstrap

libkarma fails to cross build from source, because it fails relinking
the library during make install. This is because it uses the build
architecture compiler there as dh_auto_install (unlike dh_auto_build)
does not pass cross compilers along. This relinking is entirely
unnecessary though and is due to depending on $(LIBDIR) which is always
modified. Turning that dependency into an order-only dependency avoids
the unnecessary relinking and thus makes libkarma cross buildable. It
also builds slightly faster. Please consider applying the attached
patch.

Helmut

--- libkarma-0.1.2.orig/src/Makefile
+++ libkarma-0.1.2/src/Makefile
@@ -57,17 +57,17 @@
 $(LIBDIR):
 	@[ -d $(LIBDIR) ] || mkdir -p $(LIBDIR) > /dev/null 2>&1
 
-$(LIBDIR)/$(TARGET).a: $(OBJS) $(LIBDIR)
+$(LIBDIR)/$(TARGET).a: $(OBJS) | $(LIBDIR)
 	$(AR) r $(LIBDIR)/$(TARGET).a $(OBJS)
 	$(RANLIB) $(LIBDIR)/$(TARGET).a
 
-$(LIBDIR)/$(OUT_VERSION): $(OBJS) $(LIBDIR)
+$(LIBDIR)/$(OUT_VERSION): $(OBJS) | $(LIBDIR)
 	$(CC) $(LDFLAGS) $(OBJS) $(CFLAGS) -o $(LIBDIR)/$(OUT_VERSION) $(LIBS)
 
-$(LIBDIR)/$(OUT_MAJOR): $(LIBDIR)/$(OUT_VERSION) $(LIBDIR)
+$(LIBDIR)/$(OUT_MAJOR): $(LIBDIR)/$(OUT_VERSION) | $(LIBDIR)
 	$(LN_S) $(OUT_VERSION) $(LIBDIR)/$(OUT_MAJOR)
 
-$(LIBDIR)/$(OUT_BASE): $(LIBDIR)/$(OUT_VERSION) $(LIBDIR)
+$(LIBDIR)/$(OUT_BASE): $(LIBDIR)/$(OUT_VERSION) | $(LIBDIR)
 	$(LN_S) $(OUT_VERSION) $(LIBDIR)/$(OUT_BASE)
 
 shared-lib-stamp: $(LIBDIR)/$(OUT_VERSION) $(LIBDIR)/$(OUT_MAJOR) $(LIBDIR)/$(OUT_BASE)

--- End Message ---
--- Begin Message --- 
Source: libkarma
Source-Version: 0.1.2-4

We believe that the bug you reported is fixed in the latest version of
libkarma, 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 901265@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang <byang@debian.org> (supplier of updated libkarma 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: Tue, 01 Jan 2019 18:36:36 -0500
Source: libkarma
Binary: karma-tools libkarma-cil libkarma-cil-dev libkarma-dev libkarma0
Architecture: source
Version: 0.1.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Boyuan Yang <byang@debian.org>
Description:
 karma-tools - Rio Karma access library [tools]
 libkarma-cil - Rio Karma access library [CLI runtime library]
 libkarma-cil-dev - Rio Karma access library [CLI library development files]
 libkarma-dev - Rio Karma access library [development files]
 libkarma0  - Rio Karma access library [runtime files]
Closes: 901265
Changes:
 libkarma (0.1.2-4) unstable; urgency=medium
 .
   * QA upload.
   * debian/control:
     + Merge Build-Dep-Indep and Build-Dep to simplify dependency
       relationship and fix FTBFS on Debian Buildd.
   * debian/patches:
     + Apply patch to make package cross buildable. (Closes: #901265)
Checksums-Sha1:
 43dd75fb70a926d3a65e6177371c65efb7ae081b 2160 libkarma_0.1.2-4.dsc
 fe70185dd00d81dc8827f2a7ec6a462db05b253e 6136 libkarma_0.1.2-4.debian.tar.xz
 b420508daacbf292ecfbc39ebdc55c0572dd523b 17418 libkarma_0.1.2-4_amd64.buildinfo
Checksums-Sha256:
 d721616db15a0b3deb5c3fb6643caba8829af049dd229c4459584a38b462e874 2160 libkarma_0.1.2-4.dsc
 08ed6ee356b8bce88476fa3704751e711499f312c2277f7dcca5edf3df2fee6d 6136 libkarma_0.1.2-4.debian.tar.xz
 86f088956339c0f89de8891bfee75dc9382f27b8993eb563fda7bc7f2a052244 17418 libkarma_0.1.2-4_amd64.buildinfo
Files:
 cde3e3543f340164e8ff7e2c7c2130c1 2160 libs optional libkarma_0.1.2-4.dsc
 b015aa52ba0c496bb63ee09ceba51e2e 6136 libs optional libkarma_0.1.2-4.debian.tar.xz
 095b2b4deaa0bfc56afe00fef21b7604 17418 libs optional libkarma_0.1.2-4_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlwr/F8ACgkQwpPntGGC
Ws6axxAAh7u49TfRPSltrPZhvLYFKjykPkfB13Rx6kGeNlCHy6PE+zxjdTwIh5h8
zJ+5oq/l3vY4HUlWDA52Z3LYrUwdS0SVpOHWlMnZUR6aRKL4MQ18pHG5s0KNrGab
ZDQ0w5Ff0fqr2JyS/7BUM12/UhWacyYwibnPm94WCWtqLUZ6rdUGTgnFzLqzw+zE
dcRJt/cg/FrE1sZTjIX8gciGuwes/xvGx+FyCobzoijflfYNZlLua4lcQaxvMmam
jk6iKVvhyEd8ClohQRaLdTNIJ5arLYNZXYj0CpY7dQDbIBO1wUmlJKD10zHgomPE
7S1M/Gm1SNsOd0sZgGLmRYoQmVy2nR7wKBVpoa5VGipfOIEZZFzf3LJ3ydbihV8s
PnK0L6BCQ4ffWgAD/OJ/D+yP9V9uBlxbq7dt4muZYnlcJu62ittr71Us/POxnPgU
lvuF2OS+LU1r37Xn+YBot3jswazqtsRvvmdkJ1AoKC2jv/sj3mKlbWs3IzLpuk96
TqoGd/4o7DMSVEMkJKyMK/MVBplHHNygliKFKRrXeFI3lpb4K7NGk5htGgG5MO4Q
pa+ZRXcqdsrU+q/AexCNfU9dlSeurDJ/kjd4DjHyTJ53mjC9RN4XVOpRS4qGPgmr
qVhBGznAdI6349L0V+kvj9UmySQhPHxyMEWZMdcW4vbh8Yq5HgM=
=/k0T
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: