help-octave
[Top][All Lists]
Advanced

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

Re: octave 2.9.12 cvs and non cvs doesn't compile on ubuntu feisty


From: Riccardo Corradini
Subject: Re: octave 2.9.12 cvs and non cvs doesn't compile on ubuntu feisty
Date: Fri, 15 Jun 2007 19:44:09 +0200 (CEST)

Thanks a lot
Cheers
Riccardo

"John W. Eaton" <address@hidden> ha scritto:
On 15-Jun-2007, David Bateman wrote:

| Riccardo Corradini wrote:
| > I am trying to compile the latest octave on latest ubuntu feisty, but
| > I have this nasty output..
| > make -C interpreter all
| > make[3]: Entering directory
| > `/home/debianuser/Octavepkg/octave/doc/interpreter'
| > DISPLAY= ../../run-octave -f -q -H -p . --eval "sparseimages ('gplot',
| > 'txt'); sleep (1);"
| > mawk: program limit exceeded: sprintf buffer size=1020
| > FILENAME="-" FNR=19 NR=19
| > mawk: program limit exceeded: sprintf buffer size=1020
| > FILENAME="-" FNR=20 NR=20
| > mawk: program limit exceeded: sprintf buffer size=1020
| > FILENAME="-" FNR=20 NR=20
| > error: `fullfile' undefined near line 1 column 19
| > error: evaluating argument list element number 2
| > error: near line 1 of file `/home/debianuser/Octavepkg/octave/src/PKG_ADD'
| > error: source: error sourcing file
| > `/home/debianuser/Octavepkg/octave/src/PKG_ADD'
| >
| > make[3]: *** [gplot.txt] Error 1
| > make[3]: Leaving directory
| > `/home/debianuser/Octavepkg/octave/doc/interpreter'
| > make[2]: *** [interpreter] Error 2
| > make[2]: Leaving directory `/home/debianuser/Octavepkg/octave/doc'
| > make[1]: *** [doc] Error 2
| > make[1]: Leaving directory `/home/debianuser/Octavepkg/octave'
| > make: *** [all] Error 2
| >
| > Is there anybody that may help me?
| > Cheers
| > Riccardo
| >
| > ------------------------------------------------------------------------
| > ------------------------------------------------------------------------
|
| Yes, don't start octave from a directory with a PKG_ADD and a "autoload"
| command included in the PKG_ADD. As the path "." is first on the path
| the PKG_ADD command in ./PKG_ADD will be run before the fullfile
| function is on the path..

I don't see how that helps. Isn't the failure above a failure during
the build? If that's due to running Octave in the wrong directory,
then I think that would be a bug in a Makefile.

The error is coming from mawk, so maybe a workaround is to use gawk
instead of mawk? I had no idea that mawk had a fixed size buffer for
sprintf.

But in any case, maybe we can avoid the buffer size limit. Where is
AWK being used here? Oh, in the run-octave script. Please try the
following patch.

Thanks,

jwe


ChangeLog:

2007-06-15 John W. Eaton

* run-octave.in: Use simple string concatenation instead of
sprintf in AWK program.


Index: run-octave.in
===================================================================
RCS file: /cvs/octave/run-octave.in,v
retrieving revision 1.18
diff -u -u -r1.18 run-octave.in
--- run-octave.in 20 Apr 2007 05:31:41 -0000 1.18
+++ run-octave.in 15 Jun 2007 16:22:43 -0000
@@ -22,10 +22,10 @@
d3_list=$(find "$d3" -type d -a ! \( \( -name CVS -o -name private \) -a -prune \) -exec echo '{}': ';')
d4_list=$(find "$d4" -type d -a ! \( \( -name CVS -o -name private \) -a -prune \) -exec echo '{}': ';')

-d1_path=$(echo "$d1_list" | $AWK '{ s = sprintf ("%s%s", s, $0); } END { sub (/:$/, "", s); print s; }')
-d2_path=$(echo "$d2_list" | $AWK '{ s = sprintf ("%s%s", s, $0); } END { sub (/:$/, "", s); print s; }')
-d3_path=$(echo "$d3_list" | $AWK '{ s = sprintf ("%s%s", s, $0); } END { sub (/:$/, "", s); print s; }')
-d4_path=$(echo "$d4_list" | $AWK '{ s = sprintf ("%s%s", s, $0); } END { sub (/:$/, "", s); print s; }')
+d1_path=$(echo "$d1_list" | $AWK '{ t = (s $0); s = t; } END { sub (/:$/, "", s); print s; }')
+d2_path=$(echo "$d2_list" | $AWK '{ t = (s $0); s = t; } END { sub (/:$/, "", s); print s; }')
+d3_path=$(echo "$d3_list" | $AWK '{ t = (s $0); s = t; } END { sub (/:$/, "", s); print s; }')
+d4_path=$(echo "$d4_list" | $AWK '{ t = (s $0); s = t; } END { sub (/:$/, "", s); print s; }')

LOADPATH="$d1_path:$d2_path:$d3_path:$d4_path"
IMAGEPATH="$top_srcdir/scripts/image"



L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail
reply via email to

[Prev in Thread] Current Thread [Next in Thread]