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

Bug#1017311: marked as done (zfs-fuse: FTBFS: malloc.c:447:13: error: '__malloc_hook' undeclared (first use in this function); did you mean 'umem_malloc_hook'?)

Your message dated Thu, 22 Sep 2022 00:48:04 +0000
with message-id <E1obANo-00AUdC-Up@fasolo.debian.org>
and subject line Bug#1017311: fixed in zfs-fuse 0.7.0-23
has caused the Debian Bug report #1017311,
regarding zfs-fuse: FTBFS: malloc.c:447:13: error: '__malloc_hook' undeclared (first use in this function); did you mean 'umem_malloc_hook'?
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.)


-- 
1017311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017311
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: zfs-fuse
Version: 0.7.0-22
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  gcc -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT malloc.lo -MD -MP -MF .deps/malloc.Tpo -c malloc.c  -fPIC -DPIC -o .libs/malloc.o
> malloc.c: In function 'umem_malloc_init_hook':
> malloc.c:447:13: error: '__malloc_hook' undeclared (first use in this function); did you mean 'umem_malloc_hook'?
>   447 |         if (__malloc_hook != umem_malloc_hook) {
>       |             ^~~~~~~~~~~~~
>       |             umem_malloc_hook
> malloc.c:447:13: note: each undeclared identifier is reported only once for each function it appears in
> malloc.c:448:17: warning: implicit declaration of function 'umem_startup' [-Wimplicit-function-declaration]
>   448 |                 umem_startup(NULL, 0, 0, NULL, NULL);
>       |                 ^~~~~~~~~~~~
> malloc.c:450:17: error: '__free_hook' undeclared (first use in this function); did you mean 'umem_free_hook'?
>   450 |                 __free_hook = umem_free_hook;
>       |                 ^~~~~~~~~~~
>       |                 umem_free_hook
> malloc.c:451:17: error: '__realloc_hook' undeclared (first use in this function); did you mean 'umem_realloc_hook'?
>   451 |                 __realloc_hook = umem_realloc_hook;
>       |                 ^~~~~~~~~~~~~~
>       |                 umem_realloc_hook
> malloc.c:452:17: error: '__memalign_hook' undeclared (first use in this function); did you mean 'umem_memalign_hook'?
>   452 |                 __memalign_hook = umem_memalign_hook;
>       |                 ^~~~~~~~~~~~~~~
>       |                 umem_memalign_hook
> make[1]: *** [Makefile:375: malloc.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/zfs-fuse_0.7.0-22_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message --- 
Source: zfs-fuse
Source-Version: 0.7.0-23
Done: Hilko Bengen <bengen@debian.org>

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

Debian distribution maintenance software
pp.
Hilko Bengen <bengen@debian.org> (supplier of updated zfs-fuse 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: SHA256

Format: 1.8
Date: Thu, 22 Sep 2022 01:32:45 +0200
Source: zfs-fuse
Architecture: source
Version: 0.7.0-23
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Hilko Bengen <bengen@debian.org>
Closes: 1017162 1017311
Changes:
 zfs-fuse (0.7.0-23) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Hilko Bengen ]
   * Add patch to FTBFS with glibc >= 2..34 (Closes: #1017162, #1017311)
Checksums-Sha1:
 891e69cff599c98b64e45ef28d49c3d7bc16039c 2054 zfs-fuse_0.7.0-23.dsc
 4f123e4f7ed599626940c3120981243c5071ee4c 29052 zfs-fuse_0.7.0-23.debian.tar.xz
 24040e8e649afd3b19d99753ad2ec7e8b94a1593 7685 zfs-fuse_0.7.0-23_source.buildinfo
Checksums-Sha256:
 80fa78c727514d332f0527b5be857288f498012f5f9691648108e620ad1628d4 2054 zfs-fuse_0.7.0-23.dsc
 6fee97ae09607d348ee1f4a252c9e256e1ca1250c69974f09426579b800ed5a6 29052 zfs-fuse_0.7.0-23.debian.tar.xz
 2f3b7a4b9a22269492a9c091550132372b7e95c3f868a03f189a435e5b4bfec7 7685 zfs-fuse_0.7.0-23_source.buildinfo
Files:
 c53fb15d7d7fc96ead60ca3e70d8d498 2054 otherosfs optional zfs-fuse_0.7.0-23.dsc
 9341cf1940f3c67f52b6e79a653c6026 29052 otherosfs optional zfs-fuse_0.7.0-23.debian.tar.xz
 927d25a66365f57b6f35128b94fb88e3 7685 otherosfs optional zfs-fuse_0.7.0-23_source.buildinfo

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

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmMrn34ACgkQdbcQY1wh
On6byg/9E6BKsJFTDszWo8J+j+PtjiBi86qsTs2LzBlPuPn29fBueLOC+ih6m+Pf
ZRzj9YRuYKuR7OOHskkeP75wYlLUUWiSeUDKLatMtKNXSA6b2GEaJdcciDcmvQA0
RlYozDQkBT7qq1KXOLWViGoXlvTRCn52lhwfZ2FBTKDxpF63q0PsHyAyNEQdO5rS
G1ssLnhXjinuY86qOUIQ4vAD2clkwSZGQJiMLH+G//cBjkMx9e+LaYy7wYOEGRSV
4pl0wy2z60+YkY2iYcHzmrMRCSbmERioLFXnnnnK5tMn9IVrNKDUHdsRpken0Jhj
SeE6fiYe0pYLu1g7Sf/SGqytXbDG4xSYn0tFVo10ZZ28WSNOK0hhL8rIqa8Me3ko
+Rda7Oiaj7jW0WvTK3hSYhiVY3Jq5sDw1JY/+ad7p95NvIRZEECuLw2HG/XqkOcG
3XhpLq0ICCDRXQ+JNTBU7kSr0ZDJmH1xPGH+r6WNgYuuJreGHyPUAbrVBVZhkFQh
knV9UPrH9fI3BeXmOKnYbvGnzpROQZ8INSf2s8QMt47Z5doPkLmcEw1ZBG2WGrpJ
Tqnr4/LwZN0bk7Y0PUA+mcjf4X+lbNqQueGrbU0VkuXxJJGbxQSPIx7caD8RuY2q
IAbHzLFNgIyJmIpXDREBQgdtQrfjpQWe3XLp6pyDQWQbXUebHiI=
=hBXK
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: