[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: gcc internal compiler error on mips with octave-forge



On Tue, Jan 20, 2004 at 07:16:54PM +0000, Martin Michlmayr wrote:
> * Dirk Eddelbuettel <edd@debian.org> [2004-01-20 11:06]:
> > mkoctfile -DHAVE_OCTAVE_21 -v lp.cc
> > /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.52
> > -I/usr/include/octave-2.1.52/octave -O2 -DHAVE_OCTAVE_21 lp.cc -o lp.o
> > lp.cc: In function ctave_value_list Flp(const octave_value_list&, int)':
> > lp.cc:640: internal compiler error: Segmentation fault
> 
> It seems to build here with the same toolchain used in the failed
Interesting. I also note that it used to build before (but IIRC some changes
were applied more recently to this particular file, though I may confuse
this with another file in octave-forge).

If it builds, could you possibly upload the resulting .deb to ftp-master.d.o?

> build.  I'd just give the mips buildd a chance to take a look and
> possibly try another build.

Could do too, though that will happen with the next upload anyway. This
2004.01.18-1 upload is a bit of a test for upstream; if it works there will
be a new version anyway (and we may refrain from re-uploading it if there
are in fact no changes at all).

Dirk

> 152:tbm@denial: ..orge-2004.01.18/main/optim] make
          ^^^^^^
	  
Cool hostname for someone with, if memory serves, an undergrad in psychology :)

Dirk

> mkoctfile -DHAVE_OCTAVE_21 -v lp.cc
> /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.52 -I/usr/include/octave-2.1.52/octave -O2 -DHAVE_OCTAVE_21 lp.cc -o lp.o
> /tmp/ccOcRNbv.s: Assembler messages:
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /tmp/ccOcRNbv.s:43994: Warning: AT used after ".set noat" or macro used after ".set nomacro"
> /usr/bin/g++ -shared -o lp.oct lp.o
> mkoctfile -DHAVE_OCTAVE_21 -v leval.cc
> /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.52 -I/usr/include/octave-2.1.52/octave -O2 -DHAVE_OCTAVE_21 leval.cc -o leval.o
> /usr/bin/g++ -shared -o leval.oct leval.o
> 153:tbm@denial: ..orge-2004.01.18/main/optim]
> 
> ii  binutils               2.14.90.0.7-3          The GNU assembler, linker and binary utilities
> ii  libc6-dev              2.3.2.ds1-10           GNU C Library: Development Libraries and Header Files
> ii  gcc-3.3                3.3.3-0pre1            The GNU C compiler
> ii  g++-3.3                3.3.3-0pre1            The GNU C++ compiler
> ii  libstdc++5             3.3.3-0pre1            The GNU Standard C++ Library v3
> ii  libstdc++5-3.3-dev     3.3.3-0pre1            The GNU Standard C++ Library v3 (development files)
> 
> -- 
> Martin Michlmayr
> tbm@cyrius.com
> 

-- 
The relationship between the computed price and reality is as yet unknown.  
                                             -- From the pac(8) manual page



Reply to: