Re: [OctDev] Re: Bug#281994: octave-forge: literal @AWK@ in /usr/bin/mex

[Dan M. <dan...@mc...>]

On Thu, Nov 18, 2004 at 08:38:02PM -0600, Dirk Eddelbuettel wrote:
> On Thu, Nov 18, 2004 at 03:12:53PM +0000, Christophe Rhodes wrote:
> > Package: octave-forge
> > Version: 2004.11.16-1
> > Severity: normal
> > 
> > Hi,
> > 
> > My copy of /usr/bin/mex seems to have a literal @AWK@ left in it --
> > which stops mex from working.  Is it the sign of an autoconf gone wrong?
> > Hand-editing the script to have awk rather than @AWK@ makes it work.
> 
> Thanks for the bug report, which I am passing on to the octave-forge
> hackers. This looks like something we can probably patch rather quickly in
> both the package and upstream cvs.
> 
> Here what my build log shows:
> 
> Processing extra/mex/
> make[3]: Entering directory /tmp/buildd/octave-forge-2004.11.16/extra/mex'
> mkoctfile -DHAVE_OCTAVE_21 -v -c  -o mex.o mex.cc
> /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.63
> -I/usr/include/octave-2.1.63/
> octave -mieee-fp -O2 -DHAVE_OCTAVE_21 mex.cc -o mex.o
> cat mex.in | sed -e "s:@MKOCTFILE@:mkoctfile -DHAVE_OCTAVE_21
> -v:;s:@LIBPATH@:/u
> sr/lib/octave/2.1.63/site/oct/i386-pc-linux-gnu/octave-forge:g;s:@MEXLIB@:mex.o:
> g" \
>         -e 's;@_AWK_@;@AWK@;g' > mex
> chmod a+x mex
> 
> Probably something wrong with configure ...

This looks like the following patch hasn't been applied yet:

--- /dev/null   Mon Oct 18 16:08:42 2004
+++ extra/mex/configure.add     Mon Oct 18 16:26:09 2004
@@ -0,0 +1,3 @@
+
+AC_PROG_AWK
+

That should have been part of the patches in bug #1062239
(http://sourceforge.net/tracker/index.php?func=detail&aid=1062239&group_id=2888&atid=102888)
but that part seems to be missing.  Maybe someone forgot to 'cvs add configure.add'.

-Dan

--