Greetings! My apologies for following up to my own post one last
time, but I wanted to mention that gcl uses volatile variable
declarations to protect information across setjmp/longmp in its
formatting code. Is it possible that hppa is not handling these
declarations properly?
Take care,
Camm M
Package: fastjar
Version: 1:3.1.1-2 or 3.2-0pre3
Severity: grave
Justification: renders package unusable
Fastjar segfaults when trying to create jar archive.
Reverting to version from testing/stable worked.
Invocation:
jar cf ../gjdoc.jar ./Manifest.mf `find . -name \*.class`
gives a bit garbage
James Antill <[EMAIL PROTECTED]> writes:
> Package: gcc
> Version: 2:2.95.4-14
> Severity: normal
[...]
> I've included a C file that should work not matter what value the
> TST_SINGLE_ARG is set to.
This is fixed in gcc 3.
Regards,
Martin
I did hit 'i' for include in reportbug, but I can't see it now so here
it is...
/* BEG: */
#include
#define TST_SINGLE_ARG 0
#if TST_SINGLE_ARG
# define EMAC(x) x EXIT_SUCCESS
#else
# define EMAC(x, y) x EXIT_SUCCESS
#endif
int main(void)
{
#if TST_SINGLE_ARG
return (EMAC(,));
#else
return
Package: gcc
Version: 2:2.95.4-14
Severity: normal
In C you are allowed to have empry arguments to macro function, however
gcc-2.95.* doesn't seem to allow this for macro function with only one
argument.
I've included a C file that should work not matter what value the
TST_SINGLE_ARG is set to.
On Fri, Aug 09, 2002 at 08:38:07PM +0200, Martin v. Loewis wrote:
> > So, should this change be considered to be a bug fix in g++ 3.2, and
> > anything which breaks because of it should be fixed, or is it a
> > problem with g++ 3.2?
>
> It's clearly a bug fix.
Thanks Martin for your help with thi
Accepted:
cpp-3.2-doc_3.2-0pre4_all.deb
to pool/main/g/gcc-3.2/cpp-3.2-doc_3.2-0pre4_all.deb
cpp-3.2_3.2-0pre4_i386.deb
to pool/main/g/gcc-3.2/cpp-3.2_3.2-0pre4_i386.deb
fastjar_3.2-0pre4_i386.deb
to pool/main/g/gcc-3.2/fastjar_3.2-0pre4_i386.deb
fixincludes_3.2-0pre4_i386.deb
to pool/main
There are disparities between your recently accepted upload and the
override file for the following file(s):
libg2c0_3.2-0pre4_i386.deb: section is overridden from libs to devel.
Either the package or the override file is incorrect. If you think
the override is correct and the package wrong plea
Jan-Hendrik Palic <[EMAIL PROTECTED]> writes:
> Hmm ok .. but, I thought we have a binary incompatibility, when the
> glibc is compiled with gcc-3.x? If we upload glibc build with gcc-3.x,
> this will break the whole debian-unstable, no?
The incompatibility is minor, and must be fixed before anyb
9 matches
Mail list logo
