[ANNOUNCEMENT] Updated: octave-forge-20120714-1

[ANNOUNCEMENT] Updated: octave-forge-20120714-1

[marco atzeri]

New version of

octave-forge-20120714-1

for cygwin is available in the Cygwin distribution:

This release is the bundle of upstream packages
for octave 3.6.x serie

ADVISE
On cygwin none of the package is autoloaded,
as some package could change substantially
the normal octave behaviour (eg "nan").

66 of 89 packages are available, run "pkg list"
from octave to see the full list.

To load any package before usage run
  "pkg load <package_name>"

see "help pkg" for details.

CHANGES
Packages available up to 2012-07-14, built for octave-3.6.x .
In same cases available SVN version were used, where
specific build problem or compatibility with octave-3.6.x
was found.

Upstream decided to split all the package as standalon;
I prefer to maintain the previous bundle structure, as
I can not manage the workload of many small packages.

DESCRIPTION
The octave-forge project contains contributed functions
for GNU Octave which are not in the main distribution.

HOMEPAGE
http://octave.sourceforge.net

Full documentation and FAQ are available at:
http://octave.sourceforge.net/docs.html

Original source of individual packages
http://sourceforge.net/projects/octave/files/Octave%20Forge%20Packages/Individual%20Package%20Releases/

Regards
Marco Atzeri

               *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list,
look at the "List-Unsubscribe: " tag in the email header of this
message. Send email to the address specified there. It will be in the 
format:

cygwin-announce-unsubscribe-you=yourdomain.com@cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that
is available starting at this URL.


--
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

Re: [ANNOUNCEMENT] Updated: octave-forge-20120714-1

[Achim Gratz]

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.


--
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

Re: [ANNOUNCEMENT] Updated: octave-forge-20120714-1

[marco atzeri]

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

Re: [ANNOUNCEMENT] Updated: octave-forge-20120714-1

[Achim Gratz]

marco atzeri <marco.atzeri <at> gmail.com> writes:
> .mex are dll not exe files.
[...]
> I will look on what caused the change, as temporary workaround 
> remove/copy the *.mex.exe to *.mex files.

Thank you for the clarification.  I'll see to prepare a patch to include these
in rebaseall.


Regards,
Achim.





--
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

Re: [ANNOUNCEMENT] Updated: octave-forge-20120714-1

[Yaakov (Cygwin/X)]

On 2012-07-18 03:51, marco atzeri wrote:
> .mex are dll not exe files.

I thought Octave modules were .oct?

> on previous nan-2.5.2, included in octave-forge-20120224-1
> they were correctly identified as .mex
> on  octave-forge-20120714-1, nan are wrong and tsa are right
>
> I will look on what caused the change, as temporary workaround
> remove/copy the *.mex.exe to *.mex files.

That would be my fault. :-(  This should be fixed in cygport git master 
now; sorry for the inconvenience.


Yaakov


--
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

Re: [ANNOUNCEMENT] Updated: octave-forge-20120714-1

[marco atzeri]

On 7/18/2012 1:01 PM, Yaakov (Cygwin/X) wrote:
> On 2012-07-18 03:51, marco atzeri wrote:
>> .mex are dll not exe files.
>
> I thought Octave modules were .oct?

standard yes.

mex are special Matlab compatible ones, in theory they should
work with both Matlab and Octave...


>
>> on previous nan-2.5.2, included in octave-forge-20120224-1
>> they were correctly identified as .mex
>> on  octave-forge-20120714-1, nan are wrong and tsa are right
>>
>> I will look on what caused the change, as temporary workaround
>> remove/copy the *.mex.exe to *.mex files.
>
> That would be my fault. :-(  This should be fixed in cygport git master
> now; sorry for the inconvenience.

I noticed that outside cygport, the problem do not arise.

I am also investigating why tsa mex were not changed, and something is 
clearly wrong in the octave-forge build system

$ file *.mex
covm_mex.mex:       ELF 64-bit LSB shared object, x86-64, version 1 
(SYSV), dynamically linked, 
BuildID[sha1]=0x7b9f63a496a41bb490ebb7d6239da5c7dbb2e130, not stripped
sumskipnan_mex.mex: ELF 64-bit LSB shared object, x86-64, version 1 
(SYSV), dynamically linked, 
BuildID[sha1]=0x38057facd70b6f315b722c6749d6b872d425b619, not stripped

while before
$ file *.mex
covm_mex.mex:       PE32 executable (DLL) (console) Intel 80386, for MS 
Windows
sumskipnan_mex.mex: PE32 executable (DLL) (console) Intel 80386, for MS 
Windows

it seems a upstream package bug....

> Yaakov

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

Re: [ANNOUNCEMENT] Updated: octave-forge-20120714-1

[Corinna Vinschen]

On Jul 18 14:07, marco atzeri wrote:
> On 7/18/2012 1:01 PM, Yaakov (Cygwin/X) wrote:
> >On 2012-07-18 03:51, marco atzeri wrote:
> >>.mex are dll not exe files.
> >
> >I thought Octave modules were .oct?
> 
> standard yes.
> 
> mex are special Matlab compatible ones, in theory they should
> work with both Matlab and Octave...

Just that we specificially changed rebaseall and the autorebase
mechanism to deal with .oct files by default, while .mex files
were not mentioned at all...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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

Re: [ANNOUNCEMENT] Updated: octave-forge-20120714-1

[marco atzeri]

On 7/18/2012 2:19 PM, Corinna Vinschen wrote:
> On Jul 18 14:07, marco atzeri wrote:
>> On 7/18/2012 1:01 PM, Yaakov (Cygwin/X) wrote:
>>> On 2012-07-18 03:51, marco atzeri wrote:
>>>> .mex are dll not exe files.
>>>
>>> I thought Octave modules were .oct?
>>
>> standard yes.
>>
>> mex are special Matlab compatible ones, in theory they should
>> work with both Matlab and Octave...
>
> Just that we specificially changed rebaseall and the autorebase
> mechanism to deal with .oct files by default, while .mex files
> were not mentioned at all...
>
>
> Corinna
>

I never used them and I did not notice few were present in
a octave-forge sub package.
sorry

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