Package: gcc-3.3
Version: 1:3.3-1
Severity: normal
The package libgcc1 depends of nonexistent lib64gcc1, so it is not
installable.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux drizzt 2.4.20-ck4 #1 sáb mar 22 17:17:18 CET 2003 i686
Locale: [EMAIL PROTECT
bgcj-common suggests no packages.
-- no debconf information
Thanks,
--
Javier.
--
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/BANLkTimbP82ZZWJby2ivXXdNqyN-OnWx=g...@mail.gmail.com
>When coconut fall from tree he can't fasten back.
>A Good Example is the Best Sermon.
Hi boy's,
WHY we are giving away Top Quality Software at ROCK BOTTOM Prices
Get your hands on the leading software products at only a fraction of
the costs! You dont have to spend hundreds, or even thousands o
le = stderr;
ret = errno;
}
return ret;
}
int err_set_output_file(FILE * f)
{
int ret = 0;
if (error_file != stderr)
fclose(error_file);
error_file = f;
if (!error_file) {
error_file = stderr;
ret = errno;
}
return ret;
}
/*
pin - pin and unpin processes in
On 8/1/07, Bastian Blank <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 01, 2007 at 04:16:13PM +0200, Javier Cabezas Rodríguez wrote:
> > void do_pin_processes(int pids[], int n, char pin)
> > {
> > int i;
> > for (i = 0; i < n; i++) {
> > printf("
Estimada
empresa,
Le
presentamos el software profesional para el comercio
electrónico
i
p e r 1
es
la solución mejor para abrir una tienda en
in
Estimada
empresa,
Le
presentamos el software profesional para el comercio
electrónico
i
p e r 1
es
la solución mejor para abrir una tienda en
in
If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the De
If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the De
kages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read
If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the De
If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the Debian P
If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the De
kages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read
If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the De
kages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read
kages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read
kages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the De
If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the Debian P
On Tue, Sep 09, 2003 at 11:55:44PM +0200, Matthias Klose wrote:
> > The description should be written so that it gives the system
> > administrator enough information to decide whether to install the
> > package.
>
> it does.
Agreed, my mistake. I should have reviewed the descripti
kages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the De
kages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read
Package: gcc-3.3
Version: 1:3.3.2-0pre4
Priority: wishlist
Tags: upstream
I would very much like stack/buffer overflow protection such as (StackGuard
[1] or to Stack Smashing Protector [2]) be available in Debian's stock
gcc-3.3 compiler. The people at Immunix are making an effort to integrate
Sta
This patch has been recently announced in bugtraq and might be also
relevant.
Aside from providing these patches at debian/patches, is there any way they
could be applied to the stock gcc-3.3 package? As I understand it, in order
for these to be activated sources need to be compiled with an exp
On Wed, Dec 03, 2003 at 02:03:50PM +0100, Falk Hueffner wrote:
> Javier =?iso-8859-15?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <[EMAIL PROTECTED]>
> writes:
>
> > This patch has been recently announced in bugtraq and might be also
> > relevant.
> >
> > Aside
On Fri, Dec 05, 2003 at 01:45:37PM +1100, Russell Coker wrote:
> On Fri, 5 Dec 2003 13:18, Steve Kemp <[EMAIL PROTECTED]> wrote:
> > On Fri, Dec 05, 2003 at 12:10:44PM +1100, Russell Coker wrote:
> > > Are you using any extra patches to GCC? Or just a GCC built with the
> > > propolice option?
> >
anagers directly in order to do tests with newer
gcc-3.3 versions
Thanks
Javier
27 matches
Mail list logo
