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

Bug#1069179: marked as done (pandoc: use "--enable-executable-dynamic" in d/rules to reduce binary size on loong64)

Your message dated Sat, 20 Apr 2024 23:49:23 +0000
with message-id <E1ryKSR-00E5F1-O4@fasolo.debian.org>
and subject line Bug#1069179: fixed in pandoc 3.1.3+ds-3
has caused the Debian Bug report #1069179,
regarding pandoc: use "--enable-executable-dynamic" in d/rules to reduce binary size on loong64
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.)


-- 
1069179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069179
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: pandoc
Version: 3.1.3+ds-2
Severity: important
Tags: ftbfs patch
User: debian-loongarch@lists.debian.org
Usertags: loong64
X-Debbugs-Cc: wanghonghu@loongson.cn, zhangjialing@loongson.cn, fanpeng@loongson.cn 

Dear maintainers,
The pandoc is blocked from building by haskell-pandoc and haskell-pandoc-lua-engine in the Debian Package Auto-Building environment. I have built haskell-pandoc and haskell-pandoc-lua-engine locally, and then compiling pandoc for loong64 in my local ENV failed.
The error message is related to "relocation R_LARCH_B26 overflow ......" during static linking when built pandoc binary. 
The build error log of pandoc from my local ENV is as follows,
```
[4 of 4] Linking dist-ghc/build/pandoc/pandoc
/usr/bin/ld.bfd: /usr/lib/ghc/lib/../lib/loongarch64-linux-ghc-9.4.7/rts-1.0.2/libHSrts-1.0.2_thr.a(NonMovingMark.thr_o): relocation R_LARCH_B26 overflow 0xfffffffff62f45e4 
Dump relocate record:
stack top        relocation name        symbol
at /usr/lib/gcc/loongarch64-linux-gnu/13/../../../loongarch64-linux-gnu/crt1.o(.text+0x0): 
...
0x0000000000000000 R_LARCH_NONE    `<nameless>' + 3(0x3)
......
```
It is recommended to use "--enable-executable-dynamic" in d/rules to reduce binary size on loong64. The parameter "--enable-executable-dynamic" means "enable dynamic linking of executable files". 
Please consider the patch I attached.
With the attached patch, the pandoc was built successfully in my local ENV.
```
......
if grep -q '^Component:[[:space:]]*main' /CurrentlyBuilding 2>/dev/null; then dh_scour -ppandoc ; fi 
dh_md5sums -ppandoc
dh_builddeb -ppandoc
dpkg-deb: building package 'pandoc' in '../pandoc_3.1.3+ds-2_loong64.deb'.
 dpkg-genbuildinfo -O../pandoc_3.1.3+ds-2_loong64.buildinfo
 dpkg-genchanges -O../pandoc_3.1.3+ds-2_loong64.changes
