Processing commands for [EMAIL PROTECTED]:
> reassign 161957 ftp.debian.org
Bug#161957: please remove the gcc-3.1 source package
Bug reassigned from package `gcc-3.1' to `ftp.debian.org'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system adm
Package: gcc-3.2
Version: 3.2.1-0pre3
Hi folks,
According to http://gcc.gnu.org/gcc-3.2/c++-abi.html GCC must
be configured using '--enable-__cxa_atexit' to support the
Common C++ ABI. But 'g++ -v' doesn't list this configuration
flag. Is this correct?
Regards
Harri
reassign 164458 g++-3.2
severity 164458 important
merge 164458 163422
thanks
Harald Dunkel writes:
> Package: gcc-3.2
> Version: 3.2.1-0pre3
>
> Hi folks,
>
> According to http://gcc.gnu.org/gcc-3.2/c++-abi.html GCC must
> be configured using '--enable-__cxa_atexit' to support the
> Common C++ A
Processing commands for [EMAIL PROTECTED]:
> reassign 164458 g++-3.2
Bug#164458: gcc 3.2 correctly configured?
Bug reassigned from package `gcc-3.2' to `g++-3.2'.
> severity 164458 important
Bug#164458: gcc 3.2 correctly configured?
Severity set to `important'.
> merge 164458 163422
Bug#163422:
Jack Howarth writes:
> Matthias,
> You might want to do a test build of gcc-3.2.1 against the new
> bison 1.50-1. I have found that this new bison breaks the binutils
> build. Not sure yet if this is a bison bug or a flaw in the binutils
> build process. Hopefully not that may packages will be
> g++-3.2 -g -Wall -O3 AcceptanceRateBin.o AlarmClock.o BlockedIntervalList.o
> BlockedIntervalListManager.o DP.o DP2CDSClient.o DPComm.o DP_Config.o
> FlowManager.o FlowSchedule.o MFSequence.o RateList.o SO.o SchedulerFig36.o
> TGUIProxy.o TimeReferencePointList.o main.o ../lib/libsassmsg.a
>
Processing commands for [EMAIL PROTECTED]:
> retitle 158371 [fixed in g++-3.2] internal compiler error in expand_end_loop
> with -O
Bug#158371: g++-3.0: internal compiler error in expand_end_loop with -O
Changed Bug title.
> tags 158371+ fixed
Unknown command or malformed arguments to command.
Jack Howarth writes:
> Hi,
>I am not filing a bug on this right now, but you should
> all be aware that any arch that wants to switch to gcc 3.2
> as its default compiler will need to address the following
> issue. The libgcc symbols starting in gcc 3.1 are now .hidden
> which means breakage of
Matthias,
It appears this problem is specific to binutils. Alan Modra has a
fix applied to binutils cvs. While the fix didn't make it into
binutils 2.13.90.0.10, I passed it along to Chris for our deb packages
of 2.13.90.0.10.
Jack
On Saturday 12 October 2002 19:48, Matthias Klose wrote:
> Jack Howarth writes:
> > Hi,
> >I am not filing a bug on this right now, but you should
> > all be aware that any arch that wants to switch to gcc 3.2
> > as its default compiler will need to address the following
> > issue. The libgcc
Matthias,
I'm not sure. I know I was told that hppa was okay. Also from my
conversations with Jakub it appears i386, ia-64, alpha and sparc32
should be fine. So I would suggest we focus on checking the status
of arm, hurd-i386, m68k, mips, mipsel, s390 and sh. I'm not sure
how many of those arch
On Sat, Oct 12, 2002 at 02:58:44PM -0400, Jack Howarth wrote:
>I'm not sure. I know I was told that hppa was okay. Also from my
> conversations with Jakub it appears i386, ia-64, alpha and sparc32
> should be fine. So I would suggest we focus on checking the status
> of arm, hurd-i386, m68k, m
Your message dated Sat, 12 Oct 2002 21:18:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#158581: g++-3.2: problem location header files
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
Bootrapping the gcc-3_2-branch using bison-1.50 is broken. Reverting
back to bison-1.35 works. HEAD does work well using bison-1.50
cd /build/gcc/gcc-3.2-3.2.1ds3/src/gcc && \
if bison -o c-p$$.c c-parse.y; then \
test -f c-p$$.output && mv -f c-p$$.output c-parse.output ; \
mv -f c-p$$.c c-p
On Sat, Oct 12, 2002 at 02:58:44PM -0400, Jack Howarth wrote:
Hi,
>I'm not sure. I know I was told that hppa was okay. Also from my
> conversations with Jakub it appears i386, ia-64, alpha and sparc32
> should be fine. So I would suggest we focus on checking the status
> of arm, hurd-i386, m
> From: Matthias Klose
>
> Bootrapping the gcc-3_2-branch using bison-1.50 is broken. Reverting
> back to bison-1.35 works. HEAD does work well using bison-1.50
>
> cd /build/gcc/gcc-3.2-3.2.1ds3/src/gcc && \
> if bison -o c-p$$.c c-parse.y; then \
> test -f c-p$$.output && mv -f c-p
> From: Matthias Klose
>
> Bootrapping the gcc-3_2-branch using bison-1.50 is broken. Reverting
> back to bison-1.35 works. HEAD does work well using bison-1.50
>
> cd /build/gcc/gcc-3.2-3.2.1ds3/src/gcc && \
> if bison -o c-p$$.c c-parse.y; then \
> test -f c-p$$.output && mv -f c-p
17 matches
Mail list logo
