public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ash Hughes <ash.hues@gmail.com>
To: marco.atzeri@gmail.com, cygwin@cygwin.com
Subject: Octave
Date: Fri, 14 Feb 2014 16:22:00 -0000	[thread overview]
Message-ID: <52FE3619.2020405@gmail.com> (raw)

Hi,

I have recently compiled (with some hopefully ignorable warnings at the
end, although I don't have my Windows machine here to look up which
ones) the octave-forge packages for cygwin x64 and I came across a few
issues. First, I found I had to patch mex.h from octave-devel, as
discussed here:

http://cygwin.com/ml/cygwin/2014-01/msg00120.html

I also had to add a #include <unistd.h> as detailed here:

http://freebsd.1045724.n5.nabble.com/ports-184568-math-octave-forge-fl-core-fix-build-with-gcc47-td5866666.html

Is it worth pushing a small patch to these files, or is Octave 3.8 just
around the corner? It'd be great to see x64 fully supported with
octave-forge packages available - I can probably help provide 3.6
octave-forge binaries too, seeing as I've just built them :)

Finally, fltk doesn't seem to work on x64, I get:

function '__init_fltk__' not found

when I try to switch graphics package.

Thanks,

Ash


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2014-02-14 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 16:22 Ash Hughes [this message]
2014-02-14 17:30 ` Octave Marco Atzeri
2014-02-14 17:40   ` Octave Ash Hughes
2014-02-14 18:35     ` Octave Marco Atzeri
2014-02-16 11:56       ` Octave Marco Atzeri
     [not found] <35074990.680FE527@ucsd.edu>
1998-02-28 23:38 ` Octave Adam Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52FE3619.2020405@gmail.com \
    --to=ash.hues@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).