Your message dated Wed, 13 Mar 2024 16:41:25 +0300
with message-id 
<CAOq2pXF0BKRv+Zmg=on4pa9q5mg91-0j87uo0+gt+xtnbjr...@mail.gmail.com>
and subject line Re: Bug#1066333: tcltrf: FTBFS: ./generic/crypt.c:96:35: 
error: implicit declaration of function ‘crypt’ 
[-Werror=implicit-function-declaration]
has caused the Debian Bug report #1066333,
regarding tcltrf: FTBFS: ./generic/crypt.c:96:35: error: implicit declaration 
of function ‘crypt’ [-Werror=implicit-function-declaration]
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 [email protected]
immediately.)


-- 
1066333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066333
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: tcltrf
Version: 2.1.4-dfsg3-2.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

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

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"Trf\" -DPACKAGE_TARNAME=\"trf\" 
> -DPACKAGE_VERSION=\"2.1.4\" -DPACKAGE_STRING=\"Trf\ 2.1.4\" 
> -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DSIZEOF_INT=4 -DSIZEOF_LONG_INT=8 
> -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 
> -DMODULE_SCOPE=extern\ __attribute__\(\(__visibility__\(\"hidden\"\)\)\) 
> -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_IS_LONG=1 -DUSE_TCL_STUBS=1 
> -DUSE_ZLIBTCL_STUBS=1 -DHAVE_ZLIB_H=1 -DHAVE_SSL_H=1 -DHAVE_MD2_H=1 
> -DHAVE_MD5_H=1 -DHAVE_SHA_H=1 -DHAVE_BZ2_H=1 -DZLIB_STATIC_BUILD=1 
> -DBZLIB_STATIC_BUILD=1 -DMD5_STATIC_BUILD=1 -DHAVE_DLFCN_H=1 
> -DHAVE_STDLIB_H=1 -DHAVE_FEATURES_H=1 -DMD5_STATIC_BUILD=1 
> -DZLIBTCL_VERSION=\"\" -I"." -I"./generic" -I"" -I"" -I"/usr/include" 
> -I"/usr/include/openssl" -DLIBZ_DEFAULTNAME=\"libz.so\" -I"/usr/include/tcl"  
>   -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -DSSL_STATIC_BUILD=1 -D_XOPEN_SOURCE -pipe -O2 -fomit-frame-pointer -Wall 
> -Wno-implicit-int -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c `echo 
> ./generic/crypt.c` -o crypt.o
> ./generic/crypt.c: In function ‘TrfCryptObjCmd’:
> ./generic/crypt.c:96:35: error: implicit declaration of function ‘crypt’ 
> [-Werror=implicit-function-declaration]
>    96 |   res = Tcl_NewStringObj ((char*) crypt (passwd, salt_b), -1);
>       |                                   ^~~~~
> ./generic/crypt.c:96:27: warning: cast to pointer from integer of different 
> size [-Wint-to-pointer-cast]
>    96 |   res = Tcl_NewStringObj ((char*) crypt (passwd, salt_b), -1);
>       |                           ^
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:260: crypt.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/tcltrf_2.1.4-dfsg3-2.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&[email protected]&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 mark 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 ---
fixed 1066333 2.1.4-dfsg3-3
thanks

Hi Lucas,

The bug is already fixed in tcltrf 2.1.4-dfsg3-3.

On Wed, Mar 13, 2024 at 2:57 PM Lucas Nussbaum <[email protected]> wrote:
>
> Source: tcltrf
> Version: 2.1.4-dfsg3-2.1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: [email protected]
> Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> This is most likely caused by a change in dpkg 1.22.6, that enabled
> -Werror=implicit-function-declaration. For more information, see
> https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration
>
> Relevant part (hopefully):
> > gcc -DPACKAGE_NAME=\"Trf\" -DPACKAGE_TARNAME=\"trf\" 
> > -DPACKAGE_VERSION=\"2.1.4\" -DPACKAGE_STRING=\"Trf\ 2.1.4\" 
> > -DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
> > -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
> > -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> > -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DSIZEOF_INT=4 -DSIZEOF_LONG_INT=8 
> > -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 
> > -DMODULE_SCOPE=extern\ __attribute__\(\(__visibility__\(\"hidden\"\)\)\) 
> > -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_IS_LONG=1 -DUSE_TCL_STUBS=1 
> > -DUSE_ZLIBTCL_STUBS=1 -DHAVE_ZLIB_H=1 -DHAVE_SSL_H=1 -DHAVE_MD2_H=1 
> > -DHAVE_MD5_H=1 -DHAVE_SHA_H=1 -DHAVE_BZ2_H=1 -DZLIB_STATIC_BUILD=1 
> > -DBZLIB_STATIC_BUILD=1 -DMD5_STATIC_BUILD=1 -DHAVE_DLFCN_H=1 
> > -DHAVE_STDLIB_H=1 -DHAVE_FEATURES_H=1 -DMD5_STATIC_BUILD=1 
> > -DZLIBTCL_VERSION=\"\" -I"." -I"./generic" -I"" -I"" -I"/usr/include" 
> > -I"/usr/include/openssl" -DLIBZ_DEFAULTNAME=\"libz.so\" 
> > -I"/usr/include/tcl"    -g -O2 -Werror=implicit-function-declaration 
> > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> > -DSSL_STATIC_BUILD=1 -D_XOPEN_SOURCE -pipe -O2 -fomit-frame-pointer -Wall 
> > -Wno-implicit-int -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -c `echo 
> > ./generic/crypt.c` -o crypt.o
> > ./generic/crypt.c: In function ‘TrfCryptObjCmd’:
> > ./generic/crypt.c:96:35: error: implicit declaration of function ‘crypt’ 
> > [-Werror=implicit-function-declaration]
> >    96 |   res = Tcl_NewStringObj ((char*) crypt (passwd, salt_b), -1);
> >       |                                   ^~~~~
> > ./generic/crypt.c:96:27: warning: cast to pointer from integer of different 
> > size [-Wint-to-pointer-cast]
> >    96 |   res = Tcl_NewStringObj ((char*) crypt (passwd, salt_b), -1);
> >       |                           ^
> > cc1: some warnings being treated as errors
> > make[2]: *** [Makefile:260: crypt.o] Error 1
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2024/03/13/tcltrf_2.1.4-dfsg3-2.1_unstable.log
>
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;[email protected]
> or:
> https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&[email protected]&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 mark 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.



-- 
Sergei Golovan

--- End Message ---

Reply via email to