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

Re: Cuba multidimensional integration



On 2019-03-29 21:58, Francesco Montanari wrote:
Hi,

Following #886254 (submitted a while ago), I'm working on packaging
the Cuba library for multidimensional integration.

I'm stuck since a while so I'd like to ask for help. The package lives
here: <https://gitlab.com/montanari/cuba-4.2/>.
...
I get an error only when installing libcuba4-dbgsym_4.2-1_amd64.deb:

  Unpacking libcuba4-dbgsym:amd64 (4.2-1) ...
dpkg: error processing archive libcuba4-dbgsym_4.2-1_amd64.deb (--install):
   trying to overwrite
'/usr/lib/debug/.build-id/c8/ac72a8619c9fdea68e3b66e9d24249a31b503c.debug',
which is also in package libcuba4-dbg:amd64 4.2-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

However, if I ran directly dpkg-buildpackage the build fails because
of undefined references. I report below lintian output (nothing
related to symbols etc., though) and the failed debuild log.

Any suggestion about what's going wrong?



From your build log, I'd say the thing to look into is the memory warning when compiling partview.o:

In file included from /usr/include/string.h:494,
                 from ./src/common/stddecl.h:20,
                 from ./src/divonne/decl.h:9,
                 from ./src/divonne/Divonne.c:13:
In function ‘memcpy’,
    inlined from ‘SobolIni’ at ./src/common/Random.c:105:5,
    inlined from ‘IniRandom’ at ./src/common/Random.c:340:22,
    inlined from ‘Integrate’ at ./src/divonne/Integrate.c:74:5:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34:10: warning: ‘__builtin_memcpy’ specified size 18446744073709551608 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=] return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest));
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


ld then complains partview.o is malformed. I guess the oversized memcpy means it never compiled to a useful object file. Why is the code requesting an oversized memcpy?


Your dbgsym error indicated the debug files got placed in the main lib package, not just the dbgsym package.


Reply to: