Package: libphobos-5-dev
Version: 5-20150205
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I assume that at the time, gcc-5-base had an 0205 version, but being
experimental, has moved on, and left gdc/phobos behind, so all (I know,
I know) that's needed is for a rebuild
nd of process memory map.
configure:3474: $? = 1
configure:3481: error: in `/usr/oms/src/libpsl':
configure:3483: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
Regards, Tim
-- System Information:
Debian Release:
fff5889000-0x75bdb000
0x75bdb000-0x75bf1000 /lib/x86_64-linux-gnu/libgcc_s.so.1
0x75bf1000-0x75df /lib/x86_64-linux-gnu/libgcc_s.so.1
...
With Best Regards, Tim
On 07/20/2017 05:09 PM, Matthias Klose wrote:
> On 20.07.2017 14:45, Tim Ruehsen wrot
On 07/20/2017 05:09 PM, Matthias Klose wrote:
> On 20.07.2017 14:45, Tim Ruehsen wrote:
>> Package: gcc-6
>> Version: 6.4.0-1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> building autotools packages with address sanitizer currently breaks with
Package: libstdc++6
Version: 12.2.0-14
Severity: normal
File: libstdc++.so
#0 0x7f2c7daa4ccc
__pthread_kill_implementation (libc.so.6 + 0x8accc)
#10 0x556d13d51d8e n/a
(index++ + 0xed
This can be closed the issue is no longer occurring.
--
Tim McConnell
nk, it's because
although dpkg-shlibdeps does do symlink resolution (which is how this
can work), it's only on the last path component and not recursive, and
one of the libX directories for biarch targets will already be a
symlink.) This patch needs a bit of tidying, as it won't
Source: gcc-4.2
Version: 4.2.2-7
Severity: normal
When building a cross compiler targeting Debian-amd64, the executable
prefix is x86_64-linux-gnu, but the alternatives are installed using the
prefix x86-64-linux-gnu, i.e. with a hyphen instead of the underscore.
e.g.:
/usr/bin/x86-64-linux-gnu-g
Package information. ---
Depends (Version) | Installed
===-+-===
cpp (>= 4:4.2.3-4) | 4:4.2.3-4
gcc (>= 4:4.2.3-4) | 4:4.2.3-4
gfortran-4.3 (>= 4.3.0-1) | 4.3.0-2
--
Tim Gershon
University of Warwick
+44 (0) 247
In my particular situation, we have software which *must* be compiled
using gcc-4.7. I'm a little confused by message #20 which seems to imply
that gcc-4.7 could be reinstalled after the upgrade is complete.
Thanks,
Tim Gokcen
Package: gcc-4.9-base
Version: 4.9.2-10
Debian bug 770025 added a "Breaks: gcc-4.7-base (< 4.7.3)" header to
gcc-4.9, because it was found in bug 736607 (which relates to gcc-4.8)
that the package manager would sometimes leave the system with an
older-release version of gcc instead of using th
Actually, I think I've figured it out. It looks like bugs 770025, which
was an extension of bug 736607, were intended to force gcc-4.7 to be
upgraded to the Jessie version. However, these changes were then trumped
by bug 765379 which just straight-up removed gcc-4.7 from Debian Jessie.
https:/
Alternatively, failure to perform this requested optimization could be made a
warning rather than an error.
--
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/c043526c-03da-
Package: gcc-4.7
Version: 4.7.2-5
Severity: normal
Dear Maintainer,
Compiling the following as C++ with -Wall:
unsigned int n;
union U { unsigned int x:8; } u = { n };
results in:
$ gcc-4.7 -Wall -c test.cpp
test.cpp:2:39: warning: narrowing conversion of 'n' from 'unsigned int' to
'unsigned
h -- due to the
_GLIBCXX_USE_CLOCK_REALTIME definition -- accesses the system_clock with
nanosecond duration.
Best,
Tim
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Archi
This also seems to apply to already-compiled binaries, e.g. if I compile the
aforementioned testcase with libstdc++6 version 4.8.0-7, which results in
correct output, and then upgrade libstdc++6 to version 4.8.0-8, re-running the
testcase without recompilation results in faulty output.
So since th
Hi Matthias,
> Please could you name the software where you did see this failure?
I only spotted this regression in my own development code, so it seems
that the impact is limited after all.
Thanks,
Tim
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject
Is there a workaround for this bug, while waiting for gcc <4.8 to get
fixed? Holding libstdc++6 back tends to break stuff.
--
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.o
If you are unable to view the images in this email, please copy and paste the following url into your browser...
http://www.haestad.com/forums/09
debian-gcc@lists.debian.org not part of the Civil Engineering community? Reply
Note that in the gcc subversion repository, the file listed in the
assertion does not exist for the 4.0.2 release tag.
In the 4.0.2 release, GtkImage is in a pure Java file; the jni tree only
has GtkImagePainter.
See:
http://gcc.gnu.org/viewcvs/tags/gcc_4_0_2_release/libjava/jni/gtk-peer/
and
htt
--
tim at buttersideup dot com changed:
What|Removed |Added
CC||tim at buttersideup dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi
21 matches
Mail list logo
