* Matthias Klose <[EMAIL PROTECTED]> [2006-02-21 02:44]:
> - uploading GCC 4.1 to unstable for those architectures which do not
> have ABI problems (these should be all, but should be validated).
I just checked ARM using the extract-syms.sh script and it looks fine.
--
Martin Michlmayr
http://w
test
This Email has been scanned for all viruses by PAETEC Email Scanning Services,
utilizing MessageLabs proprietary SkyScan infrastructure. For more information
on a proactive anti-virus service working around the clock,
LAST_UPDATED: Obtained from SVN: tags/gcc_4_1_0_release revision 111560
Native configuration is m68k-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/eh/omit-frame-pointer2.C execution test
FAIL: g++.dg/eh/registers1.C execution test
FAIL: g++.dg/ext/visibili
LAST_UPDATED: Obtained from SVN: tags/gcc_4_1_0_release revision 111560
Native configuration is arm-unknown-linux-gnu
=== libffi tests ===
Running target unix
XPASS: libffi.call/closure_fn0.c execution test
XPASS: libffi.call/closure_fn1.c execution test
XPASS: libffi.call/closu
On Thu, Mar 23, 2006 at 04:12:51PM +0100, Matthias Klose wrote:
> hmm, I don't see it as a bug. the nice thing is that you can unpack
> old deb's on other places and just use them.
Not with the path resolution policy I was describing. It starts
out with an absolute path name rooted at /usr and c
On Thu, Mar 23, 2006 at 05:32:37PM +, Martin Michlmayr wrote:
> clone 357122 -1
> reassign -1 gcc-4.1,autoconf
> retitle -1 mips: -fstack-protector generates warning only but then fails to
> link
> thanks
>
> * Martin Michlmayr <[EMAIL PROTECTED]> [2006-03-15 23:27]:
> > | checking whether gc
Accepted:
chill_2.95.4-47_i386.deb
to pool/main/g/gcc-defaults/chill_2.95.4-47_i386.deb
cpp-doc_4.0.3-1_i386.deb
to pool/main/g/gcc-defaults/cpp-doc_4.0.3-1_i386.deb
cpp_4.0.3-1_i386.deb
to pool/main/g/gcc-defaults/cpp_4.0.3-1_i386.deb
g++_4.0.3-1_i386.deb
to pool/main/g/gcc-defaults/g++_4
On Wed, Mar 22, 2006 at 10:15:40PM -0800, Steve Langasek wrote:
> Ok, this is pretty much an unsupported configuration in Debian. Debian
> policy assumes, for instance, that any symlinks within a single top-level
> directory can be made relative symlinks: e.g., /usr/include/X11 ->
> /usr/X11R6/in
gcc-defaults_1.32_i386.changes uploaded successfully to localhost
along with the files:
gcc-defaults_1.32.dsc
gcc-defaults_1.32.tar.gz
cpp_4.0.3-1_i386.deb
cpp-doc_4.0.3-1_i386.deb
gcc_4.0.3-1_i386.deb
gcc-doc_4.0.3-1_i386.deb
g++_4.0.3-1_i386.deb
gobjc_4.0.3-1_i386.deb
g77_3.4.6-
Martin Michlmayr <[EMAIL PROTECTED]> writes:
> reassign 358644 autoconf
> thanks
>
> * Martin Michlmayr <[EMAIL PROTECTED]> [2006-03-23 17:32]:
>> Can someone please comment whether this is a compiler bug (I think
>> so) or whether autoconf needs to be changed.
>
> I talked to Andrew Pinski of GCC
reassign 358644 autoconf
thanks
* Martin Michlmayr <[EMAIL PROTECTED]> [2006-03-23 17:32]:
> Can someone please comment whether this is a compiler bug (I think
> so) or whether autoconf needs to be changed.
I talked to Andrew Pinski of GCC and he told me the behaviour of GCC
4.1 is correct:
19:2
Processing commands for [EMAIL PROTECTED]:
> reassign 358644 autoconf
Bug#358644: mips: -fstack-protector generates warning only but then fails to
link
Bug reassigned from package `gcc-4.1,autoconf' to `autoconf'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Deb
test case and GCC info for the GCC people:
$ cat > test.c
int main() {
}
$ gcc-3.4 -o test -g -O2 -fstack-protector ./test.c
cc1: error: unrecognized command line option "-fstack-protector"
zsh: exit 1 gcc-3.4 -o test -g -O2 -fstack-protector ./test.c
$ gcc-4.0 -o test -g -O2 -fstack-protecto
Hail!
Just one bottle will change your life!
Gain MASSIVE Sexual Chemistry on Demand!
Instantly Arouse, Attract, Excite, Intrigue and Seduce
Gorgeous Women Whenever You Want, Wherever You Want,
As Often As You Want ... Any Time YOU Are In the Mood.
Increase your self-confidence and masculinity
> Pjotr Kourzanov writes:
> > Package: gcc-4.0
> > Version: 4.0.2-9.my
> > Followup-For: Bug #357661
> >
> > --- gcc-4.0-4.0.3/debian/control.m4 2006-03-20 20:07:22.0
> > +0100 +++ gcc-4.0-4.0.3-1/debian/control.m4 2006-03-21
> > 16:33:32.0 +0100 @@ -103,6 +103,8 @@
> > Section: i
Processing commands for [EMAIL PROTECTED]:
> clone 357122 -1
Bug#357122: FTBFS on mips: cannot compute sizeof (char *)
Bug 357122 cloned as bug 358644.
> reassign -1 gcc-4.1,autoconf
Bug#358644: FTBFS on mips: cannot compute sizeof (char *)
Bug reassigned from package `samhain' to `gcc-4.1,autoco
clone 357122 -1
reassign -1 gcc-4.1,autoconf
retitle -1 mips: -fstack-protector generates warning only but then fails to link
thanks
* Martin Michlmayr <[EMAIL PROTECTED]> [2006-03-15 23:27]:
> | checking whether gcc accepts -fstack-protector... no
> ...
> | checking size of char *... 4
> But let'
Steve Langasek writes:
> On Wed, Mar 22, 2006 at 04:10:32PM +0100, Christian E. Boehme wrote:
> > You (as in distributor) can solve that problem with using
> > ``--with-gxx-include-dir=/usr/include/c++/4.0'' during configuration
> > as was done with g++-3.4 or tell the GCC people to change their mi
Pjotr Kourzanov writes:
> Package: gcc-4.0
> Version: 4.0.2-9.my
> Followup-For: Bug #357661
>
> --- gcc-4.0-4.0.3/debian/control.m4 2006-03-20 20:07:22.0 +0100
> +++ gcc-4.0-4.0.3-1/debian/control.m4 2006-03-21 16:33:32.0 +0100
> @@ -103,6 +103,8 @@
> Section: ifdef(`TARGET',`d
Martin Michlmayr writes:
> * Martin Buck <[EMAIL PROTECTED]> [2006-03-20 10:03]:
> > I would have thought that a compiler that miscompiles trivial for loops and
> > thus inserts bugs in lots of programs compiled with it is unsuitable for
> > release, i.e. severity serious.
>
> I don't know... I co
20 matches
Mail list logo
