On 26 April 2012 13:00, Mike Miller <[email protected]> wrote:
> I've noticed a fair number of Makefiles that call mkoctfile instead of
> the $(MKOCTFILE) variable, this will not work as intended if compiling
> against an Octave in a non-standard path, right? Is this something
> that should be fixed per-package or across the board? For example,
> I'm working in comm, should I just submit a patch for comm's Makefile
> for now? Thanks.
So all Makefile should use?
ifndef MKOCTFILE
MKOCTFILE := mkoctfile -Wall
endif
Is this correct? I'll guess that almost all packages will need this fix.
Carnë
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev