[Pkg-octave-devel] Re: octave2.1
Sun, 30 Jan 2005 08:42:44 -0600
On 30 January 2005 at 15:21, Christian T. Steigies wrote:
| On Sun, Jan 30, 2005 at 07:50:16AM -0600, Dirk Eddelbuettel wrote:
| > On 30 January 2005 at 14:24, Christian T. Steigies wrote:
| > | Moin Dirk,
| > | octave2.1 hat ein Problem auf meinem Amiga:
| > |
| > | /usr/bin/g++ -c -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc -I../glob -I../glob -DHAVE_CONFIG_H -Wall -W -Wshadow -O1 -g0 ls-mat5.cc -o pic/ls-mat5.o
| > | /tmp/cc6bz4xl.s: Assembler messages:
| > | /tmp/cc6bz4xl.s:20898: Error: operands mismatch -- statement `move.b %a4,%d1' ignored
| > | make: *** [pic/ls-mat5.o] Error 1
| > |
| > | Gabs doch vorher nicht? Hat sich da irgendwas im code geaendert oder liegt
| > | das evtl an nem neuen g++?
| > Don't know.
| > There hasn't been a code update in the octave2.1 package in weeks (as the
| > changes stayed in the upstream CVS archive). So I'd suspect that one of our
| > beloved irrelevant architectures has problems with the toolchain.
| > I'll CC the newly created octave group on alioth who is now the maintainer.
| Oh, you got rid of it already? So I guess I'll have to translate. octave2.1
| fails to build on m68k, and I thought it did not have any problems before,
| but I was wrong. It also fails on ia64, actually before this point I think,
| and on mips with a different problem, so there is not one but three
Yes, Rafael has already followed up on that with the teams for the respective
architectures. Not sure if we heard anything back yet, though.
| doorstop arches that have a problem with octave2.1. Last time it built on
| m68k it used slightly different libc and gcc versions, do we have a
Better to have an approximate answer to the right question than a precise
answer to the wrong question. -- John Tukey as quoted by John Chambers