Stop paying high prices for the meds you need! We can help you save by buying
overseas.
Don't believe me? Check out this link, whats the worst that could happen. You
save some money?
http://www.cotj.com/pharm/tangy/
Yours,
Emily
Egon Willighagen writes:
>
> Package: gij-3.4
> Severity: normal
>
>
> gij-3.4 suggests libgcj-awt5 but not found. Should be libgcj5-awt?
thanks, fixed for the next upload.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> # submitted Debian report #290438 to gcc-gnats as PR 19469
> # http://gcc.gnu.org/PR19469
> forwarded 290438 http://gcc.gnu.org/PR19469
Bug#290438: g77-3.3: produces wrong code on i386 compiling with -fno-automatic
-O1
Noted your statement that Bug has
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-16
16:36 ---
Hmm, this really sounds like PR 323. (I would have them look at that PR and
make sure they try out
-ffloat-store.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19469
--- You are receiving this ma
# submitted Debian report #290438 to gcc-gnats as PR 19469
# http://gcc.gnu.org/PR19469
forwarded 290438 http://gcc.gnu.org/PR19469
retitle 290438 [PR 19469] wrong code on i486 compiling with f77 -fno-automatic
-O1
tags 290438 + upstream
thanks
Please could you subscribe to the upstream report?
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-16
16:39 ---
Also since this depends on a library, we really need a self contained example.
I still think -ffloat-store will "fix" their problem. If it does then it is a
dup of PR 323.
--
What|Removed
--
What|Removed |Added
CC||kmccarty at princeton dot
||edu
http://gcc.gnu.org/bugzilla/sho
On 01/16/2005 11:39 AM, Matthias Klose wrote:
> Please could you subscribe to the upstream report?
Done.
> using the current g77-3.4 from unstable, I cannot reproduce the
> segfault (you should link with g77-3.4 as well).
I still get a segfault with -O1 under g77-3.4, even when linking with
g77
Kevin McCarty writes:
> Package: g77-3.3
> Version: 1:3.3.5-6
> Severity: wishlist
>
> Hi,
>
> Through no fault of my own :-) I have to deal with FORTRAN code that uses
> very large UNIT numbers (up to 750) when opening files. According to
> src/libf2c/libI77/README.netlib, this can be done by i
LAST_UPDATED: Sat Jan 15 17:37:36 UTC 2005
Native configuration is ia64-unknown-linux-gnu
=== g++ tests ===
Running target unix
WARNING: g++.old-deja/g++.mike/p10769a.C compilation failed to produce
executable
XPASS: g++.old-deja/g++.other/init5.C execution test
On Sun, 16 Jan 2005, Matthias Klose wrote:
Looking at the code, it looks safe to increase the size. However you
let the code compile on Debian systems, but it will fail anywhere
else, where MXUNIT has the unchanged value. Did other distributors
raise this value? Is the compilation of the modified l
gcc-4.0_4.0ds3-0pre4_i386.changes uploaded successfully to localhost
along with the files:
gcc-4.0_4.0ds3-0pre4.dsc
gcc-4.0_4.0ds3.orig.tar.gz
gcc-4.0_4.0ds3-0pre4.diff.gz
cpp-4.0-doc_4.0-0pre4_all.deb
libgcj6-common_4.0-0pre4_all.deb
libgcj-common_4.0-0pre4_all.deb
libstdc++6-4.0-doc
There are disparities between your recently accepted upload and the
override file for the following file(s):
fastjar_4.0-0pre4_i386.deb: package says priority is optional, override says
extra.
lib64stdc++6_4.0-0pre4_i386.deb: package says section is base, override says
libs.
libstdc++6_4.0-0pre4
Accepted:
cpp-4.0-doc_4.0-0pre4_all.deb
to pool/main/g/gcc-4.0/cpp-4.0-doc_4.0-0pre4_all.deb
cpp-4.0_4.0-0pre4_i386.deb
to pool/main/g/gcc-4.0/cpp-4.0_4.0-0pre4_i386.deb
fastjar_4.0-0pre4_i386.deb
to pool/main/g/gcc-4.0/fastjar_4.0-0pre4_i386.deb
fixincludes_4.0-0pre4_i386.deb
to pool/main
gcc-4.0_4.0ds3-0pre4_sparc.changes uploaded successfully to localhost
along with the files:
gcc-4.0-base_4.0-0pre4_sparc.deb
libgcc1_4.0-0pre4_sparc.deb
lib64gcc1_4.0-0pre4_sparc.deb
cpp-4.0_4.0-0pre4_sparc.deb
protoize_4.0-0pre4_sparc.deb
fixincludes_4.0-0pre4_sparc.deb
libmudflap0_4
gcc-4.0_4.0ds3-0pre4_ia64.changes uploaded successfully to localhost
along with the files:
gcc-4.0-base_4.0-0pre4_ia64.deb
libgcc1_4.0-0pre4_ia64.deb
cpp-4.0_4.0-0pre4_ia64.deb
protoize_4.0-0pre4_ia64.deb
fixincludes_4.0-0pre4_ia64.deb
libmudflap0_4.0-0pre4_ia64.deb
libmudflap0-dev_4.
Your message dated Mon, 17 Jan 2005 08:05:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-4.0_4.0ds3-0pre4 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Mon, 17 Jan 2005 08:05:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-4.0_4.0ds3-0pre4 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Mon, 17 Jan 2005 08:05:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-4.0_4.0ds3-0pre4 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
gcc-4.0_4.0ds3-0pre4_powerpc.changes uploaded successfully to localhost
along with the files:
gcc-4.0-base_4.0-0pre4_powerpc.deb
libgcc1_4.0-0pre4_powerpc.deb
cpp-4.0_4.0-0pre4_powerpc.deb
protoize_4.0-0pre4_powerpc.deb
fixincludes_4.0-0pre4_powerpc.deb
libmudflap0_4.0-0pre4_powerpc.deb
Accepted:
cpp-4.0_4.0-0pre4_ia64.deb
to pool/main/g/gcc-4.0/cpp-4.0_4.0-0pre4_ia64.deb
fastjar_4.0-0pre4_ia64.deb
to pool/main/g/gcc-4.0/fastjar_4.0-0pre4_ia64.deb
fixincludes_4.0-0pre4_ia64.deb
to pool/main/g/gcc-4.0/fixincludes_4.0-0pre4_ia64.deb
g++-4.0_4.0-0pre4_ia64.deb
to pool/main/g
Accepted:
cpp-4.0_4.0-0pre4_sparc.deb
to pool/main/g/gcc-4.0/cpp-4.0_4.0-0pre4_sparc.deb
fastjar_4.0-0pre4_sparc.deb
to pool/main/g/gcc-4.0/fastjar_4.0-0pre4_sparc.deb
fixincludes_4.0-0pre4_sparc.deb
to pool/main/g/gcc-4.0/fixincludes_4.0-0pre4_sparc.deb
g++-4.0_4.0-0pre4_sparc.deb
to pool
Your message dated Mon, 17 Jan 2005 08:05:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-4.0_4.0ds3-0pre4 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Mon, 17 Jan 2005 08:05:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-4.0_4.0ds3-0pre4 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Mon, 17 Jan 2005 08:05:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-4.0_4.0ds3-0pre4 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Mon, 17 Jan 2005 08:08:21 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#280142: FTBFS (unstable/m68k) ICE during build
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the cas
Your message dated Mon, 17 Jan 2005 08:05:05 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-4.0_4.0ds3-0pre4 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Accepted:
cpp-4.0_4.0-0pre4_powerpc.deb
to pool/main/g/gcc-4.0/cpp-4.0_4.0-0pre4_powerpc.deb
fastjar_4.0-0pre4_powerpc.deb
to pool/main/g/gcc-4.0/fastjar_4.0-0pre4_powerpc.deb
fixincludes_4.0-0pre4_powerpc.deb
to pool/main/g/gcc-4.0/fixincludes_4.0-0pre4_powerpc.deb
g++-4.0_4.0-0pre4_powerpc
28 matches
Mail list logo
