On Wed, Jan 15, 2025 at 07:21:02PM +, Debian Bug Tracking System wrote:
>...
> Version: 14.2.0-14
>
> On 15.01.25 19:31, Andrey Rakhmatullin wrote:
> > Package: libn32gcc-14-dev
> > Version: 14.2.0-13
> >
> > Unless I'm very confused, libn32gcc-14-dev is not installable on mips64el
> > and th
Package: gcc-14
Version: 14.2.0-5
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-sp...@lists.debian.org
sparc64 has some spurious library dependencies due to gcc-as-needed.diff
currently only adding --as-needed to 32bit-only sparc builds, please
append the attached patch to gcc-as-needed.diff
Package: gcc-13
Severity: normal
Tags: patch
X-Debbugs-Cc: debian-sp...@lists.debian.org
sparc64 has some spurios library dependencies due to gcc-as-needed.diff
currently only adding --as-needed to 32bit-only sparc builds, please
append the attached patch to gcc-as-needed.diff
Thanks in advance
-
On Tue, Jan 23, 2024 at 09:08:00AM +0100, Matthias Klose wrote:
> Package: src:gcc-14
> Version: 14-20240121-1
> Severity: important
> Tags: sid trixie ftbfs
> X-Debbugs-CC: debian-loonga...@lists.debian.org
>
> gcc-14 ftbfs on loong64:
>...
The remaining build failure is now:
https://buildd.deb
On Sun, Jan 29, 2023 at 12:41:48AM +0100, Axel Beckert wrote:
> # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029633#10
> tags 1029641 + moreinfo
> thanks
What info is missing here for also covering the packages that are not
already covered by built-using-field-on-arch-all-package because
Control: tags -1 ftbfs
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10
Control: reassign -2 src:gcc-10-cross
Control: retitle -2 gcc-10-cross: source and binary version go out of sync
Control: reassign -3 src:gcc-10-cross-ports
Control: retitle -3 gcc-10-cross-ports: source and binary version go out
Source: gcc-12-cross-mipsen
Version: 2+c1
Severity: serious
X-Debbugs-Cc: YunQiang Su
gcc-*-cross* packages in general have an (IMHO RC severity) problem
that binNMUs are not possible since binary-any packages being
newer than binary-all packages might cause problems.
This is also the case right
xinfo.
+(Closes: #997145)
+
+ -- Adrian Bunk Sat, 19 Nov 2022 21:40:11 +0200
+
autoconf2.69 (2.69-3) unstable; urgency=medium
* Don't apply the add-runstatedir backport, not needed in the context
diff -Nru autoconf2.69-2.69/debian/patches/0001-doc-port-to-Texinfo-6.3.patch autoconf2.69-2
Source: gcc-12
Version: 12.2.0-9
Severity: important
Control: block 1023690 by -1
gcc-12 build depends on gcc-11 that should not be in bookworm.
Package: gcc-11
Version: 11.3.0-8
Severity: important
gcc-11 should not be shipped in bookworm.
Package: gcc-10
Version: 10.4.0-5
Severity: serious
gcc-10 should not be shipped in bookworm.
ebian/changelog 2021-10-07 15:13:26.0 +0300
+++ autofdo-0.19/debian/changelog 2022-09-13 23:41:57.0 +0300
@@ -1,3 +1,10 @@
+autofdo (0.19-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Build with LLVM 13. (Closes: #1016238)
+
+ -- Adrian Bunk Tue, 13 Sep 2022 23:41:57
On Wed, Mar 09, 2022 at 05:49:04PM +0800, YunQiang Su wrote:
> On Tue, 08 Mar 2022 20:53:46 +0100 Paul Gevers wrote:
> > Source: gcc-12
> > Version: 12-20220222-1
> > Severity: serious
> > Tags: ftbfs
> >
> > Dear Matthias, GCC maintainers,
> >
> > gcc-12 fails to build from source on mips64el i
build dependencies on armel/armhf.
+(Closes: #1000892)
+ * Recommend colordiff. (Closes: #1001375)
+
+ -- Adrian Bunk Wed, 29 Dec 2021 22:41:49 +0200
+
cvise (2.4.0-2) unstable; urgency=medium
* (Build-)depend on python3-chardet.
diff -Nru cvise-2.4.0/debian/control cvise-2.4.0/debian/co
Source: cvise
Version: 2.4.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=cvise&ver=2.4.0-1
...
=== FAILURES ===
___ TestCvise.test_simple_reduction
self
loses: #974802)
+ * Backport upstream fix for FTBFS with LLVM 11.
+ * Use the system libprotobuf. (Closes: #960822)
+ * Remove vendored copies in dh_auto_clean,
+fixes building twice in a row.
+
+ -- Adrian Bunk Thu, 07 Oct 2021 15:13:26 +0300
+
autofdo (0.19-2) unstable; urgency=m
Source: gcc-10
Version: 10.3.0-8
Severity: serious
Your upload included the binary package lib32atomic1, version 10.3.0-8, for
mips64el,
however unstable already has version 11.2.0-3+b1.
On Wed, Jul 14, 2021 at 09:18:45AM +0200, Matthias Klose wrote:
> On 7/13/21 9:52 PM, Adrian Bunk wrote:
> > On Tue, Jul 13, 2021 at 04:51:40PM +0200, Matthias Klose wrote:
> >> No, 2.36 is not required. Perfectly fine to build with 2.35.2.
> >
> > That's corr
On Tue, Jul 13, 2021 at 04:51:40PM +0200, Matthias Klose wrote:
> No, 2.36 is not required. Perfectly fine to build with 2.35.2.
That's correct.
But if you build with 2.36, what does the runtime dependency say?
Forcing binutils (>= 2.36) for both would be the easiest way
to avoid this situation.
Source: gcc-11
Severity: serious
Helmut Grohne reported on IRC:
when gcc-11 is built with experimental binutils, the binary packages
do not work with unstable binutils by passing unrecognized options
http://gcc.gnu.org/gcc-11/changes.html confirms that gcc 11
might optionally use binutils 2.36
Source: gcc-9-cross
Version: 25
Severity: serious
Tags: ftbfs
Control: clone -1 -2 -3 -4
Control: reassign -2 gcc-9-cross-ports 23
Control: retitle -2 gcc-9-cross-ports: Incorrect Source: version generated for
binary packages in binNMUs
Control: reassign -3 gcc-10-cross 15
Control: retitle -3 gcc-
Source: gcc-defaults
Version: 1.192
Severity: normal
Looking at pygccjit, a libgccjit-dev package depending on
the corresponding package from the default gcc would be nice.
Control: severity -1 grave
On Tue, Oct 27, 2020 at 12:44:44PM +0100, Matthias Klose wrote:
> Control: severity -1 important
>
> On 10/26/20 1:04 PM, Adrian Bunk wrote:
> > Package: libgcc-s1
> > Version: 10.2.0-15
> > Severity: grave
> >
> > On a bus
Package: libgcc-s1
Version: 10.2.0-15
Severity: grave
On a buster system, with unstable pinned to low priority:
# apt-get install libgcc-s1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
gcc-10-base
T
On Tue, Jul 28, 2020 at 12:41:42PM +0200, Matthias Klose wrote:
>...
> Suggested ways to solve these issues:
>
> - Use plain shlibs files, without using symbols files, although
>debhelper wrongly warns about missing symbols files.
Usually this is the better option for C++ libraries,
for more
On Wed, Jul 22, 2020 at 05:42:35PM +0200, Matthias Klose wrote:
> Control: tags -1 + moreinfo
>
> On 7/22/20 12:59 PM, Adrian Bunk wrote:
> > Package: gdc-10
> > Version: 10.1.0-6
> > Severity: important
> > Tags: ftbfs
> > Control: affects -1 src:gtk-d
&g
Package: gdc-10
Version: 10.1.0-6
Severity: important
Tags: ftbfs
Control: affects -1 src:gtk-d
https://buildd.debian.org/status/package.php?p=gtk-d&suite=sid
...
during RTL pass: expand
/usr/lib/gcc/arm-linux-gnueabihf/10/include/d/std/algorithm/mutation.d: In
function ‘gtkd_container_remove’:
Control: reassign -1 binutils 2.34.90.20200706-1
Control: reassign 965372 binutils 2.34.90.20200706-1
Control: forcemerge -1 965372
Control: retitle -1 FTBFS: DWARF version 0 unhandled
Control: affects -1 dwz src:caml-crush src:ocaml-mccs src:ocamlnet src:extlib
On Mon, Jul 20, 2020 at 08:57:07PM
Source: autofdo
Version: 0.19-2
Severity: important
Tags: patch
autofdo should use the system libprotobuf instead of
an own copy.
debdiff attached.
diff -Nru autofdo-0.19/debian/control autofdo-0.19/debian/control
--- autofdo-0.19/debian/control 2019-10-27 21:52:39.0 +0200
+++ autofdo-0.1
Control: reassign -1 iraf-dev 2.16.1+2018.11.01-3
Control: retitle -1 iraf-dev must drop the c-compiler alternative in the
dependency
Control: affects -1 src:gcc-9
On Sun, May 10, 2020 at 07:00:02PM +0200, Paul Gevers wrote:
>...
> /usr/lib/iraf/unix/hlib/f77.sh: 208: gcc: not found
>...
This is
On Sun, May 10, 2020 at 08:56:50PM +0200, Andreas Tille wrote:
>...
> On Sun, May 10, 2020 at 11:19:27AM +0300, Adrian Bunk wrote:
> > What does fix the problem is disabling OpenMP.
> > I suspect OpenMP is somehow broken in gcc >= 8 on mipsel.
>
> I wonder how we could
Source: flang
Version: 20190329-4
Severity: serious
Tags: ftbfs
...
dh_dwz -O--buildsystem=cmake
-O--builddirectory=/tmp/flang-20190329/debian/build
install -d debian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu
dwz -mdebian/flang-7/usr/lib/debug/.dwz/x86_64-linux-gnu/flang-7.de
Control: reopen -1
Control: tags -1 buster sid
The following breaks are needed to handle the moved symbols from the
pr64735 fix in gcc-6 in stretch->buster upgrades on armel:
dnsdist (<< 1.3.3-3)
lambda-align (<< 1.0.3-5)
libllvm3.8
libllvm3.9
libllvm4.0
mednafen (<< 1.22.1+dfsg-1)
nghttp2-proxy
Control: reassign -1 gcc-8 8.2.0-11
Control: retitle -1 gcc fails to compile Eigen code
Control: affects -1 libeigen3-dev
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87531
On Sat, Dec 08, 2018 at 12:50:53AM +0100, Johannes 'josch' Schauer wrote:
> Package: libeigen3-dev
> Ve
Control: forwaded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28314
On Mon, Nov 26, 2018 at 12:28:28PM +, Dimitri John Ledkov wrote:
> xnox@diamond:~$ g++ -std=c++14 -dM -E -x c++ - < /dev/null | grep linux
> #define __linux__ 1
> #define __gnu_linux__ 1
>
> xnox@diamond:~$ g++ -std=gnu++
Control: reassign -1 gcc-8
Control: affects -1 src:theseus
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86835
On Fri, May 04, 2018 at 12:23:55PM +, Matthias Klose wrote:
>...
> /usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops
> -fomit-frame-pointer -Wall -We
Control: reopen -1
On Tue, Jan 30, 2018 at 09:24:09AM +, Debian Bug Tracking System wrote:
>...
> mpfr4 (4.0.0-6) unstable; urgency=medium
>...
>* libmpfr6: Break libmpc3 (<< 1.1.0-1~). Closes: #888422.
>...
Looking at #888911 and the fact that this FTBFS on armhf disappeared
after ever
Package: gcc-7
Version: 7.3.0-1
Severity: serious
Control: affects -1 src:pcre3
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pcre3.html
Successful build in buster:
...
--- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-8_amd64)
+++ dpkg-gensymbolsy1tQ9U 2018-01-31
Control: severity -1 serious
On Thu, Jan 25, 2018 at 09:53:21PM +0200, Adrian Bunk wrote:
> Control: tags -1 - moreinfo
>
> On Thu, Jan 25, 2018 at 07:39:27PM +0100, Julien Cristau wrote:
> > Control: severity -1 normal
> > Control: tag -1 moreinfo
> >
> > On Th
On Thu, Jan 25, 2018 at 11:53:46PM +0100, Vincent Lefevre wrote:
> On 2018-01-25 20:32:45 +0200, Adrian Bunk wrote:
> > On Thu, Jan 25, 2018 at 02:15:15PM +0100, Vincent Lefevre wrote:
> > > On 2018-01-25 14:11:49 +0200, Adrian Bunk wrote:
> > > > Mixing libmpfr4
Control: tags -1 - moreinfo
On Thu, Jan 25, 2018 at 07:39:27PM +0100, Julien Cristau wrote:
> Control: severity -1 normal
> Control: tag -1 moreinfo
>
> On Thu, Jan 25, 2018 at 14:11:49 +0200, Adrian Bunk wrote:
>
> > Package: libmpfr6
> > Version: 4.0.0-5
> >
On Thu, Jan 25, 2018 at 02:15:15PM +0100, Vincent Lefevre wrote:
> On 2018-01-25 14:11:49 +0200, Adrian Bunk wrote:
> > Mixing libmpfr4 and libmpfr6 doesn't work well:
>
> Wasn't symbol versioning supposed to solve this issue?
Yes, versioning all symbols could sol
Package: libmpfr6
Version: 4.0.0-5
Severity: serious
Mixing libmpfr4 and libmpfr6 doesn't work well:
flint-arb FTBFS with:
/usr/bin/ld: warning: libmpfr.so.4, needed by /usr/lib/libflint.so, may
conflict with libmpfr.so.6
/usr/bin/ld: mpfr_free_func: TLS definition in
//usr/lib/x86_64-linux-gnu
On Sat, Jan 06, 2018 at 02:09:44PM +0100, John Paul Adrian Glaubitz wrote:
> > dh_compress: unknown option or error during option parsing; aborting
> > debian/rules:1354: recipe for target 'binary-native' failed
> > make: *** [binary-native] Error 25
>
> I'm running into this on ia64 now but I'm n
Package: gcc-7
Version: 7.2.0-16
Severity: normal
Tags: patch
As announced in https://lists.debian.org/debian-arm/2017/11/msg00045.html
this patch raises the armel baseline for buster from armv4t to armv5te.
--- debian/rules2.old 2017-11-18 22:12:44.946825904 +
+++ debian/rules2 2017-
Package: gfortran-7
Version: 7.2.0-14
Severity: serious
Control: affects -1 src:open-coarrays
Testcase:
$ gfortran global_field.f90 -fcoarray=lib
global_field.f90:126:0:
lhs%values(:) = rhs%state()
internal compiler error: Segmentation fault
Please submit a full bug report,
with preproces
Package: gcc-7
Version: 7.2.0-12
Severity: serious
Control: affects -1 src:amanda
https://buildd.debian.org/status/package.php?p=amanda&suite=sid
...
checking for gcc flag -fstrict-aliasing...
E: Build killed with signal TERM after 360 minutes of inactivity
Testcase:
(sid_mips-dchroot)bunk@mi
On Mon, Aug 21, 2017 at 04:02:03PM +0200, Matthias Klose wrote:
> On 10.08.2017 08:15, Adrian Bunk wrote:
> > Source: gcc-defaults
> > Severity: important
> > Tags: patch
> >
> > https://buildd.debian.org/status/fetch.php?pkg=lorene&arch=ppc64el&
Source: gcc-defaults
Version: 1.173d1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gcc-defaults.html
...
dh_compress -s -Ncpp-aarch64-linux-gnu -Ncpp-arm-linux-gnueabi
-Ncpp-arm-linux-gnueabihf -Ncpp-doc -Ncpp-mips-linux-gnu
-Ncpp-mips64el-linux-gnuabi64
Source: gcc-snapshot
Version: 20170923-1
Severity: serious
gcc-snapshot build depends on the transitional package realpath,
removed in coreutils 8.28-1.
The realpath program is part of the
(essential) coreutils package.
Source: gcc-7-cross-ports
Version: 6
Severity: serious
gcc-7-cross-ports build depends on the transitional package realpath,
removed in coreutils 8.28-1.
The realpath program is part of the
(essential) coreutils package since 8.23-1.
Source: gcc-7-cross
Version: 8
Severity: serious
gcc-7-cross build depends on the transitional package realpath,
removed in coreutils 8.28-1.
The realpath program is part of the
(essential) coreutils package since 8.23-1.
Source: gcc-7
Version: 7.2.0-7
Severity: serious
gcc-7 build depends on the transitional package realpath,
removed in coreutils 8.28-1.
The realpath program is part of the
(essential) coreutils package since 8.23-1.
Source: gcc-6-cross-ports
Version: 23
Severity: serious
gcc-6-cross-ports build depends on the transitional package realpath,
removed in coreutils 8.28-1.
The realpath program is part of the
(essential) coreutils package since 8.23-1.
Source: gcc-6-cross
Version: 25
Severity: serious
gcc-6-cross build depends on the transitional package realpath,
removed in coreutils 8.28-1.
The realpath program is part of the
(essential) coreutils package since 8.23-1.
Source: gcc-6
Version: 6.4.0-7
Severity: serious
gcc-6 build depends on the transitional package realpath,
removed in coreutils 8.28-1.
The realpath program is part of the
(essential) coreutils package since 8.23-1.
Source: gcc-5-cross-ports
Version: 11
Severity: serious
gcc-5-cross-ports build depends on the transitional package realpath,
removed in coreutils 8.28-1.
The realpath program is part of the
(essential) coreutils package since 8.23-1.
Source: gcc-5-cross
Version: 26
Severity: serious
gcc-5-cross build depends on the transitional package realpath,
removed in coreutils 8.28-1.
The realpath program is part of the
(essential) coreutils package since 8.23-1.
Source: gcc-5-cross
Version: 26
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gcc-5-cross.html
...
dh_installdirs -plibgfortran-5-dev usr/lib/gcc-cross/s390x-linux-gnu/5
dh_installdirs: Requested unknown package libgfortran-5-dev via -p/--package,
expected
On Tue, Sep 26, 2017 at 09:48:52AM +0100, Edmund Grimley Evans wrote:
>...
> This is not specific to cross-compiling and not even to gcc-6.
>
> We noticed the infinite loop when the buildd tries to build rnahybrid:
>
> https://buildd.debian.org/status/logs.php?pkg=rnahybrid&arch=armel
>...
In ad
On Thu, Aug 17, 2017 at 01:35:17PM +0200, Matthias Klose wrote:
>...
> by reassigning you stop tracking the xubble build failure.
We need to track the causes, not the symptoms - affects is
sufficient for the symptoms.
Like there's no point in opening 20 bugs in all the packages I've so
far seen
Source: gcc-defaults
Severity: important
Tags: patch
https://buildd.debian.org/status/fetch.php?pkg=lorene&arch=ppc64el&ver=0.0.0~cvs20161116%2Bdfsg-1%2Bb1&stamp=1502276276&raw=0
https://buildd.debian.org/status/fetch.php?pkg=dynare&arch=ppc64el&ver=4.5.1-1%2Bb1&stamp=1502287921&raw=0
https://buil
On Sat, Jul 01, 2017 at 01:33:14PM +0200, Matthias Klose wrote:
> On 30.06.2017 15:22, Adrian Bunk wrote:
> > On Thu, Jun 29, 2017 at 02:37:27PM +0200, Matthias Klose wrote:
> >> On 29.06.2017 06:51, Adrian Bunk wrote:
> >>> Package: libstdc++6
> >>>
On Thu, Jun 29, 2017 at 02:37:27PM +0200, Matthias Klose wrote:
> On 29.06.2017 06:51, Adrian Bunk wrote:
> > Package: libstdc++6
> > Version: 7.1.0-7
> > Severity: serious
> > Control: affects -1 src:mesa
> >
> > mesa FTBFS on armel due to:
> >
>
On Thu, Jun 29, 2017 at 02:37:27PM +0200, Matthias Klose wrote:
> On 29.06.2017 06:51, Adrian Bunk wrote:
> > Package: libstdc++6
> > Version: 7.1.0-7
> > Severity: serious
> > Control: affects -1 src:mesa
> >
> > mesa FTBFS on armel due to:
> >
>
Package: libstdc++6
Version: 7.1.0-7
Severity: serious
Control: affects -1 src:mesa
mesa FTBFS on armel due to:
https://buildd.debian.org/status/fetch.php?pkg=mesa&arch=armel&ver=17.1.3-2&stamp=1498610882&raw=0
...
llvm-config-4.0: relocation error:
/usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1
Package: gcj-6
Version: 6.3.0-8
Severity: serious
Control: affects -1 src:pdftk
The latest pdftk binNMU FTBFS on i386:
https://buildd.debian.org/status/package.php?p=pdftk&suite=sid
The relevant part of the build log is:
gcj: error trying to exec 'ecj1': execvp: No such file or directory
gcj-6 c
Package: gcc-6
Version: 6.3.0-8
Severity: serious
Control: affects -1 src:d-itg src:gtk-gnutella
https://buildd.debian.org/status/fetch.php?pkg=gtk-gnutella&arch=ppc64el&ver=1.1.8-2+b1&stamp=1488642493&raw=0
...
cc -c -I../.. -I.. -I../if/gen -pthread -I/usr/include/glib-2.0
-I/usr/lib/powerpc64
Package: libgcj-bc
Version: 6.2.1-1
Severity: grave
Control: affects -1 libecj-java-gcj ecj1 ecj-gcj ant-gcj ant-optional-gcj
$ cat /var/lib/dpkg/info/libgcj-bc\:amd64.shlibs
libgcj_bc 1 libgcj-bc (>= 6.2.1-3~)
$
That seems to be the reason why several packages can currently
not be installed i
Package: libgcj-common
Version: 1:6.2-1
Severity: normal
< bunk> Is there a reason or is it a bug that mips64el is not listed in
/usr/share/gcj/debian_defaults (package libgcj-common)?
< jcowgill> bunk: probably a bug left over from when gcj was broken on
mips64el
Control: retitle -1 gdc-6 PIE build failures
Control: severity -1 serious
I am setting the severity back to serious since this is breaking the
build of several packages.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been nee
Control: reassign -1 src:gcc-6 6.2.0-7
Control: affects -1 src:torus-trooper
On Sat, Nov 26, 2016 at 10:59:23AM +0100, Chris Lamb wrote:
>...
> torus-trooper fails to build from source in unstable/amd64:
>
> […]
>
> dh_auto_build -- DFLAGS="-frelease"
> make -j1 DFLAGS=-frelease
> ma
Source: yadifa
Version: 2.2.2-1
Severity: serious
https://buildd.debian.org/status/fetch.php?pkg=yadifa&arch=ppc64el&ver=2.2.2-1&stamp=1480164499
...
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./include/dnscore -Wdate-time
-D_FORTIFY_SOURCE=2 -DNDEBUG -g -DDNSCORE_BUILD -D_THREAD_SAFE -D_REENT
Source: libwebp
Version: 0.5.1-3
Severity: serious
https://buildd.debian.org/status/logs.php?pkg=libwebp&arch=armhf
...
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src/webp -DNDEBUG
-Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wall
-Wdeclaration-after-statement -Wextra -Wfloat-co
On Thu, Nov 24, 2016 at 04:35:28PM +0100, Guillem Jover wrote:
>...
> On Thu, 2016-11-24 at 14:52:33 +, Thorsten Glaser wrote:
>...
> > Worse, they break *differently* on whether…
> >
> > >Precisely to make the behavior consistent on all architectures, dpkg
> > >enables PIE (conditionally if n
Control: reassign -1 release.debian.org
Control: severity -1 normal
Control: retitle -1 nmu: zlib_1:1.2.8.dfsg-2
Control: affects -1 src:zlib
On Mon, Oct 31, 2016 at 03:27:11PM +0100, Charlemagne Lasse wrote:
> Package: gcc-6
> Version: 6.2.0-10
> Severity: serious
> X-Debbugs-CC: lede-...@lists.i
On Sun, Oct 23, 2016 at 03:17:06PM +0200, Bálint Réczey wrote:
> Hi Adrian,
>
> 2016-10-23 13:26 GMT+02:00 Adrian Bunk :
> > On Sun, Oct 23, 2016 at 12:29:42PM +0200, Bálint Réczey wrote:
> >> Hi Ardian,
> >
> > Hi Bláint, ;-)
>
> I'm sorry. :-)
On Sun, Oct 23, 2016 at 12:29:42PM +0200, Bálint Réczey wrote:
> Hi Ardian,
Hi Bláint, ;-)
> 2016-10-23 10:18 GMT+02:00 Adrian Bunk :
> > Hi Bálint,
> >
> > there is some confusion regarding how static libraries should be
> > compiled now.
> >
> >
Hi Bálint,
there is some confusion regarding how static libraries should be
compiled now.
Your bugs (e.g. #837350) say "Please build libfoo.a with -fPIC".
Why do these say -fPIC and not -fPIE?
My current understanding is that a binNMU would recompile the the static
library with PIE (not PIC),
Control: severity -1 important
Control: tags -1 -stretch
I am lowering the severity of these bugs exposed by
#841292 (gcc-6: flexible array support broken).
gcc 6 has the problematic change reverted, so this shouldn't be
a problem for stretch.
This is expected to be a FTBFS with gcc >= 7,
so the
Package: gcc-doc
Version: 5:4.8.2-3
Severity: normal
gcc-doc should be updated to point at gcc-4.9-doc.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140621162519.
I just tried compiling the emacs22 package from unstable with gcc 4.3,
and ran into an issue similar to what Martin described back in
May 2007 for another package in #425544, with the following differences:
- it's not an infinite loop but a one minute hang
(see the alarm() in conftest.c)
- the b
Package: java-gcj-compat-dev
Version: 1.0.41-1
Severity: important
s/ecj-boostrap-gcj/ecj-bootstrap-gcj/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, Mar 12, 2005 at 04:48:46PM +0100, Thiemo Seufer wrote:
> Adrian Bunk wrote:
> [snip]
> > #define sprintf __builtin_sprintf
> >
> > int main()
> > {
> > char str[] = "abc";
> > char buf[10];
> >
> > sprintf(buf
Package: gcc-3.4
Version: 3.4.3-11
Severity: normal
The info file says:
<-- snip -->
With the `-fno-builtin-FUNCTION' option only the built-in function
FUNCTION is disabled. FUNCTION must not begin with `__builtin_'.
If a function is named this is not built-in in this version
Package: gcc-3.4
Version: 3.4.2-3
Severity: serious
buildd.debian.org lists the following build error on mips and mipsel:
<-- snip -->
...
/build/buildd/gcc-3.4-3.4.2/build/gcc/xgcc -shared-libgcc -B/build/buildd/gcc-3
.4-3.4.2/build/gcc/ -nostdinc++ -L/build/buildd/gcc-3.4-3.4.2/build/mips-l
Package: gcc-3.4
Version: 3.4.1-4sarge1
Severity: grave
Tags: sarge
Rebuilding sarge gcc-3.4 with sarge binutils results in a
binutils dependency that is not sufficient.
Package: gcc-3.3
Version: 1:3.3.4-6sarge1.2
Severity: grave
Tags: sarge
Rebuilding sarge gcc-3.3 with sarge binutils results in a
binutils dependency that is not sufficient.
Hi Andreas,
your second suggestion for this bug ("gcc-3.3 on i386, mipsel and sparc
is built against binutils 2.15 and will try to use --as-needed") is
flawed, since this will break again with any binary NMU or other update
for gcc-3.3.
The only real choices are:
1. update the dependency on b
severity 263019 grave
thanks
If gcc-3.4 requires binutils (>= 2.15) the dependencies need an update.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
reassign 218710 gnumeric
thanks
On Sun, Jan 25, 2004 at 10:02:09AM +0100, J.H.M. Dassen (Ray) wrote:
> On Sun, Jan 25, 2004 at 03:12:14 +0100, Adrian Bunk wrote:
> > I wasn't able to reproduce this issue you reported (FTBFS with gcc 2.95 in
> > dialog-simulation.c) using
On Fri, May 30, 2003 at 10:54:51AM +0200, Matthias Klose wrote:
> Adrian Bunk writes:
> > Package: gcc-3.3
> > Version: 1:3.3-2
> > Severity: normal
> >
> >
> > Building gcc-3.3 on a woody system with some additional updates produces
> &g
reassign 194339 gcc-3.3
retitle 194339 __thread problem with woody backports of gcc 3.3
thanks
I had to solve the same problem in my backport of gcc 3.3 to woody [1].
There are no changes to the glibc packages in woody needed, gcc already
includes a fix. The problem is that the build of the Debi
Package: gcc-3.3
Version: 1:3.3-2
Severity: normal
Building gcc-3.3 on a woody system with some additional updates produces
the following messages:
<-- snip -->
...
make[2]: Entering directory `/home/bunk/Pakete/gcc-3.3/gcc-3.3-3.3ds9/build/i386
-linux/libstdc++-v3'
(srcdir=`cd ../../../src/l
Package: libstdc++5
Version: 1:3.2.3-0pre8
Severity: minor
The package description of the various libstdc++5* packages
(libstdc++5, libstdc++5-dev, libstdc++5-3.3-dev) talks about
v3 and g++-3.0 .
severity 180048 serious
thanks
I've observed the same problem ("automake-1.4: command not found") while
recompiling gcc-3.2 for woody.
I'm changing the severity to "serious" since this is a "cannot build
from source" bug.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked sud
Package: gpc-2.1-3.2
Version: 1:3.2.2.20021128-0pre1
Severity: important
Christoph Bayer <[EMAIL PROTECTED]> sent me the following
mail (he noticed this problem in a backport of the gcc 3.2 packages for
woody I provide at [1]):
<-- snip -->
I have noticed that gpc-2.1-3.2 recomments librx1g-d
Package: gcc-3.1
Version: 1:3.1.1-0pre1
Severity: normal
<-- snip -->
/usr/share/doc/gcc-3.1$ ls -la |grep info
lrwxrwxrwx1 root root 28 Jun 2 21:07 gcc-3.1.1.info.gz ->
../../info/gcc-3.1.1.info.gz
/usr/share/doc/gcc-3.1$
<-- snip -->
1. This is a dangling symlink beca
Package: chill-2.95
Version: 1:2.95.4-0.011223
Severity: normal
Package: chill-2.95
...
Version: 1:2.95.4-0.011223
...
Description: The GNU 1 compiler.
NOTE: This is not a final release, but taken from the CVS gcc-2_95-branch
(dated 20010522).
.
This is the ITU 1 compiler. 1 is
...
It seem
Package: gcc272
Version: 2.7.2.3-18
Severity: grave
Since unstable/testing does no longer include kernel 2.0.x (and these
kernels won't work with the modutils in unstable/testing) it's in
my opinion time to remove gcc272 from unstable.
I've set the severity to be RC so that this doesn't be forgo
1 - 100 of 104 matches
Mail list logo
