Re: [Pkg-octave-devel] octave-forge_2004.11.16-4 accepted

[Dirk Eddelbuettel]

On 24 February 2005 at 08:43, Rafael Laboissiere wrote:
| [Cc: to maintainers AT octave DOT org]
| 
| * Dirk Eddelbuettel <address@hidden> [2005-02-23 20:15]:
| 
| > On 23 February 2005 at 16:43, Rafael Laboissiere wrote:
| > | An aside note: buildd of octave2.1 on m68k failed after 20h41min with the
| > | usual error message:
| > | 
| > | /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/cchqGuhc.s: Assembler messages:
| > | /tmp/cchqGuhc.s:20898: Error: operands mismatch -- statement `move.b 
%a4,%d1' ignored
| > 
| > I see the -01 -g0 --- for R I actually use -O0 -g0 on m68k. I may be worth a
| > try with -O0 -g0 on m68k.
| 
| >From the i368 build log, the line above is:
| 
| /usr/bin/g++ -c  -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc 
-I.. /glob -I../glob -DHAVE_CONFIG_H -mieee-fp -Wall -W -Wshadow -O2 ls-mat5.cc 
-o pic/ls-mat5.o
| 
| It has "-O2" instead of "-O1 -g0".  I could not find in configure.in where
| these values are specified and how they end up in mkoctfile.  Could any of
| the octave maintainers help us here?

It's Debian specific, and all in debian/rules. A variable "compilerflags" is
set conditionally on the build arch, and then passed to make:

compilerflags   = -O2
[...]

ifneq "$(findstring $(arch), m68k-linux)" ""
[...]
compilerflags   = -O1 -g0
endif

[...]
        $(MAKE)         CFLAGS="$(compilerflags)"               \
[...]


Hth, Dirk

-- 
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