On Mon, Apr 30, 2012 at 3:32 PM, Claudio Freire <klaussfre...@gmail.com> wrote:
> On Mon, Apr 30, 2012 at 3:27 PM, Jordi Gutiérrez Hermoso
> <jord...@octave.org> wrote:
>>
>> Although I know Octave-Forge is more lax about coding standards, I
>> don't think this sort of macro checking is a good idea. Instead, in
>> configure.ac we can do
>>
>>         AC_CHECK_HEADERS([unistd.h])
>
> I proposed the win32 thing since it's what's in use in sockets.
>
> But I can try the autoconf one.

Attached is a version with autoconf, and without the "pcdata" bits. It
builds fine.

Actually, I only used autoconf for parallel. sockets and fl-core both
use simple Makefiles without any autoconf, and setting up the
autostuff for this is a bit much.

Attachment: octave-forge-gcc-errors.patch
Description: Binary data

------------------------------------------------------------------------------
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
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to