Part of the problem is libgcc:
$ readelf -a /lib/libgcc_s.so.1 | egrep LOAD
LOAD 0x00 0x 0x 0x12024 0x12024 R E 0x1
LOAD 0x012024 0x00022024 0x00022024 0x002d0 0x00664 RWE 0x1
Another part is that -msecure-plt is not the default:
$ echo 'int foo
Package: g77-2.95
Version: 1:2.95.4-27
Severity: normal
Hi,
as Fortran support is disabled on alpha, there should in my understanding
be no need for a g77 alpha package. Indeed, the current package only
contains files in /usr/share/doc.
Please list the supported architectures for g77, don't spec
--
dvdkhlng at gmx dot de changed:
What|Removed |Added
CC||dvdkhlng at gmx dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29226
--
Accepted:
java-gcj-compat-dev_1.0.65-5_i386.deb
to pool/main/j/java-gcj-compat/java-gcj-compat-dev_1.0.65-5_i386.deb
java-gcj-compat-plugin_1.0.65-5_i386.deb
to pool/main/j/java-gcj-compat/java-gcj-compat-plugin_1.0.65-5_i386.deb
java-gcj-compat_1.0.65-5.diff.gz
to pool/main/j/java-gcj-compa
java-gcj-compat_1.0.65-5_i386.changes uploaded successfully to localhost
along with the files:
java-gcj-compat_1.0.65-5.dsc
java-gcj-compat_1.0.65-5.diff.gz
java-gcj-compat-dev_1.0.65-5_i386.deb
java-gcj-compat_1.0.65-5_i386.deb
java-gcj-compat-plugin_1.0.65-5_i386.deb
Greetings,
Your message dated Sat, 30 Sep 2006 05:47:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#388347: fixed in gcc-defaults 1.43
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
Your message dated Sat, 30 Sep 2006 05:47:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389215: fixed in gcc-defaults 1.43
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
Your message dated Sat, 30 Sep 2006 05:47:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390201: fixed in gcc-defaults 1.43
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
Your message dated Sat, 30 Sep 2006 05:47:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#387161: fixed in gcc-defaults 1.43
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
Your message dated Sat, 30 Sep 2006 05:47:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385732: fixed in gcc-defaults 1.43
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
Accepted:
cpp_4.1.1-9_i386.deb
to pool/main/g/gcc-defaults/cpp_4.1.1-9_i386.deb
g++_4.1.1-9_i386.deb
to pool/main/g/gcc-defaults/g++_4.1.1-9_i386.deb
g77_3.4.6-13_i386.deb
to pool/main/g/gcc-defaults/g77_3.4.6-13_i386.deb
gcc-defaults_1.44.dsc
to pool/main/g/gcc-defaults/gcc-defaults_1.44.
There are disparities between your recently accepted upload and the
override file for the following file(s):
gpc-doc_3.4.6-13_i386.deb: package says section is doc, override says devel.
Either the package or the override file is incorrect. If you think
the override is correct and the package wro
There are disparities between your recently accepted upload and the
override file for the following file(s):
gpc-doc_3.4.6-12_i386.deb: package says section is doc, override says devel.
Either the package or the override file is incorrect. If you think
the override is correct and the package wro
Accepted:
cpp_4.1.1-8_i386.deb
to pool/main/g/gcc-defaults/cpp_4.1.1-8_i386.deb
g++_4.1.1-8_i386.deb
to pool/main/g/gcc-defaults/g++_4.1.1-8_i386.deb
g77_3.4.6-12_i386.deb
to pool/main/g/gcc-defaults/g77_3.4.6-12_i386.deb
gcc-defaults_1.43.dsc
to pool/main/g/gcc-defaults/gcc-defaults_1.43.
Your message dated Sat, 30 Sep 2006 14:12:02 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#384123: cpp has broken dependancies
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
Please could you recheck with the current g++ from unstable, and with
gcc-snapshot (from unstable as well).
Thanks, Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Sat, 30 Sep 2006 14:29:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#375725: Segmentfault
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 your responsib
gcc-defaults_1.44_i386.changes uploaded successfully to localhost
along with the files:
gcc-defaults_1.44.dsc
gcc-defaults_1.44.tar.gz
cpp_4.1.1-9_i386.deb
gcc_4.1.1-9_i386.deb
gnat_4.1.1-9_i386.deb
g++_4.1.1-9_i386.deb
gobjc_4.1.1-9_i386.deb
gobjc++_4.1.1-9_i386.deb
g77_3.4.6-13_
gcc-defaults_1.43_i386.changes uploaded successfully to localhost
along with the files:
gcc-defaults_1.43.dsc
gcc-defaults_1.43.tar.gz
cpp_4.1.1-8_i386.deb
gcc_4.1.1-8_i386.deb
gnat_4.1.1-8_i386.deb
g++_4.1.1-8_i386.deb
gobjc_4.1.1-8_i386.deb
gobjc++_4.1.1-8_i386.deb
g77_3.4.6-12_
Your message dated Sat, 30 Sep 2006 14:08:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line gcc-4.1.1 manual pages are now missing!
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 no
Your message dated Sat, 30 Sep 2006 14:10:00 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385010: GCC internal compiler error (seg-fault) whilst
compiling wxWidgets
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been deal
Processing commands for [EMAIL PROTECTED]:
> reassign 390201 g77
Bug#390201: g77-3.4: broken alternative f77.1.gz
Bug reassigned from package `g77-3.4' to `g77'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Processing commands for [EMAIL PROTECTED]:
> reopen 389539
Bug#389539: file conflict with java-gcj-compat-dev
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug reopened, originator not changed.
> thanks
Stopping processing her
Your message dated Sat, 30 Sep 2006 13:47:13 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390177: gcc-4.1: Non-free docs
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 your
Your message dated Sat, 30 Sep 2006 13:45:41 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389225: correction
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 your responsibil
Your message dated Sat, 30 Sep 2006 04:02:30 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385505: fixed in gcc-4.1 4.1.1ds1-15
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 no
Your message dated Sat, 30 Sep 2006 04:02:30 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#386180: fixed in gcc-4.1 4.1.1ds1-15
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 no
Your message dated Sat, 30 Sep 2006 04:02:30 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389468: fixed in gcc-4.1 4.1.1ds1-15
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 no
Your message dated Sat, 30 Sep 2006 04:02:30 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#390042: fixed in gcc-4.1 4.1.1ds1-15
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 no
Your message dated Sat, 30 Sep 2006 04:02:30 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389539: fixed in gcc-4.1 4.1.1ds1-15
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 no
Accepted:
cpp-4.1_4.1.1-15_i386.deb
to pool/main/g/gcc-4.1/cpp-4.1_4.1.1-15_i386.deb
cpp-4.1_4.1.1-15_powerpc.deb
to pool/main/g/gcc-4.1/cpp-4.1_4.1.1-15_powerpc.deb
fastjar_4.1.1-15_i386.deb
to pool/main/g/gcc-4.1/fastjar_4.1.1-15_i386.deb
fastjar_4.1.1-15_powerpc.deb
to pool/main/g/gcc-4
There are disparities between your recently accepted upload and the
override file for the following file(s):
gcc-4.1-base_4.1.1-15_i386.deb: package says section is libs, override says
devel.
gcc-4.1-base_4.1.1-15_powerpc.deb: package says section is libs, override says
devel.
libssp0_4.1.1-15_i
gcc-4.1_4.1.1ds1-15_multi.changes uploaded successfully to localhost
along with the files:
lib64stdc++6_4.1.1-15_i386.deb
gobjc++-4.1_4.1.1-15_powerpc.deb
libstdc++6_4.1.1-15_i386.deb
lib64ssp0_4.1.1-15_i386.deb
libffi4-dev_4.1.1-15_i386.deb
g++-4.1_4.1.1-15_powerpc.deb
lib64mudflap0_
33 matches
Mail list logo
