From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: octave-forge-20120714-1
Date: Wed, 18 Jul 2012 08:52:00 -0000 [thread overview]
Message-ID: <50067917.9090603@gmail.com> (raw)
In-Reply-To: <loom.20120718T100052-599@post.gmane.org>
On 7/18/2012 10:04 AM, Achim Gratz wrote:
> marco atzeri <marco.atzeri <at> gmail.com> writes:
>> octave-forge-20120714-1
>
> In the directory
>
> /usr/lib/octave/packages/nan-2.5.5/i686-pc-cygwin-api-v48+/
>
> several *.mex.exe files have been installed. Apparently, these are actually
> DLL, not EXE files (at least that's what file and peflags claim they are) - and
> follwing the handling of .oct files, should they not just be called .mex (and
> added to rebaseall accordingly)?
>
>
> Regards,
> Achim.
>
>
.mex are dll not exe files.
on previous nan-2.5.2, included in octave-forge-20120224-1
they were correctly identified as .mex
packages/nan-2.5.2/i686-pc-cygwin-api-v48+/covm_mex.mex
packages/nan-2.5.2/i686-pc-cygwin-api-v48+/histo_mex.mex
packages/nan-2.5.2/i686-pc-cygwin-api-v48+/kth_element.mex
packages/nan-2.5.2/i686-pc-cygwin-api-v48+/str2array.mex
packages/nan-2.5.2/i686-pc-cygwin-api-v48+/sumskipnan_mex.mex
packages/nan-2.5.2/i686-pc-cygwin-api-v48+/svmpredict_mex.mex
packages/nan-2.5.2/i686-pc-cygwin-api-v48+/svmtrain_mex.mex
packages/nan-2.5.2/i686-pc-cygwin-api-v48+/train.mex
packages/nan-2.5.2/i686-pc-cygwin-api-v48+/xptopen.mex
packages/tsa-4.2.2/i686-pc-cygwin-api-v48+/covm_mex.mex
packages/tsa-4.2.2/i686-pc-cygwin-api-v48+/sumskipnan_mex.mex
on octave-forge-20120714-1, nan are wrong and tsa are right
packages/nan-2.5.5/i686-pc-cygwin-api-v48+/histo_mex.mex.exe
packages/nan-2.5.5/i686-pc-cygwin-api-v48+/kth_element.mex.exe
packages/nan-2.5.5/i686-pc-cygwin-api-v48+/str2array.mex.exe
packages/nan-2.5.5/i686-pc-cygwin-api-v48+/sumskipnan_mex.mex.exe
packages/nan-2.5.5/i686-pc-cygwin-api-v48+/svmpredict_mex.mex.exe
packages/nan-2.5.5/i686-pc-cygwin-api-v48+/svmtrain_mex.mex.exe
packages/nan-2.5.5/i686-pc-cygwin-api-v48+/train.mex.exe
packages/nan-2.5.5/i686-pc-cygwin-api-v48+/xptopen.mex.exe
packages/tsa-4.2.4/i686-pc-cygwin-api-v48+/covm_mex.mex
packages/tsa-4.2.4/i686-pc-cygwin-api-v48+/sumskipnan_mex.mex
I will look on what caused the change, as temporary workaround
remove/copy the *.mex.exe to *.mex files.
Regards
Marco
--
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
next prev parent reply other threads:[~2012-07-18 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 12:16 marco atzeri
2012-07-18 8:05 ` Achim Gratz
2012-07-18 8:52 ` marco atzeri [this message]
2012-07-18 11:00 ` Achim Gratz
2012-07-18 11:01 ` Yaakov (Cygwin/X)
2012-07-18 12:08 ` marco atzeri
2012-07-18 12:20 ` Corinna Vinschen
2012-07-18 12:24 ` marco atzeri
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=50067917.9090603@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.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).