Your message dated Sun, 14 Jun 2020 13:15:58 +0100
with message-id
<cadvatmpjhudoys5wwww8vv18-ewj_hwd__c2djm66a4aez4...@mail.gmail.com>
and subject line Re: Bug#948074: din FTBFS: cannot find X11/X.h
has caused the Debian Bug report #948074,
regarding din FTBFS: cannot find X11/X.h
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.)
--
948074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: din
Version: 5.2.1-6
Severity: serious
Tags: ftbfs
din fails to build from source in unstable on amd64. A build log ends
with:
| dh_auto_build
| make -j1
| make[2]: Entering directory '/<<PKGBUILDDIR>>'
| Making all in include
| make[3]: Entering directory '/<<PKGBUILDDIR>>/include'
| make[3]: Nothing to be done for 'all'.
| make[3]: Leaving directory '/<<PKGBUILDDIR>>/include'
| Making all in src
| make[3]: Entering directory '/<<PKGBUILDDIR>>/src'
| g++ -DPACKAGE_NAME=\"din\" -DPACKAGE_TARNAME=\"din\"
-DPACKAGE_VERSION=\"5.2.1\" -DPACKAGE_STRING=\"din\ 5.2.1\"
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"din\"
-DVERSION=\"5.2.1\" -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_GL_GL_H=1
-DHAVE_TCL8_6_TCL_H=1 -DHAVE_LIBIRCCLIENT_H=1 -I. -Wdate-time
-D_FORTIFY_SOURCE=2 -I /usr/include -I /usr/local/include -I /opt/include
-I/usr/include/tcl8.6 -I/usr/local/include/tcl8.6 -I /opt/include/tcl8.6 -I
../include -Wall -O3 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -Wformat -Werror=format-security -c -o main.o main.cc
| main.cc:22:9: fatal error: X11/X.h: No such file or directory
| 22 | #include<X11/X.h>
| | ^~~~~~~~~
| compilation terminated.
| make[3]: *** [Makefile:517: main.o] Error 1
| make[3]: Leaving directory '/<<PKGBUILDDIR>>/src'
| make[2]: *** [Makefile:350: all-recursive] Error 1
| make[2]: Leaving directory '/<<PKGBUILDDIR>>'
| dh_auto_build: make -j1 returned exit code 2
| make[1]: *** [debian/rules:12: override_dh_auto_build] Error 255
| make[1]: Leaving directory '/<<PKGBUILDDIR>>'
| make: *** [debian/rules:4: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
--- End Message ---
--- Begin Message ---
On Sun, Jun 14, 2020 at 12:29 AM Mattia Rizzolo <mat...@mapreri.org> wrote:
>
> I know that at the start of the year some reorganization within the X11
> packages caused down FTBFS while files where being moving around.
>
> I recommend you just close this bug. FTR, it also builds in
> reproducible-builds testing.
Thanks Mattia.
Closing now.
--
Regards
Sudip
--- End Message ---