```

Your opinions are welcome.
In addition, before the pandoc was built for loong64 in the Debian Package Auto-Building environment, could I dupload the pandoc compiled locally using "-enable-executable-dynamic" to the debian-ports/pool-loong64 repository? 
Looking forward to your reply.

Thanks,
Dandan Zhang


diff -Nru pandoc-3.1.3+ds/debian/rules pandoc-3.1.3+ds/debian/rules
--- pandoc-3.1.3+ds/debian/rules	2023-12-21 20:13:11.000000000 +0000
+++ pandoc-3.1.3+ds/debian/rules	2024-01-07 00:52:39.000000000 +0000
@@ -58,6 +58,10 @@
 DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="-O0"
 endif
 
+ifneq (,$(filter $(DEB_HOST_ARCH_CPU), loong64))
+DEB_SETUP_GHC_CONFIGURE_ARGS += --enable-executable-dynamic 
+endif
+
 DEB_SETUP_GHC_CONFIGURE_ARGS += $(if $(filter nocheck,$(DEB_BUILD_OPTIONS)),,-ftests)
 
 DEB_INSTALL_DOCS_ALL += README.md

--- End Message ---
--- Begin Message --- 
Source: pandoc
Source-Version: 3.1.3+ds-3
Done: Jonas Smedegaard <dr@jones.dk>

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

Debian distribution maintenance software
pp.
Jonas Smedegaard <dr@jones.dk> (supplier of updated pandoc 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: Sun, 21 Apr 2024 01:16:47 +0200
Source: pandoc
Architecture: source
Version: 3.1.3+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group <debian-haskell@lists.debian.org>
Changed-By: Jonas Smedegaard <dr@jones.dk>
Closes: 1069179
Changes:
 pandoc (3.1.3+ds-3) unstable; urgency=medium
 .
   * add loong64 as low-memory architecture;
     closes: bug#1069179, thanks to Dandan Zhang
   * declare compliance with Debian Policy 4.7.0
Checksums-Sha1:
 dd437fe5d1f78c734e4051e2b7c5c625d9ef2006 2478 pandoc_3.1.3+ds-3.dsc
 6db70c9188f25fc308e40089dc9cf737b17df2bc 39872 pandoc_3.1.3+ds-3.debian.tar.xz
 f9c415ba82216247728c83ff16c8f08b057a1838 22655 pandoc_3.1.3+ds-3_amd64.buildinfo
Checksums-Sha256:
 5227ad6e893c3b810be1f40cc768567a09eea2bc29701a04da2d46d95accbf05 2478 pandoc_3.1.3+ds-3.dsc
 cf55f3cb0223a0796ff101cea538eba77f5c2c9bbae38762d35b22b02ae8f726 39872 pandoc_3.1.3+ds-3.debian.tar.xz
 570ec9bc1feca28b328c7b26cc2a83efcdbbd2a1f61b2edf51de8dae8dd92279 22655 pandoc_3.1.3+ds-3_amd64.buildinfo
Files:
 6c73ab88b416bc1c8761c2ede86dff0e 2478 text optional pandoc_3.1.3+ds-3.dsc
 f76fabcfdbd4856ec842548af7235437 39872 text optional pandoc_3.1.3+ds-3.debian.tar.xz
 e1f6f36e0e2e787ec3d66288f475bfab 22655 text optional pandoc_3.1.3+ds-3_amd64.buildinfo

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

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYkUQ8ACgkQLHwxRsGg
ASGbXg//TIkPBEhJ7eVw3L6frWp/nDrwTQbvV4B3Ee4L85Pcj5u8/kiPkUFgt4xX
aNcbcpR2LINy7nS+lMk/4ruWv1tS+dW75U3YTLZj9xOj3Ze0KQ43jSh6nxdTIT/b
e9En0aYps6mhklL1WRqB23M34KZBWH9tuSpTO8q0uAnZVrHRfnoinBYsp5f7cHWs
qAqxfE2/sSNWYa5U+3b8vgF0tnuve1iO06vGRNaWcYxYbjYyLkuqOrWXuPoYBNlz
jYH2Z8cH+Yt8U7VSHEQT8LonbXmOSjiz1ymedLG5PBZk/t3FB1K9jnICU3r3d78o
WLq1oGjoHlCdT0U4ALZv7ylVB8J3X8Nl/czHwEL+OG76jXXfVH7LSNKo0Ilobp7t
sMf71jlYf/hU935lBtKg4d226GgY/0p6pXtFekyuXSij1oeg2cVPz+RPrY2XU2Tr
GLJplnrtkRhQJ8UHzCPztOlKFHONvKYemlF8JvtMSrXcG0Fc0hKYtJjM29zY4L0z
s2Nmbz9tq1DKSFaiSQzTQ3iWxDCYdo0Je9IN6eqgcCAQ34vhnx+UghtTqdYXtXV4
qMefV7aiyidnvrXxFwStcZRK/fmqVgT1mMbgA9oOIhU7oDXUC1zJKJ2PURm5Fo1W
WEdrqN2RhmrCC3vjiW4na0yZX/xBygMQjwZipar9hvVSVWRoqwQ=
=92BO
-----END PGP SIGNATURE-----

Attachment: pgpZq7moDMP2D.pgp
Description: PGP signature


--- End Message ---
Reply to: