Built a Debian package using the source code of another one
Hi, the installation/compilation instructions for some proftp modules [1] say: "To install mod_proxy, go to the third-party module area in the proftpd source code and unpack the mod_proxy source tarball: $ cd proftpd-dir/contrib/ $ tar zxvf /path/to/mod_proxy-version.tar.gz after unpacking the latest proftpd-1.3.x source code. For including mod_proxy as a statically linked module: $ ./configure --with-modules=mod_proxy:... To build mod_proxy as a DSO module: $ ./configure --enable-dso --with-shared=mod_proxy:... Then follow the usual steps: $ make $ make install " This works fine. How do I do that for a Debian package? I've seen [2], but this is not my use case: I want the proftp module in an own Debian package. Of course one could find out, which part of the proftp source tree is needed to build the module and put this into debian.tar.xz, but this gives a rather big source package and I'm not sure how fragile this will be. Any hints? Hilmar [1] https://htmlpreview.github.io/?https://github.com/Castaglia/proftpd-mod_proxy/blob/master/mod_proxy.html#Installation [2] https://raphaelhertzog.com/2010/09/07/how-to-use-multiple-upstream-tarballs-in-debian-source-packages/ -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: [Help] pvm: ftbfs with GCC-10
Control: tags -1 patch Hi Andreas, This lead to the trail: > : error: 'pvmd' undeclared (first use in this function) > /build/pvm-3.4.6/src/ddpro.c:1031:14: note: in expansion of macro 'PVMDPATH' > 1031 | pvmdpath = PVMDPATH; > | ^~~~ Definition of PVMDPATH and friends is cascaded through a tool chain from debian/rules, but double quotes went missing for some reason, maybe with the debhelper compatibility level bump. Thus, the undefined symbol _pvmd_ ended up into the C code, instead of the string _"pvmd"_. --8< diff --git a/debian/rules b/debian/rules index b1d217b..92a6247 100755 --- a/debian/rules +++ b/debian/rules @@ -11,7 +11,7 @@ soversion=3 # yes, I know this will define RSHCOMMAND twice and generate a warning. # I'm not modifying gcc. -dld # -export DEB_CPPFLAGS_MAINT_APPEND=-DRSHCOMMAND=\\\"/usr/lib/pvm3/bin/rsh\\\" -DPVMDPATH=\\\"pvmd\\\" -DPVMDFILE=\\\"/usr/bin/pvmd\\\" -DPVM_DEFAULT_ROOT=\\\"/usr/lib/pvm3\\\" -DOVERLOADHOST +export DEB_CPPFLAGS_MAINT_APPEND=-DRSHCOMMAND=\\\"/usr/lib/pvm3/bin/rsh\\\" -DPVMDPATH=\\\"pvmd\\\" -DPVMDFILE=\\\"/usr/bin/pvmd\\\" -DPVM_DEFAULT_ROOT=\\\"/usr/lib/pvm3\\\" -DOVERLOADHOST export DEB_BUILD_MAINT_OPTIONS=hardening=+all include /usr/share/dpkg/architecture.mk export DEB_HOST_MULTIARCH @@ -80,7 +80,7 @@ override_dh_auto_install: ln -s libgpvm3.so.$(version) debian/libpvm3/usr/lib/$(DEB_HOST_MULTIARCH)/libgpvm3.so.$(soversion) # pvm-examples package - mv bin/$(PVM_ARCH)/gs debian/pvm-examples/usr/bin/gs.pvm + #mv bin/$(PVM_ARCH)/gs debian/pvm-examples/usr/bin/gs.pvm mv bin/$(PVM_ARCH)/hello debian/pvm-examples/usr/bin/hello.pvm mv bin/$(PVM_ARCH)/srm debian/pvm-examples/usr/bin/srm.pvm cp bin/$(PVM_ARCH)/* debian/pvm-examples/usr/bin/ -->8 I hope this helps, but I must admit it seems rather fragile. :( Kind Regards, -- Étienne Mollier Old rsa/3072: 5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d New rsa/4096: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/4, please excuse my verbosity. signature.asc Description: PGP signature
Issues with parallel build (Was: Linker issues for libssw on armel, mips64el and mipsel)
Hi, On Wed, Aug 12, 2020 at 09:01:07AM +0100, Steve McIntyre wrote: > On Wed, Aug 12, 2020 at 09:33:31AM +0200, Andreas Tille wrote: > >... > >c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > >-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > >-Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 > >-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -I"/include" -I"/include/linux" > >-I/usr/lib/jvm/default-java/include/ > >-I/usr/lib/jvm/default-java/include/linux -fPIC -shared -rdynamic -o > >libsswjni.so sswjni.c ssw.c -Wl,-z,relro -Wl,-z,now > >cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > >-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > >-Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 > >-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -o ssw-align main.c kseq.h -L. -lssw > >-lm -lz -Wl,-z,relro -Wl,-z,now > >/usr/bin/ld: cannot find -lssw > >... > > > >(same on some non-released architectures). > > > >Any idea how to fix this? > > Comparing the buildd logs for arm64 and armel, there are obvious > differences - on armel the build doesn't even attempt to make the > library libssw.a. Check the Makefiles etc. to see if it has hard-coded > architecture support? I failed to find some architecture specific issues (as long as ifneq ($(filter nojava,$(DEB_BUILD_PROFILES)),) is not filtering for certain architectures implicitly.) I think the issue is connected to parallel builds. After comparing build logs which look pretty similar between amd64 and armel I suspected that there is some issue with parallel builds and forced --no-parallel with the result that the build now even fails for amd64: dh_auto_build --no-parallel --sourcedirectory src -- default java cd src && make -j1 "INSTALL=install --strip-program=true" default java make[2]: Entering directory '/build/libssw-1.1/src' g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/libssw-1.1=. -fstack-protector-strong -Wformat -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -fPIC -shared -rdynamic -Wl,-soname,libssw.so.0 -o libssw.so.0 ssw.c ssw.h ssw_cpp.h ssw_cpp.cpp -Wl,-z,relro -Wl,-z,now cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/libssw-1.1=. -fstack-protector-strong -Wformat -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -o ssw-align main.c kseq.h -L. -lssw -lm -lz -Wl,-z,relro -Wl,-z,now /usr/bin/ld: cannot find -lssw Michael Crusoe confirmed that The package builds for me on armel as of https://salsa.debian.org/med-team/libssw/-/commit/a19c146931e078e0e56abc85684f5a3583165e63 so perhaps the issue was introduced later? I admit I re-applied former patches to create a static lib which was kicked by the SIMDE patches but it seems I messed up the Makefile. Any second pair of eyeballs finding what I might have made wrong in Git[1] between the commit above and HEAD when re-adding the static lib that was droped at some point in time? Kind regards Andreas. [1] https://salsa.debian.org/med-team/libssw -- http://fam-tille.de
Bug#968153: RFS: tinymux/2.12.0.10-1 -- text-based multi-user virtual world server
Thanks. I've setup pbuilder, re-built (without issue), and uploaded the signed package again with dput. On Wed, Aug 12, 2020 at 4:04 AM Baptiste BEAUPLAT wrote: > Hi Stephen, > > On 8/12/20 7:22 AM, Stephen Dennis wrote: > > It builds and rebuilds for me on two different clean Debian > environments. I > > have never gotten the '/usr/bin/ld: cannot find -lmux' error. Adam hasn't > > responded in two days and is probably waiting for me to fix an error I > > cannot reproduce. Can anyone else build it? Am I building this a wrong > way? > > > > dpkg-buildpackage -k<...> > > lintian > > dput > > You will need to use sbuild[1] or pbuilder[2] to create clean minimal > Debian build environment. > > [1]: https://wiki.debian.org/sbuild > [2]: https://www.debian.org/doc/manuals/maint-guide/build.en.html#pbuilder > > -- > Baptiste BEAUPLAT - lyknode > >
Bug#968153: RFS: tinymux/2.12.0.10-1 -- text-based multi-user virtual world server
Hi Stephen, On 8/12/20 7:22 AM, Stephen Dennis wrote: > It builds and rebuilds for me on two different clean Debian environments. I > have never gotten the '/usr/bin/ld: cannot find -lmux' error. Adam hasn't > responded in two days and is probably waiting for me to fix an error I > cannot reproduce. Can anyone else build it? Am I building this a wrong way? > > dpkg-buildpackage -k<...> > lintian > dput You will need to use sbuild[1] or pbuilder[2] to create clean minimal Debian build environment. [1]: https://wiki.debian.org/sbuild [2]: https://www.debian.org/doc/manuals/maint-guide/build.en.html#pbuilder -- Baptiste BEAUPLAT - lyknode signature.asc Description: OpenPGP digital signature
Re: [Help] f2j: ftbfs with GCC-10
On Wed, Aug 12, 2020 at 10:53:24AM +0100, Sudip Mukherjee wrote: > Try the attached patch. Thanks, this works Andreas. -- http://fam-tille.de
Re: [Help] f2j: ftbfs with GCC-10
HI Andreas, On Wed, Aug 12, 2020 at 8:10 AM Andreas Tille wrote: > > Control: tags -1 help > > Hi, > > I think I've fixed part of the problem in Git[1]. Unfortunately there is a > remainig "multiple definition" issue where I have no idea how to fix it: Try the attached patch. -- Regards Sudip --- f2j-0.8.1+dfsg.orig/src/optimize.c +++ f2j-0.8.1+dfsg/src/optimize.c @@ -46,7 +46,7 @@ int optdebug = FALSE; -char *unit_name;/* name of this function/subroutine */ +extern char *unit_name;/* name of this function/subroutine */ /* * Function prototypes: *
Re: [Help] pvm: ftbfs with GCC-10
Andreas Tille writes: > while I do not intend to maintain pvm personally some Debian Med package > depend from it. Thus I like to see bug #957717 fixed but I need help. Do people still use PVM for parallel computing? I thought it was replaced by MPI decades ago. If use of PVM is optional, I would consider disabling use of PVM in reverse dependencies and just remove the unmaintained PVM package from Debian. Ansgar
Re: Linker issues for libssw on armel, mips64el and mipsel
On Wed, Aug 12, 2020 at 09:33:31AM +0200, Andreas Tille wrote: >Hi, > >while the package libssw builds nicely on most architectures on armel, >mips64el and mipsel there is a linking issue[1]: > >... >c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. >-fstack-protector-strong -Wformat -Werror=format-security >-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -fopenmp-simd >-O3 -I"/include" -I"/include/linux" -I/usr/lib/jvm/default-java/include/ >-I/usr/lib/jvm/default-java/include/linux -fPIC -shared -rdynamic -o >libsswjni.so sswjni.c ssw.c -Wl,-z,relro -Wl,-z,now >cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 >-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat >-Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 >-DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -o ssw-align main.c kseq.h -L. -lssw >-lm -lz -Wl,-z,relro -Wl,-z,now >/usr/bin/ld: cannot find -lssw >... > >(same on some non-released architectures). > >Any idea how to fix this? Comparing the buildd logs for arm64 and armel, there are obvious differences - on armel the build doesn't even attempt to make the library libssw.a. Check the Makefiles etc. to see if it has hard-coded architecture support? -- Steve McIntyre, Cambridge, UK.st...@einval.com "The problem with defending the purity of the English language is that English is about as pure as a cribhouse whore. We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary." -- James D. Nicoll
Linker issues for libssw on armel, mips64el and mipsel
Hi, while the package libssw builds nicely on most architectures on armel, mips64el and mipsel there is a linking issue[1]: ... c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -I"/include" -I"/include/linux" -I/usr/lib/jvm/default-java/include/ -I/usr/lib/jvm/default-java/include/linux -fPIC -shared -rdynamic -o libsswjni.so sswjni.c ssw.c -Wl,-z,relro -Wl,-z,now cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -o ssw-align main.c kseq.h -L. -lssw -lm -lz -Wl,-z,relro -Wl,-z,now /usr/bin/ld: cannot find -lssw ... (same on some non-released architectures). Any idea how to fix this? Kind regards Andreas. [1] https://buildd.debian.org/status/package.php?p=libssw -- http://fam-tille.de
[Help] f2j: ftbfs with GCC-10
Control: tags -1 help Hi, I think I've fixed part of the problem in Git[1]. Unfortunately there is a remainig "multiple definition" issue where I have no idea how to fix it: ex.o f2jmain.o symtab.o codegen.o vcg_emitter.o dlist.o typecheck.o optimize.o globals.o f2jmem.o -L/build/f2j-0.8.1+dfsg/libbytecode -lbytecode -Wl,-z,relro -Wl,-z,now /usr/bin/ld: optimize.o:./src/optimize.c:49: multiple definition of `unit_name'; codegen.o:./src/codegen.c:28: first defined here collect2: error: ld returned 1 exit status make[2]: *** [Makefile:20: f2java] Error 1 Any hint would be welcome Andreas. [1] https://salsa.debian.org/java-team/f2j/-/commit/fa634211dbef57ba6fda8121c3a565bafa73beed (please review) -- http://fam-tille.de
