On Sat, 24 Nov 2018 09:33:11 +0100 Sven Joachim wrote:
> Source: gcc-8
> Version: 8.2.0-10
>
> The miscompilation of mesa has been fixed in the latest gcc-8 upload,
> please see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87859 for
> details.
I recompiled mesa with 8.2.0-10 and I can confirm th
y=medium
+
+ * Non-maintainer upload.
+ * Force compilation against gcc-7, gcc-8 miscompiles mesa
+See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87859
+
+ -- Michael Biebl Thu, 22 Nov 2018 03:32:38 +0100
+
mesa (18.2.5-2) unstable; urgency=medium
* Move KHR/khrplatform.h from libegl
Am 29.09.2015 um 16:43 schrieb Matthias Klose:
> On 29.09.2015 13:47, Michael Biebl wrote:
>> Am 28.09.2015 um 16:59 schrieb Aurelien Jarno:
>>> Source: glibmm2.4
>>> Version: 2.46.1-1
>>> Severity: serious
>>>
>>> glibmm2.4 version 2.46.1
Am 28.09.2015 um 16:59 schrieb Aurelien Jarno:
> Source: glibmm2.4
> Version: 2.46.1-1
> Severity: serious
>
> glibmm2.4 version 2.46.1-1 started to use C++11 features in the headers
> it exports, but pkg-config --cflags doesn't return -std=c++11. Given the
> default is still -std=gnu++98 in GCC 5
Source: gcc-4.9
Version: 4.9.0-11
Severity: serious
The package FTBFS on i386 and hurd-i386 but successfully built in the
past.
Complete build log at [1]
[1] https://buildd.debian.org/status/package.php?p=gcc-4.9&suite=unstable
-- System Information:
Debian Release: jessie/sid
APT prefers u
Package: gcc-4.7-base
Version: 4.7.2-1
Severity: serious
I do have multiarch enabled: amd64 being the primary arch, i386 the secondary.
During today's upgrade I got the following error message:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correc
severity 565455 normal
thanks
downgrading to normal as alpha is no longer a release arch and it builds fine on
all other architectures.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital si
Package: gcc-4.4
Version: 4.4.2-9
Severity: important
Hi,
compiling fsarchiver 0.6.5-1 fails on alpha [1]
gcc -DHAVE_CONFIG_H -D_REENTRANT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE
-D_GNU_SOURCE -I. -I..-g -O2 -Wall -std=gnu99 -rdynamic -ggdb
-I/usr/include/ext2fs -I/usr/include/et -l
reassign 532821 binutils
found 532821 2.19.1-1
block 528145 by 532821
thanks
Michael Biebl wrote:
> I'm cloning the bug for gcc, because this is (one of) the packages of the
> build
> toolchain that was updated between the 1.2.12-1 and 1.2.14-2 build of dbus.
> The
> last up
Package: gcc-4.3
Version: 4.3.3-10
Severity: serious
Justification: causes package to ftbfs
Hi,
currently rsyslog ftbfs on powerpc due to a ICE.
See
https://buildd.debian.org/fetch.cgi?&pkg=rsyslog&ver=3.22.0-1&arch=powerpc&stamp=1242425299&file=log
for details.
Cheers,
Michael
-- System Infor
Package: gcc-4.2-base
Version: 4.2.4-3
Severity: normal
I was wondering why gcc-4.2-base is priority required given that gcc-4.3-base
is around which already is priority required.
The other gcc-*-base packages, like gcc-4.1-base and gcc-3.4-base, have
priority optional. Should be priority of gcc-
Package: libstdc++6
Version: 4.2.2-5
Severity: important
The latest upgrade of libstdc++6 on i386 introduced a dependency on lib64gcc1,
which in turn pulls libc6-amd64 (10Mb installed!).
As my machine is i386 i.e. 32 bit only (pentium m) I don't want to have
libc6-amd64 and lib64gcc1 installed.
I
12 matches
Mail list logo
