Cyril Brulebois k...@debian.org wrote:
Cyril Brulebois k...@debian.org (08/05/2012):
Hi pkg-phototools guys,
hugin was binNMUd for the exiv2 transition, and FTBFS due to the recent,
insane switch to gcc 4.7; for whatever reason, no bugs were filed up to
now, so here we go.
[...]
A patch is
]] Mark Brown
Attempting to boot systemd on this system by adding init=/bin/systemd to
the end of the kernel command line results in:
- The output of the fsck processes for the disks being displayed
- The screen changes to a higher resolution console mode
but no further output or disk
Andreas Metzler ametz...@downhill.at.eu.org (08/05/2012):
The patch worked for me. For paranoias sake (and in case the gcc-4.7
switch is reverted) I have uploaded to experimental instead of
unstable.
Oh, very nice. I must confess I only tried in my usual work environment,
and didn't try in a
Package: wget
Version: 1.12-2.1
Severity: normal
Tags: upstream patch
*** Please type your report below this line ***
wget fails when a URL contains a file name that is longer than
supported by the local file system, e.g. on ext[2-4]:
% wget google.de?q=`seq 200|tr -d '\n'`
[...]
Cannot write
Su cuenta serásuspendida dentro de78 horas, la falta de
validar sucuenta de correo electrónicopermitirá aesta pena.
Haga clic en elenlace de abajo yrellene el formulario paraactualizar su
cuenta.
http://www.formdesk.com/harrygarrick/acount.php
administrador del sistema
Julien,
I am sorry. I got into a panic state over getting rid of mysql-5.1. In
hindsight I can see that there were betters ways of getting the
attention of the release team. I am trying to do the right thing.
On 08/05/12 10:04, Julien Cristau wrote:
On Tue, May 1, 2012 at 22:52:22 +0100,
Package: gtk3-engines-unico
Version: 1.0.2-1
Followup-For: Bug #671936
Dear Maintainer,
After upgrading the package from 1.0.1-1 to 1.0.2-1, I've the same problem as
above.
Sometimes, controls disappears, and I must hover them to make them appear
(Screenshot#1).
Sometimes, controls are badly
On 08/05/12 at 13:20 -0400, Christopher L Conway wrote:
Lucas,
A new version of this package has been languishing unsponsored on
mentors for two months: http://mentors.debian.net/package/cvc3. Can
you check that the problem persists in that version?
Not easily, sorry.
Lucas
--
To
I've reproduced this bug on a different laptop running wicd. Same wifi
network.
--
see shy jo
signature.asc
Description: Digital signature
user debian-...@lists.debian.org
usertags 671990 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
I think those are defensible although I take the point that the
changelog is misleading. For example we just stripped out a lot of stuff
that used procps and the upstream move to cmake removed a lot of
explicit build dependencies so it was natural to ask whether these are
still required. I
Uhm... by looking at
http://release.debian.org/transitions/html/cogl.html I don't see totem,
which depends on libcogl5.
Cheers,
--
Matteo Settenvini
FSF Associated Member
Email : mat...@member.fsf.org
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS/E d--(-) s+: a- C+++ UL+++
P+ L$
user debian-...@lists.debian.org
usertags 671991 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 671992 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 671993 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
reassign 672130 wnpp
thanks
Somelauw somel...@gmail.com writes:
Subject: RFP: wi_tray -- Tray for wmii
Package: wi_tray
When reporting RFP bugs, please follow the guideline explained here[1],
and report these bugs against the correct pseudo-package: wnpp.
I have reassigned the package there
user debian-...@lists.debian.org
usertags 671994 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 671995 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 671996 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 671999 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
On Tue, May 8, 2012 at 9:46 AM, S. G. debianm...@g-e-u-e-r.de wrote:
I tested again:
Client:
Wheezy
remmina, remmina-plugin-nx 1.0.0-3
libssh-4 0.5.2-1
Server:
Lenny
nxserver 3.5.0-9 (from NoMachine)
openssh-server 1:5.5p1-6+squeeze1
This time everything worked fine!
I do not know
user debian-...@lists.debian.org
usertags 672000 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672001 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672002 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672003 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672004 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672005 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672006 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672007 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672008 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672009 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672012 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672010 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672013 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672014 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672015 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672016 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672017 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672019 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672020 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672022 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672023 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672024 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672025 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672026 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672027 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672029 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672030 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672032 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672033 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672035 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672036 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672031 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672021 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672038 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672039 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672040 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672042 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672043 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672044 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672046 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672045 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672047 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672050 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672051 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672052 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672053 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672054 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672055 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672056 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672058 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672065 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672066 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672067 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672068 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672070 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672071 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672073 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672074 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672077 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672079 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672076 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672080 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672081 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672082 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672083 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672084 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672086 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672087 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672085 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672088 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672089 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672090 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672091 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672093 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672094 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672095 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672098 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672097 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
user debian-...@lists.debian.org
usertags 672099 + ftbfs-gcc-4.7
thanks
The build failure is exposed by building with gcc-4.7/g++-4.7,
which is now the default gcc/g++ on x86 architectures.
Some hints on fixing these issues can be found at
http://gcc.gnu.org/gcc-4.7/porting_to.html
--
To
401 - 500 of 695 matches
Mail list logo
