Source: gcc-14-cross-ports
Version: 4
Severity: wishlist
X-Debbugs-Cc: pkg-qemu-de...@lists.alioth.debian.org
Please consider building loong64 cross-compiler too, once
this architecture has become one of debian ports.
In particular, this is needed to build qemu (only a tiny
part so far, vdso.so
Package: g++-12
Version: 12.2.0-14
Severity: normal
X-Debbugs-Cc: iv...@isle.spb.ru
Dear Maintainer,
When I compile c++ code which has an error (method invoked on
null class pointer) the following problem occurs: the actual
call does not crash, since 'this' pointer is not really used
in called
On Wed, May 17, 2023 at 11:27:43AM +0200, John Paul Adrian Glaubitz wrote:
> Hi Michael!
>
> On Tue, 2023-05-16 at 20:25 +1200, Michael Cree wrote:
> > On Tue, May 16, 2023 at 09:38:56AM +0200, John Paul Adrian Glaubitz wrote:
> > > After a long discussion on IRC and t
execution down to
ev56.) I have tested this in the past with a rebuild of most packages
that are in the base essential chroot in the past and it works well.
Regards,
Michael.
Package: gcc-12-alpha-linux-gnu
Version: 12.2.0-1cross3
Severity: normal
Starting this version of gcc, -mbuild-constants option causes it to produce
an ICE. Example is below. This is an old code, always worked before, in
particular with gcc-11.
Removing -mbuild-constants fixes the ICE. But
It is the same on arm64 too, eg:
https://buildd.debian.org/status/package.php?p=qemu=bullseye-backports
/mjt
On Sat, 6 Feb 2021 08:54:57 +0100 Dennis Filder wrote:
Control: tag -1 - patch + moreinfo
After looking into this some more, I don't think this is necessarily a
bug in dwz, but it could also be either someone using rogue DW_OP_*
definitions with values 0x00 and 0x01 or a buggy
Package: gcc-s390x-linux-gnu
Version: 4:11.2.0-2
Severity: normal
Current package have:
Depends: cpp-s390x-linux-gnu (= 4:11.2.0-2), gcc-11-s390x-linux-gnu (>=
11.2.0-1~)
It looks like after switch to gcc-12, it should be gcc-12-s390x-linux-gnu
instead.
Currently in unstable,
severity 1000892 serious
thanks
As part of the effort to limit the number of llvm packages in the
archive, please upgrade to -13 (or -12).
It has:
llvm-9-dev [armel armhf], libclang-9-dev [armel armhf], clang-9 [armel
armhf], clang-format-9 [armel armhf],
llvm-toolchain-9 has now been
Package: libdebuginfod1
Version: 0.183-5
Severity: important
Dear Maintainer,
There is no architecture entry for all on buildd.debian.org and on packages on
incoming.debian.org
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (710, 'unstable'), (670,
On Wed, 28 Oct 2020 12:30:41 +0100 Sebastian Ramacher
wrote:
On 2020-10-24 07:38:39 +0300, Michael Tokarev wrote:
...
> Hmm. So this looks like a gcc ICE bug. Here's the code in question:
> ...
> > | /<>/linux-user/m68k/signal.c:44:1: internal compiler error:
‘verify_typ
bug report.
> > See for instructions.
> > make[3]: *** [Makefile:194: exxengy.o] Error 1
Michael
Thanks for making the issue upstream with the minimal example!
I just built with gcc-snapshot 1:20201023-1 and now I get a build error:
https://github.com/seqan/seqan3/issues/2236#issuecomment-723232918
On Fri, 6 Nov 2020 at 17:13, Matthias Klose wrote:
> Control: forwarded -1
Package: g++-10
Version: 10.2.0-16
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
g++-10 10.2.0-16 causes the seqan3 3.0.2+ds-3 package to FTBFS due to a
g++ internal compiler error, which does not occur with g++-10 10.2.0-15
Details including a build log and processed
Package: gcc-10
Version: 10.2.0-16
Severity: wishlist
When upgrading from 10.2.0-15 to 10.2.0-16 aptitude reports that gcc-10 is
282MB larger, g++-10 is 312MB larger, and cpp-10 is 283MB larger. In -15
/usr/lib/gcc/x86_64-linux-gnu/10/lto1 is 26M and in -16
/usr/lib/gcc/x86_64-linux-gnu/10/lto1
We worked around this by removing the use of `goto` within the OpenMP
loop:
https://github.com/soedinglab/MMseqs2/pull/309/commits/a5b2f230bb6fb3ab79bed626d2f89d59e1a5b2df
However, a non-crash error message would be appreciated.
On Tue, 19 May 2020 12:38:57 +0200 "Michael R. Crusoe"
wrote:
> Attached is the reduced example.
Pardon me, that first attachment only fails on gcc-snapshot's g++
Attached is an example that does fail on g++-9, g++-10, and
gcc-snapshot's g++
class a {
public:
long b();
};
cla
Package: g++-9
Version: 9.3.0-12
Severity: normal
Tested with g++10 and g++ from gcc-snapshot 1:20200507-3
$ g++ -Og -g -fsanitize=address -fno-omit-frame-pointer
-fno-optimize-sibling-calls -fopenmp -o clusthash.cpp.o -c clusthash_prep.cpp
during GIMPLE pass: sanopt
clusthash_prep.cpp: In
5-19 09:49:31.0
+0200
@@ -1,3 +1,10 @@
+creduce (2.10.0+20200116-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/rules: Remove reference to non-existant Texinfo manual
+
+ -- Michael R. Crusoe Tue, 19 May 2020 09:49:31
+0200
+
creduce (2.10.0+20200116-1) unstable; urge
On Debian Unstable(gcc v9.3.0), gcc won't link libraries that are passed
via "-l" before the source file. This does NOT happen on Debian
Stable(gcc v8.3.0) or on my Gentoo system(gcc v9.2.0). Is this expected
behavior?
Example:
Works:
$ gcc ./simple_app.c -lX11 -o ./simple_app.out
Broken:
Hi,
On Sat, Sep 07, 2019 at 10:50:34PM +0200, Michael Banck wrote:
> > Program received signal SIGSEGV: Segmentation fault - invalid memory
> > reference.
> >
> > Backtrace for this error:
> > #0 0x7f063149eb40 in ???
> > #1 0x7f063149dd75 in ???
and I can confirm the fix.
Andreas, thank you for the quick mesa update! Feel free to drop my
workaround again in one of your next uploads.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Descriptio
onfirm the findings of GSR that this appears to be a gcc-8
regression. Rebuilding src:mesa with gcc-7 fixed those issues for me.
Might be a good idea to (temporarily) switch to gcc-7 depending on how
long it takes until this fix is applied in gcc-8.
The attached patch worked for me.
Regards,
Michael
package: src:gcc-6
version: 6.4.0-18
severity: grave
control: affects -1 src:chromium-browser
forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86166
This was marked as a duplicate upstream and closed, but it seems like
it should be considered a separate issue.
The latest chromium upload
package: src:gcc-8
severity: normal
version: 8.1.0-3
Wine now relies on this [0], but it seems to be missing in gcc on
arm64. It is supported in newer versions of clang on arm64.
Best wishes,
Mike
[0]https://buildd.debian.org/status/fetch.php?pkg=wine-development=arm64=3.8-1=1526746237=0
Package: cpp-8
Version: 8-20180321-1
Severity: minor
Dear Maintainer,
/usr/lib/gcc/x86_64-linux-gnu/8/cc1 is not stripped and therefore quite
large (171M). The same is true for /usr/lib/gcc/x86_64-linux-gnu/8/lto1.
For other gcc versions, these files are stripped, so I guess they should
also be
.pc files should really
contain -std=... ? What happens if you end up with multiple ones on the
same command line?
I'd prefer to have some input from our GCC maintainers on this issue.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from
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
and/or the
created libraries are different depending on the fortran module version.
We thought it wasn't, but it's probably a good idea to make sure.
Michael
Michael
providing lock-free atomics.
Regards,
Michael Karcher
--
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/55ac34cb.3020...@mkarcher.dialup.fu-berlin.de
Package: gcc-4.9
Version: 4.9.1-16
Severity: important
The currently available version of gcc 4.9 for mips miscompiles boolean
negation under certain circumstances.
The assembly contains the not instruction, which represents bitwise negation,
which is not appropriate, as
both 0 and 1 get mapped
Of course I meant to write The currently available version of gcc 4.9
for sh4... in the first paragraph of the bug description. I am sorry
for any confusion this might have caused.
Regards,
Michael Karcher
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject
control: tag -1 patch
A patch for the autoconf rc issues is available in bug #695704 for autoconf2.59.
Best wishes,
Mike
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On Fri, Oct 10, 2014 at 3:23 AM, Matthias Klose wrote:
Am 10.10.2014 um 06:39 schrieb Adam D. Barratt:
On Thu, 2014-10-09 at 23:01 -0400, Michael Gilbert wrote:
Note that the window for the next stable update is closing in about a
week, so there isn't a lot of time.
Actually, the /point
Hi,
I would like to ask for your opinion about uploading a newer gcc
version to wheezy?
This is to be able to continue building chromium security updates,
which has been discussed with the release team [0]. They've requested
that I discuss it with gcc maintainers, which is the reason for this
://people.debian.org/~mbanck/tce_mrcc_energy.s.wrong
Michael
--
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/20140923231105.ga17...@raptor.chemicalconnection.dyndns.org
Package: nfs-kernel-server
Version: 1:1.2.8-8
Followup-For: Bug #757835
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
This bug is already fixed in upstream (included since 1.3.1-rc2):
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=25e83c2270b2d2966c992885faed0b79be09f474
package: src:gcc-4.4, src:gcc-4.6, src:gcc-4.7, src:gcc-4.8, src:gcc-4.9
severity: serious
tags: security
Several integer overflow issues affecting all gcc versions have been
fixed in libgfortran:
http://www.openwall.com/lists/oss-security/2014/07/23/7
Best wishes,
Mike
--
To UNSUBSCRIBE,
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.9suite=unstable
-- System Information:
Debian Release: jessie/sid
APT prefers
reference to
`wxCommandEvent::Clone() const'
collect2: error: ld returned 1 exit status
For flamerobin a workaround has been put in place to fix the FTBFS reported in
#746847.
Best,
Michael
pgpiFLiktn2tH.pgp
Description: PGP signature
ifneq ($(GFDL_INVARIANT_FREE),yes)
debian_patches += alpha-ieee-doc
endif
Thanks
Michael.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org
the
toolchain
for this port. This is the current status, please correct me if I'm wrong.
- alpha, no feedback, CCing Michael Cree.
I had hoped to get glibc 2.17 building on Alpha before switching to gcc-4.8, but
that's proving to be a rather difficult nut to crack. Assuming that there is
nothing
-c unlimited
$ ./helloworld.O
zsh: segmentation fault (core dumped) ./helloworld.O
$ gdb helloworld.O /tmp/helloworld.O.core.18748
Reading symbols from /home/michael/gocode/src/helloworld.O/helloworld.O...done.
[New LWP 18748]
warning: Could not load shared library symbols for linux-vdso.so.1
(for whatever
reason).
[...]
Could you please clarify in which version that is fixed (and which might still
be broken)? Ideally, please tag the bug accordingly (if you feel this is too
much to ask for, I will do so once you provide the info).
Thanks a lot,
Michael
pgpVGStNMyZdc.pgp
Description: PGP
, namely:
ifneq (,$(filter $(DEB_TARGET_ARCH),alpha))
LDFLAGS += -Wl,--no-relax
endif
added to debian/rules2.
Actually the same fix needs to be applied to all of gcj-4.7, gnat-4.6,
gcj-4.6 and gcc-4.6. Do I need to file a bug report for each one?
Cheers
Michael.
--
To UNSUBSCRIBE, email
On Fri, Jul 26, 2013 at 02:37:15PM +0200, Matthias Klose wrote:
Am 25.07.2013 14:25, schrieb Michael Banck:
What to do about the compatibilty is a different matter, did this come
up before?
looks like one hand in the debian-science team doesn't know what the other
hands
are doing
on the GCC
list referenced therein:
https://lists.fedoraproject.org/pipermail/packaging/2007-October/003930.html
http://gcc.gnu.org/ml/fortran/2007-10/msg00306.html
Cheers,
Michael
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Fri, Jun 14, 2013 at 6:07 AM, Matthias Klose wrote:
this is #402694. It is disappointing that the security did become a management
only team. Note that this is an issue, where even a member of the security
team
is involved upstream, doesn't comment, doesn't backport the patch upstream,
Package: gcc-4.7
Severity: serious
Version: 4.7.0-1
Tags: security, patch
Hi,
An integer overflow issue was discovered for gcc-4.7:
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2002-2439
This is already fixed in gcc-4.8.
These seem to be the two relevant patches that fix the problem:
) and #682197 (same problem seen in gnat-4.6), namely
adding to debian/rules2 the following
ifneq (,$(filter $(DEB_TARGET_ARCH), alpha))
LDFLAGS = -Wl,--no-relax
endif
should enable gcc-4.8 to build on Alpha.
Cheers
Michael.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
On Wed, Jan 30, 2013 at 12:56:18AM +0100, Matthias Klose wrote:
Am 29.01.2013 09:30, schrieb Michael Cree:
should enable gcc-4.8 to build on Alpha.
please could you check if the build does succeed with this patch?
Yep, no probs. For the test I used:
ifneq (,$(filter $(DEB_TARGET_ARCH
Package: libstdc++6-4.7-doc
Version: 4.7.2-4
Severity: normal
Dear Maintainer,
I can no longer use commands containing std:: like man std::vector to access
the man pages now, which worked in previous versions. Please fix it.
Michael Tsang
-- System Information:
Debian Release: wheezy/sid
Hi Tobias,
Tobias Hansen than...@debian.org writes:
The bug is in gnat-4.4. You tested the wrong package.
I missed the fact that gnat-4.4 is _also_ in testing. My apologies.
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject
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
in performance to gcc/g++/gcj/etc since only the link
of the stage-1 compiler does not get relaxation optimisation.
Cheers
Michael.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http
On 16/07/12 21:27, Michael Cree wrote:
gcc-4.5 FTBFS on alpha with GPREL16 relocation truncation errors in the
link of cc1-dummy during stage 1 compilation. Full build log is at:
Ha, ha, I see I added the patch tag to the bug report but no patch :-/
Adding the following in debian/rules2
attached here, sorry.)
The old version of gcc-4.5 at debian-ports currently breaks installation
of the Alpha port with debootstrap, so an upload of a fix would be very
much appreciated, but we will understand if this is not possible because
of the freeze.
Cheers
Michael.
--
To UNSUBSCRIBE, email
+ tmake_file=${tmake_file} alpha/t-linux
extra_options=${extra_options} alpha/elf.opt
target_cpu_default=MASK_GAS
;;
With that my test build of gcc-4.7 has past the previous point of
failure and is in the test suite as I write this.
Thanks,
Michael.
--
To UNSUBSCRIBE
Fixed in gcc-4.6 version 4.6.2-13. Both git and libarchive, which
previously FTBFS because of this bug, now compile and their test suites
pass. Feel free to close the bug report.
Cheers
Michael.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of unsubscribe
Note that we'll backport to FSF 4.6 if appropriate.
On Jan 29, 2012 7:03 AM, Loïc Minier l...@dooz.org wrote:
forwarded 657682 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50313
tags 657682 + confirmed fixed-upstream upstream
stop
Hi
On Fri, Jan 27, 2012, Peter Green wrote:
On 12/01/12 10:56, Michael Cree wrote:
Package: gcc-4.6
Version: 4.6.2-11
git_1:1.7.8.3-1 FTBFS because of incorrect code generation by gcc-4.6.
This is now PR 51994.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51994
Cheers
Michael.
--
To UNSUBSCRIBE, email to debian-gcc-requ
, so can't be compiled directly, sorry. My attempt to reduce
it further into a minimal self contained unit no longer exhibited the
incorrect compilation.
Cheers
Michael.
/*
* GIT - The information manager from hell
*
* Copyright (C) Linus Torvalds, 2005
* Copyright (C) Johannes Schindelin
Source: gcc-defaults
Version: 1.109
Severity: wishlist
User: debian-al...@lists.debian.org
Usertags: alpha
Please default to gcc-4.6 on the Alpha architecture.
Thanks,
Michael Cree.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
no data dependencies with each
other or with instructions in between so can be safely swapped.
Cheers
Michael
[1] ../src/configure -v --with-pkgversion='Debian 4.6.0-8'
--with-bugurl='file:///usr/share/doc/gcc-4.6/README.Bugs'
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--program
. Or libppl-dev, so you don't break next time. Why are the
libppl dev packages versioned anyhow?
Because newer PPL releases might break gcc. But supposedly this isn't that much
of an issue for APRON, hence I'd agree that libapron-dev should build-depend on
libppl-dev.
Hope this helps,
Michael
(presumably producing suboptimal, but at least working, code).
Cheers
Michael.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d87125c.1040...@orcon.net.nz
a lot,
Michael
pgpLmm7HIeqA8.pgp
Description: PGP signature
is easier ;)
Could you please only let me know which versions you refer to as old and
new? It seems that Debian has 0.15.9 while on the homepage of cloog I can only
find 0.14.1 (and git even has only 0.14.0 tagged) and some Development
Version.
Thanks a lot,
Michael
pgpPqXiYgAuXG.pgp
developers I don't expect this to change any time soon.
Best regards,
Michael
pgpnIEUr2UezV.pgp
Description: PGP signature
?
I'll of course check this myself if you could just give me any hints which
package to try to build and, if you already know of any, which obstacles I might
find.
Thanks a lot,
Michael
pgp6zbff3mryN.pgp
Description: PGP signature
[...]
May I suggest to disable (for now) the Prolog interface on m68k,
as it’s in a sort-of rebootstrapping process anyway?
Thanks a lot for looking into this; I'll try to fix this ASAP. Indeed I hadn't
expected any architectures to have older swi-prolog versions lingering around.
Best,
Michael
also be ready for later migration to squeeze).
Best,
Michael
pgpOI0fK4T5S0.pgp
Description: PGP signature
a lot,
Michael
pgp48wvmEuOUf.pgp
Description: PGP signature
else I can do; the complete sources are
still there on abel.d.o.
Best regards,
Michael
[1]
https://buildd.debian.org/fetch.cgi?pkg=pplver=0.10.2-7arch=armelstamp=1280947057file=log
[2]
https://buildd.debian.org/fetch.cgi?pkg=pplver=0.10.2-6arch=armelstamp=1267963469file=log
[3] touch
tests.
I was aware of that and already have a workaround tested and ready for upload; I
just did not get around to do the final build. I'll try to get it done as soon
as possible.
Best,
Michael
pgpzCdLYns9Ma.pgp
Description: PGP signature
On 02/19/10 10:32, Michael Tautschnig wrote:
Package: ppl
Version: 0.10.2-4
Severity: serious
the prolog tests fail at least on powerpc. Please either fix these
that the package is built again, or ignore the failures in the
prolog testsuite. ppl is used as a gcc build-dependency, and we
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
and there was a gcc upload in between which could
have caused that regression.
Michael
[1]
https://buildd.debian.org/fetch.cgi?pkg=fsarchiver;ver=0.6.5-1;arch=alpha;stamp=1263529331
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1
On 06/12/09 23:21, Kurt Roeckx wrote:
On Wed, Dec 02, 2009 at 12:18:47AM -0500, Matt Turner wrote:
On Tue, Dec 1, 2009 at 3:08 PM, Michael Creemc...@orcon.net.nz wrote:
On 18/11/2009, at 9:31 AM, Kurt Roeckx wrote:
Package: gcc-4.3
Version: 4.3.4-5
Hi,
I recently started seeing several
[ prephitmp.1208 ])
(const_int 0 [0x0]))) -1 (nil))
packet-l2tp.c:1680: internal compiler error: in extract_insn, at
recog.c:2001
Would this be http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42113 ??
Cheers
Michael.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
On 02/12/09 18:18, Matt Turner wrote:
On Tue, Dec 1, 2009 at 3:08 PM, Michael Creemc...@orcon.net.nz wrote:
On 18/11/2009, at 9:31 AM, Kurt Roeckx wrote:
Package: gcc-4.3
Version: 4.3.4-5
Hi,
I recently started seeing several cases of gcc giving an error
message like this:
packet-l2tp.c
try to dig further yourself? Otherwise I'm absolutely
clueless how to handle this. Obviously it fails to build, which is also
reproducible on your hosts, but seemingly not in any other environment. I think
we'll need some further examinations using strace and gdb at least.
Thanks a lot,
Michael
the last thing
before install, and it worked fine on all Debian buildds just a few days ago!?
Thanks,
Michael
pgp4e76dmcQcg.pgp
Description: PGP signature
On Monday 26 October 2009 09:22:26 Marco d'Itri wrote:
I would like to propose enabling[1] the GCC hardening patches that Ubuntu
uses[2].
Seconded.
Thirded.
+1.
Thanks for bringing this up,
Michael
pgpcMDHNXCorM.pgp
Description: PGP signature
Excerpts from Michael Tautschnig's message of Tue Sep 15 16:57:26 +0200 2009:
Yes, there are people caring about this package. Building the binary
packages,
however, is a fairly large burden for your buildds, therefore we try to
keep the
number of uploads low. I will try to see which
to compile the program.
This is not a bug in the Eclipse compiler itself but in the class library
it uses. When GCJ got updated to version 4.4.0 the Scanner class was
introduced and it now compiles.
Cheers,
Michael
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject
with real-life work).
Sorry,
Michael
pgpd0OuJRhBNd.pgp
Description: PGP signature
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 upload of binutils
Submitter-Id: net
Originator:Michael Walle
Organization:
Confidential: no
Synopsis: segfault with bitfields in structs
Severity: serious
Priority: medium
Category: c
Class: ice-on-legal-code
Release: gcc (Debian 4.3.2-1.1) 4.3.2
Environment:
System: Linux
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=rsyslogver=3.22.0-1arch=powerpcstamp=1242425299file=log
for details.
Cheers,
Michael
-- System
Julien Cristau wrote:
On Mon, Mar 2, 2009 at 23:22:36 +0100, Michael Tautschnig wrote:
We only build the user-docs nowadays, and that actually wouldn't be
necessary if
Debian's build system did what the policy says: There is no need to
re-build the
architecture independent stuff
than kindly asking you to
accept the situation. I'll do my best to keep the frequency of uploads as low as
possible such as not to block the buildds for too long. If you see any option
for improvements I'm of course open to integrate them with the build rules of
the ppl package.
Thanks,
Michael
is appropriate.
Thanks again and sorry for the noise,
Michael
pgpBfDmeBqKQQ.pgp
Description: PGP signature
the package barely useable in that case. Upstream already has a
patch in CVS that will be picked up for 0.10-2.
Best,
Michael
pgpiSWAzikuvn.pgp
Description: PGP signature
Package: gcc-4.3
Version: 4.3.2-1
Severity: important
gcc stops with an internal compiler error when compiling mplayer 2008-12-12
snapshot.
cc -Wdisabled-optimization -Wno-pointer-sign -Wdeclaration-after-statement
-std=gnu99 -Wall -Wno-switch -Wpointer-arith -Wredundant-decls -O4 -mcpu=970
Hi Bastian,
Thanks for replying and checking stuff.
On Thu, Jul 17, 2008 at 03:34:59AM +0200, Michael Tautschnig wrote:
When rebuilding diagnostics, it failed on s390 during the selftests [0]. The
failing piece of code is attached.
This includes too many preprocessor magic. Please
Michael Tautschnig wrote:
apparently ppl 0.10 pre34 still fails to build on some architectures because
of
FPU_* macros not being defined. Please see
http://buildd.debian.org/fetch.cgi?pkg=pplver=0.10~pre34-1arch=armstamp=1223724338file=log
for details.
Hi Michael,
yes, we received
Dear developers,
apparently ppl 0.10 pre34 still fails to build on some architectures because of
FPU_* macros not being defined. Please see
http://buildd.debian.org/fetch.cgi?pkg=pplver=0.10~pre34-1arch=armstamp=1223724338file=log
for details.
Thanks,
Michael
pgp65RWiokeLZ.pgp
Description
to testing, if I'm not mistaken. Or am
I getting something wrong?
Thanks,
Michael
pgp6yyAlRUErN.pgp
Description: PGP signature
Michael Tautschnig writes:
Assume we do build the default gcc depending on a libppl0, now the
libppl soname is changed to libppl1, a new ppl source is uploaded, and
suddendly libppl0 isn't available anymore. And we still need to
rebuild gcc using gcc. Making the ppl source versioned
1 - 100 of 218 matches
Mail list logo
