Re: Autoconf issue in mpqc
On 2020-04-05, at 14:32:16 +0200, Andreas Tille wrote: > On Sun, Apr 05, 2020 at 12:34:55PM +0100, Jeremy Sowden wrote: > > > > I've attached the part or the build log that seems to be > > > > autoconf relevant. I admit I'm a bit astonished since I can > > > > only see warnings but no error ... > > > > > > Here's a patch that fixes the autoheader warnings. > > > > Whoops. That version doesn't seem to apply. The patch I've > > attached to this message I have actually tested properly. > > > > > autoreconf is still failing. > > > > That's not quite right: "autoreconf" fails, but "autoreconf -f -i" > > (which is what dh_autoreconf does) succeeds. Now dh_auto_configure > > fails. > > I confirm it fails with > > ... > checking if semctl requires semun... no > checking if fortran compiler works... no > configure: error: in `/build/mpqc-2.3.1': > configure: error: fortran compiler does not work > > > I've updated Git with your patch - thanks a lot so far. In my case, the problem was: ./configure: line 4287: mpicc: command not found IOW, missing build-deps. Once I installed those, dh_auto_configure was happy, but there were compilation failures because autoheader clobbered src/lib/scconfig.h.in. I've attached two patches which fix those. J. From 179ea7ad88afe65c49976fe713e7e061692d51cf Mon Sep 17 00:00:00 2001 From: Jeremy Sowden Date: Sun, 5 Apr 2020 20:22:51 +0100 Subject: [PATCH 1/2] shmtype fix. --- debian/patches/series| 1 + debian/patches/shmtype.patch | 45 2 files changed, 46 insertions(+) create mode 100644 debian/patches/shmtype.patch diff --git a/debian/patches/series b/debian/patches/series index db79d4fb8ff5..c5ef93ff27ed 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -12,3 +12,4 @@ g++6-constexpr.patch Fix_mpi.patch autoconf.patch autoheader.patch +shmtype.patch diff --git a/debian/patches/shmtype.patch b/debian/patches/shmtype.patch new file mode 100644 index ..0a8273be680a --- /dev/null +++ b/debian/patches/shmtype.patch @@ -0,0 +1,45 @@ +diff --git a/src/lib/scconfig.h.in b/src/lib/scconfig.h.in +index 81510ae39834..8ca70c95073d 100644 +--- a/src/lib/scconfig.h.in b/src/lib/scconfig.h.in +@@ -156,10 +156,6 @@ + /* Define to the type used for shared memory. */ + /* #undef SHMTYPE */ + +-#ifndef SHMTYPE +-#define SHMTYPE char* +-#endif +- + /* Define if you have the header file. */ + #undef HAVE_FCNTL_H + +diff --git a/src/lib/util/group/memshm.cc b/src/lib/util/group/memshm.cc +index 91964682b7f0..1314e43f01ec 100644 +--- a/src/lib/util/group/memshm.cc b/src/lib/util/group/memshm.cc +@@ -41,6 +41,10 @@ + using namespace std; + using namespace sc; + ++#ifndef SHMTYPE ++#define SHMTYPE char* ++#endif ++ + #ifndef SHMMAX + // glibc 2.0.3 isn't defining SHMMAX so make set it here + # ifdef __linux__ +diff --git a/src/lib/util/group/messshm.cc b/src/lib/util/group/messshm.cc +index f07fe1a79fde..34ee31e1ddbf 100644 +--- a/src/lib/util/group/messshm.cc b/src/lib/util/group/messshm.cc +@@ -40,6 +40,10 @@ + using namespace std; + using namespace sc; + ++#ifndef SHMTYPE ++#define SHMTYPE char* ++#endif ++ + //#define DEBUG + + #ifndef SEM_A -- 2.25.1 From 4d6bd8fc829d385bc05d696780429a03d915b18f Mon Sep 17 00:00:00 2001 From: Jeremy Sowden Date: Sun, 5 Apr 2020 20:58:57 +0100 Subject: [PATCH 2/2] restrictxx fix. --- debian/patches/restrictxx.patch | 102 debian/patches/series | 1 + 2 files changed, 103 insertions(+) create mode 100644 debian/patches/restrictxx.patch diff --git a/debian/patches/restrictxx.patch b/debian/patches/restrictxx.patch new file mode 100644 index ..e86d7d1a95e3 --- /dev/null +++ b/debian/patches/restrictxx.patch @@ -0,0 +1,102 @@ +diff --git a/src/lib/scconfig.h.in b/src/lib/scconfig.h.in +index 81510ae39834..3eaea90920ab 100644 +--- a/src/lib/scconfig.h.in b/src/lib/scconfig.h.in +@@ -14,12 +14,6 @@ + /* Define if the C++ restrict keyword extension exists. */ + #undef CXX_RESTRICT + +-#ifdef CXX_RESTRICT +-#define restrictxx restrict +-#else +-#define restrictxx +-#endif +- + #endif + + /* Define if you want to optimize the reference counting code. */ +diff --git a/src/lib/chemistry/qc/intv3/build2e.cc b/src/lib/chemistry/qc/intv3/build2e.cc +index 1179f9dcb6d2..fec356986d33 100644 +--- a/src/lib/chemistry/qc/intv3/build2e.cc b/src/lib/chemistry/qc/intv3/build2e.cc +@@ -36,6 +36,12 @@ + #include + #include + ++#ifdef CXX_RESTRICT ++#define restrictxx restrict ++#else ++#define restrictxx ++#endif ++ + using namespace std; + using namespace sc; + +diff --git a/src/lib/chemistry/qc/intv3/shift2e.cc b/src/lib/chemistry/qc/intv3/shift2e.cc +index 97d9f24df6a0..5a01bff73894 100644 +--- a/src/lib/chemistry/qc/intv3/shift2e.cc b/src/lib/chemistry/qc/intv3/shift2e.cc +@@ -29,6 +29,12 @@ + #include + #include + ++#ifdef CXX_RESTRICT ++#define restrictxx restrict ++#else ++#define
Bug#955496: RFS: libsys-hostaddr-perl/0.993-1 [ITP] -- Get IP address information about this host
On Wed, Apr 01, 2020 at 05:51:28PM +0200, Hilmar Preusse wrote:
> * Package name: libsys-hostaddr-perl
>Version : 0.993-1
>Upstream Author : Jeremy Kister|http://jeremy.kister.net/
> * URL : https://metacpan.org/release/Sys-HostAddr
> Changes since the last upload:
>
>* Initial release. (Closes: #955449).
Hi!
I'm not quite sure if this particular implementation is adequate. So far
I noticed that it:
* has seen no updates since 2014
* relies on a long-deprecated interface, via a tool that hasn't seen an
upstream release since April 2001
* has non-working support for IPv6
* its support for IPv4 isn't stellar either
* doesn't handle lack of answer or answers it doesn't understand
* provides only partial answers
For example:
perl -e 'use Sys::HostAddr;use Data::Dumper; print "\e[33m$_\e[0m\n",
eval("Dumper(Sys::HostAddr->new()->$_())") for qw(public interfaces addresses
ip first_ip main_ip)'
Modification of a read-only value attempted at /usr/share/perl5/Sys/HostAddr.pm
line 68.
public
$VAR1 = undef;
interfaces
$VAR1 = [
'br0',
'eth0',
'lo'
];
addresses
$VAR1 = [
'10.0.1.9',
'127.0.0.1'
];
ip
$VAR1 = {
'lo' => [
{
'netmask' => '255.0.0.0',
'address' => '127.0.0.1'
}
],
'br0' => [
{
'netmask' => '255.255.255.0',
'address' => '10.0.1.9'
}
]
};
first_ip
$VAR1 = '10.0.1.9';
main_ip
$VAR1 = '10.0.1.9';
(error message from public(), 192.168.0.9 on br0 is missing in other calls)
After disabling legacy IP:
Can't use an undefined value as a symbol reference at
/usr/share/perl5/Sys/HostAddr.pm line 60.
public
$VAR1 = undef;
interfaces
$VAR1 = [
'br0',
'eth0',
'lo'
];
addresses
$VAR1 = [
'127.0.0.1'
];
ip
$VAR1 = {
'lo' => [
{
'netmask' => '255.0.0.0',
'address' => '127.0.0.1'
}
]
};
first_ip
main_ip
(a different error from public())
Thus, I wonder if there's a better module to do this task.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi
⠈⠳⣄
Bug#955512: marked as done (RFS: sane-backends/1.0.29-1~experimental2 -- API library for scanners -- utilities)
Your message dated Sun, 5 Apr 2020 19:34:13 +0200 with message-id <20200405173413.gc30...@angband.pl> and subject line Re: Bug#955512: RFS: sane-backends/1.0.29-1~experimental2 -- API library for scanners -- utilities has caused the Debian Bug report #955512, regarding RFS: sane-backends/1.0.29-1~experimental2 -- API library for scanners -- utilities 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 ow...@bugs.debian.org immediately.) -- 955512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "sane-backends" Package name: sane-backends Version : 1.0.29-1~experimental2 Upstream Author : [fill in name and email of upstream] URL : http://www.sane-project.org License : GPL-2+ with sane exception Vcs : https://jff.email/cgit/sane-backends.git Section : graphics It builds those binary packages: sane-utils - API library for scanners -- utilities libsane-common - API library for scanners -- documentation and support files libsane1 - API library for scanners libsane-dev - API development library for scanners [development files] To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sane-backends Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sane-backends/sane-backends_1.0.29-1~experimental2.dsc or from git https://jff.email/cgit/sane-backends.git?h=release%2Fexperimental%2F1.0.29-1_experimental2 Changes since the last upload: * New debian/patches/0150-i386-test.patch: - Remove 4 tests failed tests on i386. * New patches/0155-hurd_PATH_MAX.patch: - Fix missing PATH_MAX on hurd-i386. * New patches/0160-big_endian.patch: - Fix FTBFS on big endian systems. * Remove now useless lintian overrides. CU Jörg Frings-Fürst -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- On Wed, Apr 01, 2020 at 10:59:44PM +0200, Jörg Frings-Fürst wrote: >Package name: sane-backends >Version : 1.0.29-1~experimental2 > Changes since the last upload: > >* New debian/patches/0150-i386-test.patch: > - Remove 4 tests failed tests on i386. >* New patches/0155-hurd_PATH_MAX.patch: > - Fix missing PATH_MAX on hurd-i386. >* New patches/0160-big_endian.patch: > - Fix FTBFS on big endian systems. >* Remove now useless lintian overrides. Uploaded. Note, though, that the Release Team has requested to be notified before this package gets uploaded to unstable. Once you're ready, it will be time to coordinate the transition. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄--- End Message ---
Bug#955753: marked as done (RFS: ck/0.6.0-1.4 [NMU, RC] -- Concurrency Kit)
Your message dated Sun, 5 Apr 2020 19:13:13 +0200 with message-id <20200405171313.gb30...@angband.pl> and subject line Re: Bug#955753: RFS: ck/0.6.0-1.4 [NMU, RC] -- Concurrency Kit has caused the Debian Bug report #955753, regarding RFS: ck/0.6.0-1.4 [NMU, RC] -- Concurrency Kit 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 ow...@bugs.debian.org immediately.) -- 955753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for "ck" * Package name: ck Version : 0.6.0-1.4 Upstream Author : Samy Al Bahra * URL : http://concurrencykit.org/ * License : BSD-2-clause * Vcs : https://anonscm.debian.org/cgit/collab-maint/ck.git Section : libs It builds those binary packages: libck0 - Concurrency Kit - shared libraries libck-dev - Concurrency Kit - development files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ck Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/ck/ck_0.6.0-1.4.dsc Changes since the last upload: * Non-maintainer upload. * Explicitly set the platform option when building for armhf rather than rely on the configure script's autodetection. I'm doing another nmu for ck, as the previous one (0.6.0-1.3) failed to build for armhf [1], preventing migration [2]. Build failure occurs because the configure script fails to autodetect the platform, for no apparent reason. That problem didn't exist in previous builds and also doesn't happen when building -1.3 in ubuntu [3] for any architecture, armhf included. The changes made in -1.3 didn't involve the configure script in any way. [1] https://buildd.debian.org/status/fetch.php?pkg=ck=armhf=0.6.0-1.3=1585323705=0 [2] https://qa.debian.org/excuses.php?package=ck [3] https://launchpad.net/ubuntu/+source/ck/0.6.0-1.3 Thank you! pgpDHwC9JJlIZ.pgp Description: OpenPGP digital signature --- End Message --- --- Begin Message --- On Sat, Apr 04, 2020 at 05:37:45PM +0200, JCF Ploemen wrote: > * Package name: ck >Version : 0.6.0-1.4 > Changes since the last upload: > >* Non-maintainer upload. >* Explicitly set the platform option when building for armhf > rather than rely on the configure script's autodetection. > > I'm doing another nmu for ck, as the previous one (0.6.0-1.3) failed to > build for armhf [1], preventing migration [2]. Build failure occurs > because the configure script fails to autodetect the platform, for no > apparent reason. > > That problem didn't exist in previous builds and also doesn't happen > when building -1.3 in ubuntu [3] for any architecture, armhf included. > The changes made in -1.3 didn't involve the configure script in any way. The cause is the armhf buildds running on 64-bit hardware (just like i386 runs on amd64 for more than a decade). This wouldn't be a problem if the upstream configure script asked eg. the compiler, but instead it checks "uname -m" which is never the right thing to do. On my test box it says "armv8l" which is not on ck's list. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄--- End Message ---
Bug#955862: RFS: sphinx-autoapi/1.2.1-1 [ITP]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "sphinx-autoapi", which is needed for the newest version of khard. * Package name: sphinx-autoapi Version : 1.2.1-1 Upstream Author : Read the Docs, Inc * URL : https://github.com/readthedocs/sphinx-autoapi/ * License : Expat * Vcs : https://salsa.debian.org/python-team/modules/sphinx-autoapi.git Section : python It builds those binary packages: python3-sphinx-autoapi - Sphinx AutoAPI provides "autodoc" style documentation for multiple programming languages without needing to load, run, or import the project being documented. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sphinx-autoapi Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sphinx-autoapi/sphinx-autoapi_1.2.1-1.dsc Changes since the last upload: * Initial release. (Closes: #955819). -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Félix signature.asc Description: PGP signature
Re: Autoconf issue in mpqc
On Sun, Apr 05, 2020 at 12:34:55PM +0100, Jeremy Sowden wrote: > > > I've attached the part or the build log that seems to be autoconf > > > relevant. I admit I'm a bit astonished since I can only see > > > warnings but no error ... > > > > Here's a patch that fixes the autoheader warnings. > > Whoops. That version doesn't seem to apply. The patch I've attached to > this message I have actually tested properly. > > > autoreconf is still failing. > > That's not quite right: "autoreconf" fails, but "autoreconf -f -i" > (which is what dh_autoreconf does) succeeds. Now dh_auto_configure > fails. I confirm it fails with ... checking if semctl requires semun... no checking if fortran compiler works... no configure: error: in `/build/mpqc-2.3.1': configure: error: fortran compiler does not work I've updated Git with your patch - thanks a lot so far. Kind regards Andreas. -- http://fam-tille.de
Bug#955696: marked as done (RFS: kcheckers/0.8.1-5 [QA] -- Checkers boardgame)
Your message dated Sun, 5 Apr 2020 14:27:49 +0200 with message-id <20200405122749.ga30...@angband.pl> and subject line Re: Bug#955696: RFS: kcheckers/0.8.1-5 [QA] -- Checkers boardgame has caused the Debian Bug report #955696, regarding RFS: kcheckers/0.8.1-5 [QA] -- Checkers boardgame 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 ow...@bugs.debian.org immediately.) -- 955696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "kcheckers" * Package name: kcheckers Version : 0.8.1-5 Upstream Author : Andi Peredri Artur Wiebe * URL : http://qcheckers.sourceforge.net/ * License : GPL-2.0+ * Vcs : https://salsa.debian.org/debian/kcheckers Section : games It builds those binary packages: kcheckers - Checkers boardgame To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kcheckers Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kcheckers/kcheckers_0.8.1-5.dsc Changes since the last upload: * QA upload. * Orphan the package. (See: #922893) * Update Standards-Version to 4.5.0 * Update compat level to 12. * Link copyright to GPL-2. * Add newline to d/rules. * Add Vcs link to salsa. * Fix FTCBFS. (Closes: #940147) - Thanks to Helmut Grohne. -- Regards Sudip --- End Message --- --- Begin Message --- On Fri, Apr 03, 2020 at 09:12:24PM +0100, Sudip Mukherjee wrote: > * Package name: kcheckers >Version : 0.8.1-5 > Changes since the last upload: > >* QA upload. >* Orphan the package. (See: #922893) >* Update Standards-Version to 4.5.0 >* Update compat level to 12. >* Link copyright to GPL-2. >* Add newline to d/rules. >* Add Vcs link to salsa. >* Fix FTCBFS. (Closes: #940147) > - Thanks to Helmut Grohne. It's sad to remove one more mention of Innocent. Uploaded. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄--- End Message ---
Re: Autoconf issue in mpqc
On 2020-04-05, at 12:13:45 +0100, Jeremy Sowden wrote: > On 2020-04-05, at 12:45:47 +0200, Andreas Tille wrote: > > On Sun, Apr 05, 2020 at 10:14:58AM +0100, Jeremy Sowden wrote: > > > > Any help would be appreciated. > > > > > > > > [1] https://salsa.debian.org/debichem-team/mpqc > > > > > > Adding AC_CONFIG_MACRO_DIR to configure.in appears to fix it > > > (patch attached). > > > > Thanks a lot for the promising patch I have commited to Git[1]. > > Unfortunately the build does not yet succeed in a pbuilder chroot. > > I've attached the part or the build log that seems to be autoconf > > relevant. I admit I'm a bit astonished since I can only see > > warnings but no error ... > > Here's a patch that fixes the autoheader warnings. Whoops. That version doesn't seem to apply. The patch I've attached to this message I have actually tested properly. > autoreconf is still failing. That's not quite right: "autoreconf" fails, but "autoreconf -f -i" (which is what dh_autoreconf does) succeeds. Now dh_auto_configure fails. J. diff --git a/debian/patches/autoheader.patch b/debian/patches/autoheader.patch new file mode 100644 index ..f00d772e29ef --- /dev/null +++ b/debian/patches/autoheader.patch @@ -0,0 +1,69 @@ +diff --git a/configure.in b/configure.in +index 99a09d38b3c2..c183ac3ef252 100644 +--- a/configure.in b/configure.in +@@ -11,6 +11,8 @@ AC_CONFIG_HEADER(src/lib/scconfig.h) + AC_CONFIG_AUX_DIR(bin) + AC_CONFIG_MACRO_DIR([lib/autoconf]) + ++AC_DEFINE_HEADER_TEMPLATES ++ + AC_CANONICAL_SYSTEM + + AC_DEFINE_UNQUOTED(HOST_ARCH, "$host") +diff --git a/lib/autoconf/templates.m4 b/lib/autoconf/templates.m4 +new file mode 100644 +index ..693d54289326 +--- /dev/null b/lib/autoconf/templates.m4 +@@ -0,0 +1,50 @@ ++AC_DEFUN([AC_DEFINE_HEADER_TEMPLATES],[ ++AH_TEMPLATE([ALWAYS_USE_MPI], []) ++AH_TEMPLATE([CXX_RESTRICT], []) ++AH_TEMPLATE([DEFAULT_ARMCI], []) ++AH_TEMPLATE([DEFAULT_MPI], []) ++AH_TEMPLATE([DEFAULT_MTMPI], []) ++AH_TEMPLATE([DEFAULT_SC_MEMORY], []) ++AH_TEMPLATE([EXPLICIT_TEMPLATE_INSTANTIATION], []) ++AH_TEMPLATE([HAVE_ARMCI], []) ++AH_TEMPLATE([HAVE_BACKTRACE], []) ++AH_TEMPLATE([HAVE_CCA_CHEM_HEADERS], []) ++AH_TEMPLATE([HAVE_CCA_SPEC_BABEL_HEADERS], []) ++AH_TEMPLATE([HAVE_FCHDIR], []) ++AH_TEMPLATE([HAVE_IOS_FMTFLAGS], []) ++AH_TEMPLATE([HAVE_ISNAN], []) ++AH_TEMPLATE([HAVE_LIBDERIV], []) ++AH_TEMPLATE([HAVE_LIBINT], []) ++AH_TEMPLATE([HAVE_LIBR12], []) ++AH_TEMPLATE([HAVE_LONG_LONG], []) ++AH_TEMPLATE([HAVE_MPI], []) ++AH_TEMPLATE([HAVE_MPIIO], []) ++AH_TEMPLATE([HAVE_MPIPP], []) ++AH_TEMPLATE([HAVE_MPI_INIT_THREAD], []) ++AH_TEMPLATE([HAVE_NIAMA], []) ++AH_TEMPLATE([HAVE_PERF], []) ++AH_TEMPLATE([HAVE_PTHREAD], []) ++AH_TEMPLATE([HAVE_PUBSEEKOFF], []) ++AH_TEMPLATE([HAVE_SCALABLE_BLAS], []) ++AH_TEMPLATE([HAVE_SEEKOFF], []) ++AH_TEMPLATE([HAVE_SGETN], []) ++AH_TEMPLATE([HAVE_SIDL_HEADERS], []) ++AH_TEMPLATE([HAVE_SYSV_IPC], []) ++AH_TEMPLATE([HAVE_TYPENAME], []) ++AH_TEMPLATE([HOST_ARCH], []) ++AH_TEMPLATE([INSTALLED_SCLIBDIR], []) ++AH_TEMPLATE([REF_OPTIMIZE], []) ++AH_TEMPLATE([SCDATADIR], []) ++AH_TEMPLATE([SC_BUILDID], []) ++AH_TEMPLATE([SC_MAJOR_VERSION], []) ++AH_TEMPLATE([SC_MICRO_VERSION], []) ++AH_TEMPLATE([SC_MINOR_VERSION], []) ++AH_TEMPLATE([SC_MPI_THREAD_LEVEL], []) ++AH_TEMPLATE([SC_VERSION], []) ++AH_TEMPLATE([SEMCTL_REQUIRES_SEMUN], []) ++AH_TEMPLATE([SIGHASELLIP], []) ++AH_TEMPLATE([SRC_SCLIBDIR], []) ++AH_TEMPLATE([TARGET_ARCH], []) ++AH_TEMPLATE([USING_NAMESPACE_STD], []) ++AH_TEMPLATE([WORDS_BIGENDIAN], []) ++]) diff --git a/debian/patches/series b/debian/patches/series index d700ae497e80..db79d4fb8ff5 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -11,3 +11,4 @@ g++6-constexpr.patch Fix_mpi.patch autoconf.patch +autoheader.patch signature.asc Description: PGP signature
Re: Autoconf issue in mpqc
On 2020-04-05, at 12:45:47 +0200, Andreas Tille wrote: > Hi Jeremy, > > On Sun, Apr 05, 2020 at 10:14:58AM +0100, Jeremy Sowden wrote: > > > Any help would be appreciated. > > > > > > [1] https://salsa.debian.org/debichem-team/mpqc > > > > Adding AC_CONFIG_MACRO_DIR to configure.in appears to fix it (patch > > attached). > > Thanks a lot for the promising patch I have commited to Git[1]. > Unfortunately the build does not yet succeed in a pbuilder chroot. > I've attached the part or the build log that seems to be autoconf > relevant. I admit I'm a bit astonished since I can only see > warnings but no error ... Here's a patch that fixes the autoheader warnings. autoreconf is still failing. J. > [...] > autoheader: warning: missing template: ALWAYS_USE_MPI > autoheader: Use AC_DEFINE([ALWAYS_USE_MPI], [], [Description]) > autoheader: warning: missing template: CXX_RESTRICT > autoheader: warning: missing template: DEFAULT_ARMCI > autoheader: warning: missing template: DEFAULT_MPI > autoheader: warning: missing template: DEFAULT_MTMPI > autoheader: warning: missing template: DEFAULT_SC_MEMORY > autoheader: warning: missing template: EXPLICIT_TEMPLATE_INSTANTIATION > autoheader: warning: missing template: HAVE_ARMCI > autoheader: warning: missing template: HAVE_BACKTRACE > autoheader: warning: missing template: HAVE_CCA_CHEM_HEADERS > autoheader: warning: missing template: HAVE_CCA_SPEC_BABEL_HEADERS > autoheader: warning: missing template: HAVE_FCHDIR > autoheader: warning: missing template: HAVE_IOS_FMTFLAGS > autoheader: warning: missing template: HAVE_ISNAN > autoheader: warning: missing template: HAVE_LIBDERIV > autoheader: warning: missing template: HAVE_LIBINT > autoheader: warning: missing template: HAVE_LIBR12 > autoheader: warning: missing template: HAVE_LONG_LONG > autoheader: warning: missing template: HAVE_MPI > autoheader: warning: missing template: HAVE_MPIIO > autoheader: warning: missing template: HAVE_MPIPP > autoheader: warning: missing template: HAVE_MPI_INIT_THREAD > autoheader: warning: missing template: HAVE_NIAMA > autoheader: warning: missing template: HAVE_PERF > autoheader: warning: missing template: HAVE_PTHREAD > autoheader: warning: missing template: HAVE_PUBSEEKOFF > autoheader: warning: missing template: HAVE_SCALABLE_BLAS > autoheader: warning: missing template: HAVE_SEEKOFF > autoheader: warning: missing template: HAVE_SGETN > autoheader: warning: missing template: HAVE_SIDL_HEADERS > autoheader: warning: missing template: HAVE_SYSV_IPC > autoheader: warning: missing template: HAVE_TYPENAME > autoheader: warning: missing template: HOST_ARCH > autoheader: warning: missing template: INSTALLED_SCLIBDIR > autoheader: warning: missing template: REF_OPTIMIZE > autoheader: warning: missing template: SCDATADIR > autoheader: warning: missing template: SC_BUILDID > autoheader: warning: missing template: SC_MAJOR_VERSION > autoheader: warning: missing template: SC_MICRO_VERSION > autoheader: warning: missing template: SC_MINOR_VERSION > autoheader: warning: missing template: SC_MPI_THREAD_LEVEL > autoheader: warning: missing template: SC_VERSION > autoheader: warning: missing template: SEMCTL_REQUIRES_SEMUN > autoheader: warning: missing template: SIGHASELLIP > autoheader: warning: missing template: SRC_SCLIBDIR > autoheader: warning: missing template: TARGET_ARCH > autoheader: warning: missing template: USING_NAMESPACE_STD > autoheader: warning: missing template: WORDS_BIGENDIAN > autoreconf: /usr/bin/autoheader failed with exit status: 1 > [...] diff --git a/configure.in b/configure.in index ee82977e4931..5a77f343331e 100644 --- a/configure.in +++ b/configure.in @@ -9,7 +9,9 @@ AC_INIT(src/lib/util/ref/ref.h) AC_PREREQ(2.55) AC_CONFIG_HEADER(src/lib/scconfig.h) AC_CONFIG_AUX_DIR(bin) AC_CONFIG_MACRO_DIR([lib/autoconf]) + +AC_DEFINE_HEADER_TEMPLATES AC_CANONICAL_SYSTEM diff --git a/lib/autoconf/templates.m4 b/lib/autoconf/templates.m4 new file mode 100644 index ..693d54289326 --- /dev/null +++ b/lib/autoconf/templates.m4 @@ -0,0 +1,50 @@ +AC_DEFUN([AC_DEFINE_HEADER_TEMPLATES],[ +AH_TEMPLATE([ALWAYS_USE_MPI], []) +AH_TEMPLATE([CXX_RESTRICT], []) +AH_TEMPLATE([DEFAULT_ARMCI], []) +AH_TEMPLATE([DEFAULT_MPI], []) +AH_TEMPLATE([DEFAULT_MTMPI], []) +AH_TEMPLATE([DEFAULT_SC_MEMORY], []) +AH_TEMPLATE([EXPLICIT_TEMPLATE_INSTANTIATION], []) +AH_TEMPLATE([HAVE_ARMCI], []) +AH_TEMPLATE([HAVE_BACKTRACE], []) +AH_TEMPLATE([HAVE_CCA_CHEM_HEADERS], []) +AH_TEMPLATE([HAVE_CCA_SPEC_BABEL_HEADERS], []) +AH_TEMPLATE([HAVE_FCHDIR], []) +AH_TEMPLATE([HAVE_IOS_FMTFLAGS], []) +AH_TEMPLATE([HAVE_ISNAN], []) +AH_TEMPLATE([HAVE_LIBDERIV], []) +AH_TEMPLATE([HAVE_LIBINT], []) +AH_TEMPLATE([HAVE_LIBR12], []) +AH_TEMPLATE([HAVE_LONG_LONG], []) +AH_TEMPLATE([HAVE_MPI], []) +AH_TEMPLATE([HAVE_MPIIO], []) +AH_TEMPLATE([HAVE_MPIPP], []) +AH_TEMPLATE([HAVE_MPI_INIT_THREAD], []) +AH_TEMPLATE([HAVE_NIAMA], []) +AH_TEMPLATE([HAVE_PERF], []) +AH_TEMPLATE([HAVE_PTHREAD], [])
Re: [RFC] python-cobra, python3-sbml5
On Sun, 5 Apr 2020, 15:50 Andreas Tille, wrote: > On Sun, Apr 05, 2020 at 03:40:56PM +0530, Nilesh Patra wrote: > > > > '_libsbml' file which corresponds to libsbml (with python3-sbml5 as a > > > > provide) package. When I dug into looking at libsbml, I noticed that > the > > > > relevant file (libsbml.py) which throws error > > > > is generated with swig-3.0 by the upstream [3] > > > > > > I admit I'm absolutely naive about swig - but if libsbml.py is really > > > autogenerated what about re-generating it with swig-4? > > > > I think there's a miscommunication here. The file in the archive(on doing > > $apt source python3-sbml5) is generated with swig-4 already, while it's > > generated with swig-3 upstream. > > Hence the issue. > > Ahhh, so it is regenerated in the Debian package build process but it > conflicts with other parts of the upstream code? Did I now understood > correctly? > Yep. That's my _suspicion_ though, that the rest of the upstream code isn't compatible with the new version, and there are API changes needed. Hence I sent the mail to confirm if I'm thinking in the right direction. > I wonder if we should exclude this kind of autogenerated code inside > the source tarball since we are repackaging the source anyway to exclude > some files for policy reasons. I'm doing so in other source tarballs > for instance with cython files to be absolutely sure that this code > is regenerated. This would probably not solve the build issue but might > be a good idea in general. What do you think? > It seems like libsbml.py would be needed by the rest of the code. So we can maybe keep the upstream's generated code and not generate it on our own - this however does not seem DFSG compliant. Not really sure what to do here. > Kind regards > > Andreas. > > > > > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656 > > > > > > > > [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10 > > > > > > > > [3]: > https://salsa.debian.org/med-team/libsbml/-/blob/master/src/bindings/python/libsbml.py?expanded=true=simple > > -- > http://fam-tille.de >
Re: Autoconf issue in mpqc
Hi Jeremy, On Sun, Apr 05, 2020 at 10:14:58AM +0100, Jeremy Sowden wrote: > > Any help would be appreciated. > > > > [1] https://salsa.debian.org/debichem-team/mpqc > > Adding AC_CONFIG_MACRO_DIR to configure.in appears to fix it (patch > attached). Thanks a lot for the promising patch I have commited to Git[1]. Unfortunately the build does not yet succeed in a pbuilder chroot. I've attached the part or the build log that seems to be autoconf relevant. I admit I'm a bit astonished since I can only see warnings but no error ... Kind regards Andreas. -- http://fam-tille.de dh_autoreconf -O--no-parallel aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:766: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from... configure.in:766: the top level configure.in:776: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from... configure.in:776: the top level configure.in:1259: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from... configure.in:1259: the top level configure.in:766: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from... configure.in:766: the top level configure.in:776: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2601: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2617: AC_COMPILE_IFELSE is expanded from... configure.in:776: the top level configure.in:1259: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from... configure.in:1259: the top level configure.in:1761: warning: AC_CACHE_VAL(lt_prog_compiler_pic_works, ...): suspicious cache-id, must contain _cv_ to be cached ../../lib/autoconf/general.m4:2042: AC_CACHE_VAL is expanded from... ../../lib/autoconf/general.m4:2063: AC_CACHE_CHECK is expanded from... lib/autoconf/libtool.m4:664: AC_LIBTOOL_COMPILER_OPTION is expanded from... lib/autoconf/libtool.m4:4901: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from... lib/autoconf/libtool.m4:2737: _LT_AC_LANG_C_CONFIG is expanded from... lib/autoconf/libtool.m4:2736: AC_LIBTOOL_LANG_C_CONFIG is expanded from... lib/autoconf/libtool.m4:80: AC_LIBTOOL_SETUP is expanded from... lib/autoconf/libtool.m4:60: _AC_PROG_LIBTOOL is expanded from... lib/autoconf/libtool.m4:25: AC_PROG_LIBTOOL is expanded from... configure.in:1761: the top level configure.in:1761: warning: AC_CACHE_VAL(lt_prog_compiler_static_works, ...): suspicious cache-id, must contain _cv_ to be cached ../../lib/autoconf/general.m4:2042: AC_CACHE_VAL is expanded from... ../../lib/autoconf/general.m4:2063: AC_CACHE_CHECK is expanded from... lib/autoconf/libtool.m4:709: AC_LIBTOOL_LINKER_OPTION is expanded from... lib/autoconf/libtool.m4:4901: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from... lib/autoconf/libtool.m4:2737: _LT_AC_LANG_C_CONFIG is expanded from... lib/autoconf/libtool.m4:2736: AC_LIBTOOL_LANG_C_CONFIG is expanded from... lib/autoconf/libtool.m4:80: AC_LIBTOOL_SETUP is expanded from... lib/autoconf/libtool.m4:60: _AC_PROG_LIBTOOL is expanded from... lib/autoconf/libtool.m4:25: AC_PROG_LIBTOOL is expanded from... configure.in:1761: the top level configure.in:1761: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from... ../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from... lib/autoconf/libtool.m4:332: _LT_AC_SYS_LIBPATH_AIX is expanded from... lib/autoconf/libtool.m4:5428: AC_LIBTOOL_PROG_LD_SHLIBS is expanded from... lib/autoconf/libtool.m4:2737: _LT_AC_LANG_C_CONFIG is expanded from... lib/autoconf/libtool.m4:2736: AC_LIBTOOL_LANG_C_CONFIG is expanded from... lib/autoconf/libtool.m4:80: AC_LIBTOOL_SETUP is expanded from... lib/autoconf/libtool.m4:60:
Re: [RFC] python-cobra, python3-sbml5
Hi On Sun, 5 Apr 2020, 11:43 Andreas Tille, wrote: > Hi Nilesh, > > On Sat, Apr 04, 2020 at 06:53:55PM +0530, Nilesh Patra wrote: > > > > >From the logs, in the last message[2] it looks like an import-error for > > '_libsbml' file which corresponds to libsbml (with python3-sbml5 as a > > provide) package. When I dug into looking at libsbml, I noticed that the > > relevant file (libsbml.py) which throws error > > is generated with swig-3.0 by the upstream [3] > > I admit I'm absolutely naive about swig - but if libsbml.py is really > autogenerated what about re-generating it with swig-4? > I think there's a miscommunication here. The file in the archive(on doing $apt source python3-sbml5) is generated with swig-4 already, while it's generated with swig-3 upstream. Hence the issue. > > > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656 > > > > [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10 > > > > [3]: > > > https://salsa.debian.org/med-team/libsbml/-/blob/master/src/bindings/python/libsbml.py?expanded=true=simple > > > > Thanks and regards > > Nilesh > > -- > http://fam-tille.de >
Re: Sponsor for DMX - The Context Machine
On Sun, Apr 05, 2020 at 12:16:16PM +0200, Fabrice BAUZAC-STEHLY wrote: > Andrey Rahmatullin writes: > > > On Sat, Apr 04, 2020 at 11:36:03PM +0200, Fabrice BAUZAC-STEHLY wrote: > >> - By building the upstream source (main)? By packaging the upstream > >> binary (contrib)? > > > Pre-built binaries are for non-free, not for contrib. Contrib is strictly > > DFSG-free. > > Here the binaries seem to be free software (AGPL3 or GPL3). Are you sure? Then what would stop them from being included in main if that was the only requirement? There is only one difference between main and contrib: "packages in main must not require or recommend a package outside of main for compilation or execution". Do you know about some rebuildability requirements being true only for main but not for contrib? -- WBR, wRAR signature.asc Description: PGP signature
Re: [RFC] python-cobra, python3-sbml5
On Sun, Apr 05, 2020 at 03:40:56PM +0530, Nilesh Patra wrote: > > > '_libsbml' file which corresponds to libsbml (with python3-sbml5 as a > > > provide) package. When I dug into looking at libsbml, I noticed that the > > > relevant file (libsbml.py) which throws error > > > is generated with swig-3.0 by the upstream [3] > > > > I admit I'm absolutely naive about swig - but if libsbml.py is really > > autogenerated what about re-generating it with swig-4? > > I think there's a miscommunication here. The file in the archive(on doing > $apt source python3-sbml5) is generated with swig-4 already, while it's > generated with swig-3 upstream. > Hence the issue. Ahhh, so it is regenerated in the Debian package build process but it conflicts with other parts of the upstream code? Did I now understood correctly? I wonder if we should exclude this kind of autogenerated code inside the source tarball since we are repackaging the source anyway to exclude some files for policy reasons. I'm doing so in other source tarballs for instance with cython files to be absolutely sure that this code is regenerated. This would probably not solve the build issue but might be a good idea in general. What do you think? Kind regards Andreas. > > > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656 > > > > > > [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10 > > > > > > [3]: > > > https://salsa.debian.org/med-team/libsbml/-/blob/master/src/bindings/python/libsbml.py?expanded=true=simple -- http://fam-tille.de
Re: Sponsor for DMX - The Context Machine
Andrey Rahmatullin writes: > On Sat, Apr 04, 2020 at 11:36:03PM +0200, Fabrice BAUZAC-STEHLY wrote: >> - By building the upstream source (main)? By packaging the upstream >> binary (contrib)? > Pre-built binaries are for non-free, not for contrib. Contrib is strictly > DFSG-free. Here the binaries seem to be free software (AGPL3 or GPL3). Are you sure? -- Fabrice BAUZAC-STEHLY PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D
Re: Autoconf issue in mpqc
On 2020-04-05, at 08:18:30 +0200, Andreas Tille wrote: > while Nilesh has fixed the MPI-3.0 issue of mpqc in Git[1] the package > does not build any more due to an autoconf issue: > > ... > configure.in:1802: error: possibly undefined macro: AC_CHECK_CCA > If this token and others are legitimate, please use > m4_pattern_allow. > See the Autoconf documentation. > configure.in:1833: error: possibly undefined macro: AC_DEFINE_DIR > autoreconf: /usr/bin/autoconf failed with exit status: 1 > ... > > The macro AC_CHECK_CCA is defined in > >lib/autoconf/cca.m4 > > but it seems it is not found any more by recent autotools. > > Any help would be appreciated. > > Kind regards > > Andreas. > > [1] https://salsa.debian.org/debichem-team/mpqc Adding AC_CONFIG_MACRO_DIR to configure.in appears to fix it (patch attached). J. diff --git a/configure.in b/configure.in index ee82977e4931..d615d3854a6c 100644 --- a/configure.in +++ b/configure.in @@ -9,6 +9,7 @@ AC_INIT(src/lib/util/ref/ref.h) AC_PREREQ(2.55) AC_CONFIG_HEADER(src/lib/scconfig.h) AC_CONFIG_AUX_DIR(bin) +AC_CONFIG_MACRO_DIR([lib/autoconf]) AC_CANONICAL_SYSTEM signature.asc Description: PGP signature
Bug#955808: RFS: kxd/0.14-1.1 [NMU, RC] -- Key exchange daemon
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "kxd" * Package name: kxd Version : 0.14-1.1 Upstream Author : * URL : https://blitiri.com.ar/p/kxd * License : Expat * Vcs : https://salsa.debian.org/debian/kxd Section : net It builds those binary packages: kxc - Key exchange daemon -- client kxd - Key exchange daemon To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kxd Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kxd/kxd_0.14-1.1.dsc Changes since the last upload: * Non-maintainer upload. * Set absolute path in d/rules closes: #952332 * Cherry-pick upstream commit, needed for upstream testsuite. 0001-tests-Add-missing-conn.getresponse-which-was-causing.patch Regards, Håvard
Re: [RFC] python-cobra, python3-sbml5
Hi Nilesh, On Sat, Apr 04, 2020 at 06:53:55PM +0530, Nilesh Patra wrote: > > >From the logs, in the last message[2] it looks like an import-error for > '_libsbml' file which corresponds to libsbml (with python3-sbml5 as a > provide) package. When I dug into looking at libsbml, I noticed that the > relevant file (libsbml.py) which throws error > is generated with swig-3.0 by the upstream [3] I admit I'm absolutely naive about swig - but if libsbml.py is really autogenerated what about re-generating it with swig-4? Kind regards Andreas. > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656 > > [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955656#10 > > [3]: > https://salsa.debian.org/med-team/libsbml/-/blob/master/src/bindings/python/libsbml.py?expanded=true=simple > > Thanks and regards > Nilesh -- http://fam-tille.de
Autoconf issue in mpqc
Control: tags -1 help Hi, while Nilesh has fixed the MPI-3.0 issue of mpqc in Git[1] the package does not build any more due to an autoconf issue: ... configure.in:1802: error: possibly undefined macro: AC_CHECK_CCA If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.in:1833: error: possibly undefined macro: AC_DEFINE_DIR autoreconf: /usr/bin/autoconf failed with exit status: 1 ... The macro AC_CHECK_CCA is defined in lib/autoconf/cca.m4 but it seems it is not found any more by recent autotools. Any help would be appreciated. Kind regards Andreas. [1] https://salsa.debian.org/debichem-team/mpqc -- http://fam-tille.de
