> On Wed, May 07, 2008 at 12:04:44PM +0200, Matthias Klose wrote:
> > maybe this works for the simple case, but how is it technically
> > possible to keep an alternative in manual state, if you change
> > priority, add or remove slave links?
>
> Neither of these actions cause the manual status to
Processing commands for [EMAIL PROTECTED]:
> tag 465580 + unreproducible
Bug#465580: gcc-4.2: FTBFS: ../../src/gcc/config/i386/crtfastmath.c:96: error:
size of array 'st_space' is too large
There were no tags set.
Tags added: unreproducible
> severity 465580 normal
Bug#465580: gcc-4.2: FTBFS: ..
Your message dated Thu, 8 May 2008 10:08:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: grass FTBS due to gcc seg fault on ARM
has caused the Debian Bug report #472804,
regarding grass FTBS due to gcc seg fault on ARM
to be marked as done.
This means that you claim that the pr
tag 465580 + unreproducible
severity 465580 normal
thanks
looks like this is only reproducible in the grid environment. please
don't remove the `unreproducible' tag without comment again.
Sten Heinze writes:
> I found this bug when I tried to upgrade to lenny, so I tried to reproduce it
> on the
Andreas Jochens writes:
> Hello,
>
> On Sat, Apr 19, 2008 at 03:55:49PM +0200, Ludovic Brenta wrote:
> > As I learned the hard way, it is a bad idea to try to build gnat
> > before gnat-4.3 is available. Therefore I just committed this patch
> > to gcc-defaults. The moment you produce gnat-4.3 f
On Sun, Apr 27, 2008 at 04:17:04PM +0200, Matthias Klose wrote:
> tag 473647 + wontfix
> thanks
>
> - well, how long should a compiler be kept as a legacy compiler?
> - set the package on hold if you upgrade, and the package is kept
>installed (or install it from etch).
> - having libg2c0 o
On Thu, May 08, 2008 at 09:30:26AM +0200, Matthias Klose wrote:
> > On Wed, May 07, 2008 at 12:04:44PM +0200, Matthias Klose wrote:
> > The proper approach is to only remove the alternative in prerm if $1 is
> > "remove" or "deconfigure".
>
> which exactly doesn't work when changes are made.
It w
Hello,
On Thu, May 08, 2008 at 10:12:59AM +0200, Matthias Klose wrote:
> Andreas, planning one more gcc-defaults upload; is it ok for you to
> make gnat-4.3 the default on ppc64 now?
yes, that is ok, thanks.
> Is there some place where to fetch new gcc/binutils/glibc packages,
> the alioth archi
Package: gcc
Version: 4.3.0-4
Im running Debian unstable on FS Pocket Loox 720. And gcc nor 4.3 nor 4.2
version doesn't compile anything:
kotoko720:~# uname -a
Linux kotoko720 2.6.21-hh14-128M #44 PREEMPT Sat Sep 22 20:04:17 CEST 2007
armv5tel GNU/Linux
kotoko720:~# cat test.c
#include
i
On Thu, May 08, 2008 at 09:59:18PM +0400, Jan Trofimov wrote:
> Package: gcc
> Version: 4.3.0-4
>
> Im running Debian unstable on FS Pocket Loox 720. And gcc nor 4.3 nor 4.2
> version doesn't compile anything:
>
> kotoko720:~# uname -a
> Linux kotoko720 2.6.21-hh14-128M #44 PREEMPT Sat Sep 22 20
Package: libffi-dev
Version: 3.0.5-1.0
Severity: critical
Justification: causes serious data loss
Because all the builds (native and bi-/tri-arch) install headers into
/usr/include, /usr/include/ffi.h may wind up failing to correspond to
the actual architecture of interest. In particular, on amd6
> > kotoko720:~# uname -a
> > Linux kotoko720 2.6.21-hh14-128M #44 PREEMPT Sat Sep 22 20:04:17 CEST 2007
> > armv5tel GNU/Linux
>
> This is not a Debian kernel. Does this also happen with other gcc versions and
> other distros? I rather suspect a kernel or hardware problem.
other gcc versions ha
Your message dated Thu, 8 May 2008 22:33:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#480203: gcc doesn't compile anything on arm
has caused the Debian Bug report #480203,
regarding gcc doesn't compile anything on arm
to be marked as done.
This means that you claim that t
Processing commands for [EMAIL PROTECTED]:
> tags 480203 + unreproducible
Bug#480203: gcc doesn't compile anything on arm
There were no tags set.
Tags added: unreproducible
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adm
FYI: The status of the gpc-4.1 source package
in Debian's testing distribution has changed.
Previous version: 2.1-4.1.2-17
Current version: 2.1-4.1.2-22
--
This email is automatically generated; [EMAIL PROTECTED] is responsible.
See http://people.debian.org/~henning/trille/ for more informa
gcc-defaults_1.71_i386.changes uploaded successfully to localhost
along with the files:
gcc-defaults_1.71.dsc
gcc-defaults_1.71.tar.gz
cpp_4.2.3-9_i386.deb
gcc_4.2.3-9_i386.deb
gcc-multilib_4.2.3-9_i386.deb
gnat_4.3.0-6_i386.deb
libgnatvsn-dev_4.3.0-6_i386.deb
libgnatprj-dev_4.3.0-6
Accepted:
cpp_4.2.3-9_i386.deb
to pool/main/g/gcc-defaults/cpp_4.2.3-9_i386.deb
g++-multilib_4.2.3-9_i386.deb
to pool/main/g/gcc-defaults/g++-multilib_4.2.3-9_i386.deb
g++_4.2.3-9_i386.deb
to pool/main/g/gcc-defaults/g++_4.2.3-9_i386.deb
gcc-defaults_1.71.dsc
to pool/main/g/gcc-defaults/gc
Your message dated Thu, 08 May 2008 22:47:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#471818: fixed in gcc-defaults 1.71
has caused the Debian Bug report #471818,
regarding gcj-4.3: dangling symlink /usr/share/man/man1/gc-analyze.1.gz
to be marked as done.
This means that yo
Your message dated Thu, 08 May 2008 22:47:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#469412: fixed in gcc-defaults 1.71
has caused the Debian Bug report #469412,
regarding unexpected success on armel
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 08 May 2008 22:47:04 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#477548: fixed in gcc-defaults 1.71
has caused the Debian Bug report #477548,
regarding gcj: broken symlink jv-scan
to be marked as done.
This means that you claim that the problem has been
20 matches
Mail list logo
