Octave Forge

Ólafur Jens Sigurðsson wrote:
> 
> Hey .. it seems that the fixed package fails to build on debian with
> the following error messages:
> 

I believe its fixed in the SVN. This was a failed attempt for a fix for the
cygwin/mingw platform that had other consequences..

D.

-- 
View this message in context: http://www.nabble.com/fixed-fails-to-build-on-linux-tp16220071p16220301.html
Sent from the octave-dev mailing list archive at Nabble.com.

* dbateman <dbateman@...> [2008-03-22 05:49]:

> Ólafur Jens Sigurðsson wrote:
> > 
> > Hey .. it seems that the fixed package fails to build on debian with
> > the following error messages:
> > 
> 
> I believe its fixed in the SVN. This was a failed attempt for a fix for the
> cygwin/mingw platform that had other consequences..

It is only partially fixed in SVN.  Build of fixed.oct still fails because
it tries to link against -L. -loctave_fixed, but no liboctave_fixed.so was
built (this is because LIBEXT = dll).  The first patch attached below
(extlib-so.diff) fixes this.
 
However, build still fails because liboctave_fixed.so is not really a shared
library.  The second patch fixes this (link-shared-lib.diff, dunno whether
it is portable to non-Linux OS'es).

It still does not work, because liboctave_fixed.so is not installed into
/usr/lib/octave/3.0.0/.  I am doing this by hand in the Debian package.

I am having trouble to install this package using the version of pkg.m
currently on tip of the hg repository.  This version allows installing from
the unpacked directory (not from the tarball).  The problems are caused by
the presence of PKG_ADD at the top dir.  When I issue "pkg install .",
octave complains with:

    error: `fullfile' undefined near line 1 column 22

If I add the following to the top of PKG_ADD:

    addpath (genpath ("/usr/lib/octave/3.0.0/oct"), "-begin");
    addpath (genpath ("/usr/share/octave/3.0.0/m"), "-begin");

then the error disappears but I get:

    warning: autoload: `./fixed.oct' is not an absolute file name

Is there a way to get around these problems?    

Finally, it would be great to remove Makeconf, config.log, and config.status
from the tarball, at least in a *clean rule in src/Makefile.  The third
patch attached below does this (mister-proper.diff).

-- 
Rafael

Rafael Laboissiere wrote:
> * dbateman <dbateman@...> [2008-03-22 05:49]:
>
>   
>> Ólafur Jens Sigurðsson wrote:
>>     
>>> Hey .. it seems that the fixed package fails to build on debian with
>>> the following error messages:
>>>
>>>       
>> I believe its fixed in the SVN. This was a failed attempt for a fix for the
>> cygwin/mingw platform that had other consequences..
>>     
>
> It is only partially fixed in SVN.  Build of fixed.oct still fails because
> it tries to link against -L. -loctave_fixed, but no liboctave_fixed.so was
> built (this is because LIBEXT = dll).  The first patch attached below
> (extlib-so.diff) fixes this.
>  
> However, build still fails because liboctave_fixed.so is not really a shared
> library.  The second patch fixes this (link-shared-lib.diff, dunno whether
> it is portable to non-Linux OS'es).
>
> It still does not work, because liboctave_fixed.so is not installed into
> /usr/lib/octave/3.0.0/.  I am doing this by hand in the Debian package.
>
> I am having trouble to install this package using the version of pkg.m
> currently on tip of the hg repository.  This version allows installing from
> the unpacked directory (not from the tarball).  The problems are caused by
> the presence of PKG_ADD at the top dir.  When I issue "pkg install .",
> octave complains with:
>
>     error: `fullfile' undefined near line 1 column 22
>
> If I add the following to the top of PKG_ADD:
>
>     addpath (genpath ("/usr/lib/octave/3.0.0/oct"), "-begin");
>     addpath (genpath ("/usr/share/octave/3.0.0/m"), "-begin");
>
> then the error disappears but I get:
>
>     warning: autoload: `./fixed.oct' is not an absolute file name
>
> Is there a way to get around these problems?    
>
> Finally, it would be great to remove Makeconf, config.log, and config.status
> from the tarball, at least in a *clean rule in src/Makefile.  The third
> patch attached below does this (mister-proper.diff).
>
>   
I'm tempted to give up on this method of creating an external library of
the fixed package and linking the oct-files to it.. I did this to all
windows platforms to access the symbols of the fixed package and allow
the use of the fixed type within other oct-files on windows.. This is
not needed for linux, or MacOS.

I'll take a look at it and see what I can do..

D.


-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

Hello

Please see the long discussions about the fixed package.

http://www.nabble.com/Creating-library-file-in-fixed-package-for-mingw-to14562936.html#a14562936

In the discussion Michael wrote,
My modidication of mingw/cygwin is based on the following Michael's advise.
The following the 3rd option cannot be applied to the linux. 

Regards

Tatsuro


On 1/1/08, Tatsuro MATSUOKA <tmacchant@...> wrote:
> Thank you Michael.
>
> The mingw gcc is the same as the cygwin gcc from the point of view of making ****.dll.
> For the mingw, I should do the same as those for the cygwin.
> I will consider the modification of src/Makefile.

The problem with the dll approach (whether it's cygwin, mingw or
MSVC) is that it does not integrate well with the package manager.
To be usable, the dll must be installed in a location where the
Win32 system can find it, in order to load the oct-file correctly
(the fixed oct file will be linked against the dll). Putting the dll in
the same directory of the oct file is not enough, it should be
installed in a location available from PATH. To solve this problem,
several solutions can be considered:
1) the package manager installs the DLL into a location that is
part of PATH, for instance the octave bin directory; this is not
currently supported by the package manager
2) install the DLL in the same directory of the oct file, and make
octave dynamic loader add that directory to PATH before trying
to load the oct-file
3) do not use a DLL; use a static library and link the oct file
against it

After some discussion (a few months ago), I chose the 3rd option,
as it could be implemented locally in the fixed package. Moreover,
by making the oct-file export the same symbols as the DLL, I could
completely remove the need for a DLL (as any code that needs to
be linked against the DLL can be linked against the oct-file instead).

Michael. 


--- Rafael Laboissiere <rafael@...> wrote:

> * dbateman <dbateman@...> [2008-03-22 05:49]:
> 
> > 宵ムlafur Jens Sigur娼テsson wrote:
> > > 
> > > Hey .. it seems that the fixed package fails to build on debian with
> > > the following error messages:
> > > 
> > 
> > I believe its fixed in the SVN. This was a failed attempt for a fix for the
> > cygwin/mingw platform that had other consequences..
> 
> It is only partially fixed in SVN.  Build of fixed.oct still fails because
> it tries to link against -L. -loctave_fixed, but no liboctave_fixed.so was
> built (this is because LIBEXT = dll).  The first patch attached below
> (extlib-so.diff) fixes this.
>  
> However, build still fails because liboctave_fixed.so is not really a shared
> library.  The second patch fixes this (link-shared-lib.diff, dunno whether
> it is portable to non-Linux OS'es).
> 
> It still does not work, because liboctave_fixed.so is not installed into
> /usr/lib/octave/3.0.0/.  I am doing this by hand in the Debian package.
> 
> I am having trouble to install this package using the version of pkg.m
> currently on tip of the hg repository.  This version allows installing from
> the unpacked directory (not from the tarball).  The problems are caused by
> the presence of PKG_ADD at the top dir.  When I issue "pkg install .",
> octave complains with:
> 
>     error: `fullfile' undefined near line 1 column 22
> 
> If I add the following to the top of PKG_ADD:
> 
>     addpath (genpath ("/usr/lib/octave/3.0.0/oct"), "-begin");
>     addpath (genpath ("/usr/share/octave/3.0.0/m"), "-begin");
> 
> then the error disappears but I get:
> 
>     warning: autoload: `./fixed.oct' is not an absolute file name
> 
> Is there a way to get around these problems?    
> 
> Finally, it would be great to remove Makeconf, config.log, and config.status
> from the tarball, at least in a *clean rule in src/Makefile.  The third
> patch attached below does this (mister-proper.diff).
> 
> -- 
> Rafael
> > -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace>
_______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar
http://pr.mail.yahoo.co.jp/toolbar/

Tatsuro MATSUOKA wrote:
> Hello
>
> Please see the long discussions about the fixed package.
>
> http://www.nabble.com/Creating-library-file-in-fixed-package-for-mingw-to14562936.html#a14562936
>
> In the discussion Michael wrote,
> My modidication of mingw/cygwin is based on the following Michael's advise.
> The following the 3rd option cannot be applied to the linux. 
>   

It doesn't have to be.. Under Linux the symbols are exported from the
oct-file and you can resolve teh symbols at run-time from the oct-file
itself.. Therefore there is no need for an external library file under
linux, or MacOS..

Regards
David

-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

Hello David 

Thanks for your explanation.

Regards

Tatsuro

--- David Bateman <David.Bateman@...> wrote:

> Tatsuro MATSUOKA wrote:
> > Hello
> >
> > Please see the long discussions about the fixed package.
> >
> >
> http://www.nabble.com/Creating-library-file-in-fixed-package-for-mingw-to14562936.html#a14562936
> >
> > In the discussion Michael wrote,
> > My modidication of mingw/cygwin is based on the following Michael's advise.
> > The following the 3rd option cannot be applied to the linux. 
> >   
> 
> It doesn't have to be.. Under Linux the symbols are exported from the
> oct-file and you can resolve teh symbols at run-time from the oct-file
> itself.. Therefore there is no need for an external library file under
> linux, or MacOS..
> 
> Regards
> David
> 
> -- 
> David Bateman                                David.Bateman@...
> Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
> Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
> 91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 
> 
> The information contained in this communication has been classified as: 
> 
> [x] General Business Information 
> [ ] Motorola Internal Use Only 
> [ ] Motorola Confidential Proprietary
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar
http://pr.mail.yahoo.co.jp/toolbar/

On Thu, Mar 27, 2008 at 11:32 AM, David Bateman
<David.Bateman@...> wrote:
>  It doesn't have to be.. Under Linux the symbols are exported from the
>  oct-file and you can resolve teh symbols at run-time from the oct-file
>  itself.. Therefore there is no need for an external library file under
>  linux, or MacOS..

The way I compile the fixed package, it's the same under Windows.

Michael.

Michael Goffioul wrote:
> On Thu, Mar 27, 2008 at 11:32 AM, David Bateman
> <David.Bateman@...> wrote:
>   
>>  It doesn't have to be.. Under Linux the symbols are exported from the
>>  oct-file and you can resolve the symbols at run-time from the oct-file
>>  itself.. Therefore there is no need for an external library file under
>>  linux, or MacOS..
>>     
>
> The way I compile the fixed package, it's the same under Windows.
>
>   
Yes, but that breaks the use of the fixed type in other oct-files.. See
the examples directory in the fixed package.. I don't really understand
Windows builds.. Might it be possible to flag the OCTAVE_API macro in
the fixed type and build under cygwin, mingw and MSVC linking against
the oct-file rather than an external DLL. If that is the case, I'd say
we get rid of the DLL complete and do it that way.

Unfortunately I don't have a build platform for Octave under windows and
can't really test this idea.

D.

-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

On Thu, Mar 27, 2008 at 12:06 PM, David Bateman
<David.Bateman@...> wrote:
>  Yes, but that breaks the use of the fixed type in other oct-files.. See
>  the examples directory in the fixed package.. I don't really understand
>  Windows builds.. Might it be possible to flag the OCTAVE_API macro in
>  the fixed type and build under cygwin, mingw and MSVC linking against
>  the oct-file rather than an external DLL. If that is the case, I'd say
>  we get rid of the DLL complete and do it that way.

Maybe I miss something, because this is already what the MSVC build does
(or at least it used to be like that; I made it like that...). The MSVC build do
not use a separate DLL anymore. Everything is built into the oct-file, but I
use the OCTAVE_FIXED_API macro to export the main symbols from the
oct-file. The oct-files in the examples directory are then simply linked
against the main oct-file.

Michael.

Michael Goffioul wrote:
> On Thu, Mar 27, 2008 at 12:06 PM, David Bateman
> <David.Bateman@...> wrote:
>   
>>  Yes, but that breaks the use of the fixed type in other oct-files.. See
>>  the examples directory in the fixed package.. I don't really understand
>>  Windows builds.. Might it be possible to flag the OCTAVE_API macro in
>>  the fixed type and build under cygwin, mingw and MSVC linking against
>>  the oct-file rather than an external DLL. If that is the case, I'd say
>>  we get rid of the DLL complete and do it that way.
>>     
>
> Maybe I miss something, because this is already what the MSVC build does
> (or at least it used to be like that; I made it like that...). The MSVC build do
> not use a separate DLL anymore. Everything is built into the oct-file, but I
> use the OCTAVE_FIXED_API macro to export the main symbols from the
> oct-file. The oct-files in the examples directory are then simply linked
> against the main oct-file.
>
> Michael.
>
>   
Yes, but can we do the same with cygwin and mingw?

D.

-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

Michael Goffioul wrote:
> On Thu, Mar 27, 2008 at 12:06 PM, David Bateman
> <David.Bateman@...> wrote:
>   
>>  Yes, but that breaks the use of the fixed type in other oct-files.. See
>>  the examples directory in the fixed package.. I don't really understand
>>  Windows builds.. Might it be possible to flag the OCTAVE_API macro in
>>  the fixed type and build under cygwin, mingw and MSVC linking against
>>  the oct-file rather than an external DLL. If that is the case, I'd say
>>  we get rid of the DLL complete and do it that way.
>>     
>
> Maybe I miss something, because this is already what the MSVC build does
> (or at least it used to be like that; I made it like that...). The MSVC build do
> not use a separate DLL anymore. Everything is built into the oct-file, but I
> use the OCTAVE_FIXED_API macro to export the main symbols from the
> oct-file. The oct-files in the examples directory are then simply linked
> against the main oct-file.
>
> Michael.
>
>   
If we can do the same under mingw, cygwin and msvc, then I'd suggest the
attached patch.. Tatsuro, could you check to see if you can do the
following in a freshly checked out octave-forge SVN with this patch applied

cd main/fixed/src
./autogen.sh
./configure
make
cd ../examples
make
octave
addpath ("../src")
a = ffft(fixed(6,4,32*randn(64,1)))

If you can then this patch is find with cygwin/mingw..

D.

-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

On Thu, Mar 27, 2008 at 12:27 PM, David Bateman
<David.Bateman@...> wrote:
>  Yes, but can we do the same with cygwin and mingw?

I guess you can. oct-files are just DLL's, whether you compile with MSVC,
mingw or cygwin. Moreover, mingw and cygwin export all symbols by
default, so the OCTAVE_FIXED_API macro would even not be needed.

Michael.

Michael Goffioul wrote:
> On Thu, Mar 27, 2008 at 12:27 PM, David Bateman
> <David.Bateman@...> wrote:
>   
>>  Yes, but can we do the same with cygwin and mingw?
>>     
>
> I guess you can. oct-files are just DLL's, whether you compile with MSVC,
> mingw or cygwin. Moreover, mingw and cygwin export all symbols by
> default, so the OCTAVE_FIXED_API macro would even not be needed.
>
> Michael.
>   

The problem I had with cygwin is that at the time the example oct-files
were build it wanted the symbols to be resolved, and thus linked against
fixed.oct..... If the OCTAVE_FIXED_API macro doesn't address that issue
then I don't think my fix with work on the cygwin platform and probably
not the mingw platform either. It should work on MSVC as this is
essentially what you were doing with your previous patches...

How can we force the link of the oct-file to not attempt to resolve the
symbols for the fixed type during the link, but rather at run time?

D.

-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

On Thu, Mar 27, 2008 at 12:54 PM, David Bateman
<David.Bateman@...> wrote:
>  The problem I had with cygwin is that at the time the example oct-files
>  were build it wanted the symbols to be resolved, and thus linked against
>  fixed.oct..... If the OCTAVE_FIXED_API macro doesn't address that issue
>  then I don't think my fix with work on the cygwin platform and probably
>  not the mingw platform either. It should work on MSVC as this is
>  essentially what you were doing with your previous patches...
>
>  How can we force the link of the oct-file to not attempt to resolve the
>  symbols for the fixed type during the link, but rather at run time?

You can't. What I did with MSVC is to add "-lfixed" flag when linking
the oct-files from the examples directory. AFAIK, in Win32, whatever
you do, all symbols must be resolved at link-time.

Michael.

Michael Goffioul wrote:
> On Thu, Mar 27, 2008 at 12:54 PM, David Bateman
> <David.Bateman@...> wrote:
>   
>>  The problem I had with cygwin is that at the time the example oct-files
>>  were build it wanted the symbols to be resolved, and thus linked against
>>  fixed.oct..... If the OCTAVE_FIXED_API macro doesn't address that issue
>>  then I don't think my fix with work on the cygwin platform and probably
>>  not the mingw platform either. It should work on MSVC as this is
>>  essentially what you were doing with your previous patches...
>>
>>  How can we force the link of the oct-file to not attempt to resolve the
>>  symbols for the fixed type during the link, but rather at run time?
>>     
>
> You can't. What I did with MSVC is to add "-lfixed" flag when linking
> the oct-files from the examples directory. AFAIK, in Win32, whatever
> you do, all symbols must be resolved at link-time.
>   

Ok, then if you can link against the oct-file, then that doesn't change
anything except the need to add "-L../src -lfixed" when building the
example oct-files.. I committed another patch to do that.. Tatsuro,
you'll need to update your SVN before trying

cd main/fixed/src
./autogen.sh
./configure
make
cd ../examples
make
octave
addpath ("../src")
a = ffft(fixed(6,4,32*randn(64,1)))


to see if this works for cygwin/mingw

Regards
David

-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

On Thu, Mar 27, 2008 at 2:26 PM, David Bateman
<David.Bateman@...> wrote:
>  Ok, then if you can link against the oct-file, then that doesn't change
>  anything except the need to add "-L../src -lfixed" when building the
>  example oct-files.. I committed another patch to do that.. Tatsuro,
>  you'll need to update your SVN before trying
>
>  cd main/fixed/src
>  ./autogen.sh
>  ./configure
>  make
>  cd ../examples
>  make
>  octave
>  addpath ("../src")
>  a = ffft(fixed(6,4,32*randn(64,1)))

There is still one catch at run-time: as ffft.oct is linked against fixed.oct,
fixed.oct must be available for loading by the system when ffft.oct is
loaded. That is
1) either fixed.oct is already loaded
2) or fixed.oct is located in a place where the dynamic linker can find it

Case 2 is of course not true; hence fixed.oct must be loaded by octave
before trying to load ffft.oct. I'm not sure the example code above will
do it, so it might not work. If it doesn't, just type "fixed" at octave prompt
(to force loading of fixed.oct) and it should work OK.

Michael.

Michael Goffioul wrote:
> On Thu, Mar 27, 2008 at 2:26 PM, David Bateman
> <David.Bateman@...> wrote:
>   
>>  Ok, then if you can link against the oct-file, then that doesn't change
>>  anything except the need to add "-L../src -lfixed" when building the
>>  example oct-files.. I committed another patch to do that.. Tatsuro,
>>  you'll need to update your SVN before trying
>>
>>  cd main/fixed/src
>>  ./autogen.sh
>>  ./configure
>>  make
>>  cd ../examples
>>  make
>>  octave
>>  addpath ("../src")
>>  a = ffft(fixed(6,4,32*randn(64,1)))
>>     
>
> There is still one catch at run-time: as ffft.oct is linked against fixed.oct,
> fixed.oct must be available for loading by the system when ffft.oct is
> loaded. That is
> 1) either fixed.oct is already loaded
> 2) or fixed.oct is located in a place where the dynamic linker can find it
>
> Case 2 is of course not true; hence fixed.oct must be loaded by octave
> before trying to load ffft.oct. I'm not sure the example code above will
> do it, so it might not work. If it doesn't, just type "fixed" at octave prompt
> (to force loading of fixed.oct) and it should work OK.
>
>   
The same is true for Linux.. You have to call the fixed command before
ffft in Octave. As you need to create a fixed object with the fixed
command prior to using ffft in any case, this doesn't seem to be an
issue to me.

D.



-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

Hello

Although I vote this issuse here again, I cannot have an enough time to contribute it 
at the moment.  I have an immediate work on my university activity.  
Thefore I cannot committe the isusse at the moment.
Please give a moment to try to build and test what David have advised.

Are there any other persons who have volantary minds in downloading of my cygwin octave with
the development enviroments ?

Otherwise please give me a time to try to come back to discuss the  matter.

Thank you in advance for your warm minds for my delay on this matter.

Regards

Tatsuro



--- David Bateman <David.Bateman@...> wrote:

> Michael Goffioul wrote:
> > On Thu, Mar 27, 2008 at 2:26 PM, David Bateman
> > <David.Bateman@...> wrote:
> >   
> >>  Ok, then if you can link against the oct-file, then that doesn't change
> >>  anything except the need to add "-L../src -lfixed" when building the
> >>  example oct-files.. I committed another patch to do that.. Tatsuro,
> >>  you'll need to update your SVN before trying
> >>
> >>  cd main/fixed/src
> >>  ./autogen.sh
> >>  ./configure
> >>  make
> >>  cd ../examples
> >>  make
> >>  octave
> >>  addpath ("../src")
> >>  a = ffft(fixed(6,4,32*randn(64,1)))
> >>     
> >
> > There is still one catch at run-time: as ffft.oct is linked against fixed.oct,
> > fixed.oct must be available for loading by the system when ffft.oct is
> > loaded. That is
> > 1) either fixed.oct is already loaded
> > 2) or fixed.oct is located in a place where the dynamic linker can find it
> >
> > Case 2 is of course not true; hence fixed.oct must be loaded by octave
> > before trying to load ffft.oct. I'm not sure the example code above will
> > do it, so it might not work. If it doesn't, just type "fixed" at octave prompt
> > (to force loading of fixed.oct) and it should work OK.
> >
> >   
> The same is true for Linux.. You have to call the fixed command before
> ffft in Octave. As you need to create a fixed object with the fixed
> command prior to using ffft in any case, this doesn't seem to be an
> issue to me.
> 
> D.
> 
> 
> 
> -- 
> David Bateman                                David.Bateman@...
> Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
> Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
> 91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 
> 
> The information contained in this communication has been classified as: 
> 
> [x] General Business Information 
> [ ] Motorola Internal Use Only 
> [ ] Motorola Confidential Proprietary
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar
http://pr.mail.yahoo.co.jp/toolbar/

Tatsuro MATSUOKA wrote:
> Hello
>
> Although I vote this issuse here again, I cannot have an enough time to contribute it 
> at the moment.  I have an immediate work on my university activity.  
> Thefore I cannot committe the isusse at the moment.
> Please give a moment to try to build and test what David have advised.
>
> Are there any other persons who have volantary minds in downloading of my cygwin octave with
> the development enviroments ?
>
> Otherwise please give me a time to try to come back to discuss the  matter.
>
> Thank you in advance for your warm minds for my delay on this matter.
>
> Regards
>
> Tatsuro
>   

Does anyone out there have a cygwin/mingw octave installed where
mkoctfile works and wants to test the SVN of the octave-forge fixed
package? Doing so would be a great help in debugging the build issue we
are having with this package..

D.


-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

* David Bateman <David.Bateman@...> [2008-03-27 12:41]:

> If we can do the same under mingw, cygwin and msvc, then I'd suggest the
> attached patch.. [snip]

Thanks, your patch works on Debian for me, at least for the build/install.
However, I am stiil having a problem at run time:

    octave:1> test fixedpoint
    error: can't perform indexing operations for <unknown type> type
    octave:32 which fixed
    fixed is the dynamically-linked function from the file
    /usr/lib/octave/packages/fixed-0.7.5/x86_64-pc-linux-gnu-api-v32/fixed.oct

It only works after I run:

    octave:3> source ("/usr/lib/octave/packages/fixed-0.7.5/x86_64-pc-linux-gnu-api-v32/PKG_ADD")

Is that normal?

BTW, there was another question I asked about PKG_ADD that went unanswered.
I am repeating it below, thanks, 

R.

Rafael Laboissiere wrote:
>
> I am having trouble to install this package using the version of pkg.m
> currently on tip of the hg repository.  This version allows installing from
> the unpacked directory (not from the tarball).  The problems are caused by
> the presence of PKG_ADD at the top dir.  When I issue "pkg install .",
> octave complains with:
>
>     error: `fullfile' undefined near line 1 column 22
>
> If I add the following to the top of PKG_ADD:
>
>     addpath (genpath ("/usr/lib/octave/3.0.0/oct"), "-begin");
>     addpath (genpath ("/usr/share/octave/3.0.0/m"), "-begin");
>
> then the error disappears but I get:
>
>     warning: autoload: `./fixed.oct' is not an absolute file name
>
> Is there a way to get around these problems?

Rafael Laboissiere wrote:
> * David Bateman <David.Bateman@...> [2008-03-27 12:41]:
>
>   
>> If we can do the same under mingw, cygwin and msvc, then I'd suggest the
>> attached patch.. [snip]
>>     
>
> Thanks, your patch works on Debian for me, at least for the build/install.
> However, I am stiil having a problem at run time:
>
>     octave:1> test fixedpoint
>     error: can't perform indexing operations for <unknown type> type
>     octave:32 which fixed
>     fixed is the dynamically-linked function from the file
>     /usr/lib/octave/packages/fixed-0.7.5/x86_64-pc-linux-gnu-api-v32/fixed.oct
>
> It only works after I run:
>
>     octave:3> source ("/usr/lib/octave/packages/fixed-0.7.5/x86_64-pc-linux-gnu-api-v32/PKG_ADD")
>
> Is that normal?
>   
No that not normal, though I don't have time to check that at the
moment, I will later..

> BTW, there was another question I asked about PKG_ADD that went unanswered.
> I am repeating it below, thanks, 
>
> R.
>
> Rafael Laboissiere wrote:
>   
>> I am having trouble to install this package using the version of pkg.m
>> currently on tip of the hg repository.  This version allows installing from
>> the unpacked directory (not from the tarball).  The problems are caused by
>> the presence of PKG_ADD at the top dir.  When I issue "pkg install .",
>> octave complains with:
>>
>>     error: `fullfile' undefined near line 1 column 22
>>
>> If I add the following to the top of PKG_ADD:
>>
>>     addpath (genpath ("/usr/lib/octave/3.0.0/oct"), "-begin");
>>     addpath (genpath ("/usr/share/octave/3.0.0/m"), "-begin");
>>     
They should already be on the path at that point.. Something very
strange is happen there, though I haven't checked a pkg build in the
last few days, I'll check later and see if I can generate the same issue.


>> then the error disappears but I get:
>>
>>     warning: autoload: `./fixed.oct' is not an absolute file name
>>     
That error seems to indicated that this is not Octave 3.0.0 or later.


>> Is there a way to get around these problems?
>>     




>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
>
>   


-- 
David Bateman                                David.Bateman@...
Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

* David Bateman <David.Bateman@...> [2008-03-27 18:05]:

> >> then the error disappears but I get:
> >>
> >>     warning: autoload: `./fixed.oct' is not an absolute file name
> >>     
> That error seems to indicated that this is not Octave 3.0.0 or later.

Nope, I am positive here:

$ octave --version | perl -ne 'print;exit'
GNU Octave, version 3.0.0

-- 
Rafael

Hello

Sorry for my delay will slow things.
If other people will not appear, I will come back to this topic approximately a week later.

However I strongly hope that some power users will appear on the octave for windows 
maintaining activities. 

Regards

Tatsuro

--- David Bateman <David.Bateman@...> wrote:

> Tatsuro MATSUOKA wrote:
> > Hello
> >
> > Although I vote this issuse here again, I cannot have an enough time to contribute it 
> > at the moment.  I have an immediate work on my university activity.  
> > Thefore I cannot committe the isusse at the moment.
> > Please give a moment to try to build and test what David have advised.
> >
> > Are there any other persons who have volantary minds in downloading of my cygwin octave with
> > the development enviroments ?
> >
> > Otherwise please give me a time to try to come back to discuss the  matter.
> >
> > Thank you in advance for your warm minds for my delay on this matter.
> >
> > Regards
> >
> > Tatsuro
> >   
> 
> Does anyone out there have a cygwin/mingw octave installed where
> mkoctfile works and wants to test the SVN of the octave-forge fixed
> package? Doing so would be a great help in debugging the build issue we
> are having with this package..
> 
> D.
> 
> 
> -- 
> David Bateman                                David.Bateman@...
> Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
> Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
> 91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 
> 
> The information contained in this communication has been classified as: 
> 
> [x] General Business Information 
> [ ] Motorola Internal Use Only 
> [ ] Motorola Confidential Proprietary
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar
http://pr.mail.yahoo.co.jp/toolbar/

Hello

I felt bad in the morning so that I canceled today's work.
In the afternoon my situaion rather became better so I tried the be below.
I have down loaded the SVN today by

langus (an alias comand by me to set locale to US for avoiding character traslation mistakes)
svn co https://octave.svn.sourceforge.net/svnroot/octave/trunk/octave-forge/main/fixed fixed 


On mingw

Tatsu@... ~/octaves/fixedSVN/fixed/examples
$ make
Depending ffft.cc
rm -f ffft.d
g++ -M -I/mingw/include -I/usr/local/octave-3.0.0/include -I/GnuWin32/include
-Ic:/progra~1/Pcre/include -I/usr/local/octave-3.0.0/include/octave-3.0.0
-I/usr/local/octave-3.0.0/include/octave-3.0.0/octave -I/usr/local/octave-3.0.0/include
-mieee-fp -g -O2 -I../src -DHAVE_OCTAVE_30 ffft.cc | /bin/sed -e 's,^[^:]*/\(.*\.o\):,\1:,' -e
's,ffft\.o,pic/& & ffft.d,g' > ffft.d-t && mv ffft.d-t ffft.d
Depending fixed_inc.cc
   :
   :
Linking ffft.oct
g++ -shared -Wl,--export-all-symbols -Wl,--enable-auto-import -Wl,--enable-runtime-pseudo-reloc -o
ffft.oct ffft.o -L../src -lfixed -L/usr/local/octave-3.0.0/lib/octave-3.0.0
-L/usr/local/octave-3.0.0/lib -loctinterp -loctave -lcruft -L/mingw/lib -L/usr/local/octave-3.0.0/lib
-L/GnuWin32/lib -L/GnuWin32/bin -llapack -ltmglib -lblas -lfftw3 -lreadline -ltermcap -lz -lm -luuid
-lgmp -lws2_32 -lkernel32 -L/mingw/lib -L/usr/local/octave-3.0.0/lib -L/GnuWin32/lib -L/GnuWin32/bin
-L/mingw/bin/../lib/gcc/mingw32/3.4.5 -L/mingw/bin/../lib/gcc
-L/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../mingw32/lib
-L/mingw/bin/../lib/gcc/mingw32/3.4.5/../../.. -lz -lm -luuid -lgmp -lfrtbegin -lg2c -lmingw32
-lmoldname -lmingwex -lmsvcrt -luser32 -lkernel32 -ladvapi32 -lshell32
c:\Programs\MinGW\bin\..\lib\gcc\mingw32\3.4.5\..\..\..\..\mingw32\bin\ld.exe: cannot find -lfixed
collect2: ld returned 1 exit status
make: *** [ffft.oct] Error 1

Result is just the same on cygwin.

Main problem is that new  Makefile by you  did not give a liboctave_fixed.dll.a
so that the link seeme to be failed.

However my condition is not so good, I only just the report the results.
My feeling the previous fix is required for the cygwin/mingw.
For the dll point of view, the gcc exporting function is the same on the cygwin and the mingw.
So that the treatments for dlls are the same.

Regards

Tatsuro

 
--- David Bateman <David.Bateman@...> wrote:

> Michael Goffioul wrote:
> > On Thu, Mar 27, 2008 at 12:54 PM, David Bateman
> > <David.Bateman@...> wrote:
> >   
> >>  The problem I had with cygwin is that at the time the example oct-files
> >>  were build it wanted the symbols to be resolved, and thus linked against
> >>  fixed.oct..... If the OCTAVE_FIXED_API macro doesn't address that issue
> >>  then I don't think my fix with work on the cygwin platform and probably
> >>  not the mingw platform either. It should work on MSVC as this is
> >>  essentially what you were doing with your previous patches...
> >>
> >>  How can we force the link of the oct-file to not attempt to resolve the
> >>  symbols for the fixed type during the link, but rather at run time?
> >>     
> >
> > You can't. What I did with MSVC is to add "-lfixed" flag when linking
> > the oct-files from the examples directory. AFAIK, in Win32, whatever
> > you do, all symbols must be resolved at link-time.
> >   
> 
> Ok, then if you can link against the oct-file, then that doesn't change
> anything except the need to add "-L../src -lfixed" when building the
> example oct-files.. I committed another patch to do that.. Tatsuro,
> you'll need to update your SVN before trying
> 
> cd main/fixed/src
> ./autogen.sh
> ./configure
> make
> cd ../examples
> make
> octave
> addpath ("../src")
> a = ffft(fixed(6,4,32*randn(64,1)))
> 
> 
> to see if this works for cygwin/mingw
> 
> Regards
> David
> 
> -- 
> David Bateman                                David.Bateman@...
> Motorola Labs - Paris                        +33 1 69 35 48 04 (Ph) 
> Parc Les Algorithmes, Commune de St Aubin    +33 6 72 01 06 33 (Mob) 
> 91193 Gif-Sur-Yvette FRANCE                  +33 1 69 35 77 01 (Fax) 
> 
> The information contained in this communication has been classified as: 
> 
> [x] General Business Information 
> [ ] Motorola Internal Use Only 
> [ ] Motorola Confidential Proprietary
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar
http://pr.mail.yahoo.co.jp/toolbar/

Tatsuro MATSUOKA-2 wrote:
> 
> Main problem is that new  Makefile by you  did not give a
> liboctave_fixed.dll.a
> so that the link seeme to be failed.
> 

The idea was to try and link against the fixed.oct file rather than a
separate library. That is what Michael did under MSVC, so I suspect there is
some way to do it under mingw/cygwin. How do you tell gcc that "oct" is a
valid extension for a dll?



> However my condition is not so good, I only just the report the results.
> My feeling the previous fix is required for the cygwin/mingw.
> For the dll point of view, the gcc exporting function is the same on the
> cygwin and the mingw.
> So that the treatments for dlls are the same.
> 

This good in a way, as what work with mingw will alo work with cygwin. I
hope you get better soon however..

Regards
David
-- 
View this message in context: http://www.nabble.com/fixed-fails-to-build-on-linux-tp16220071p16367323.html
Sent from the octave-dev mailing list archive at Nabble.com.

On Sat, Mar 29, 2008 at 7:48 AM, dbateman <dbateman@...> wrote:
>  The idea was to try and link against the fixed.oct file rather than a
>  separate library. That is what Michael did under MSVC, so I suspect there is
>  some way to do it under mingw/cygwin. How do you tell gcc that "oct" is a
>  valid extension for a dll?

I think you need to create the import library for fixed.oct (something like
libfixed.a). This import lib is automatically generated by MSVC when there
are exported symbols. This is not the case for MinGW, you need some
additional compile flags.

Michael.

Hello David
After one day rest, my condition rather better so that I can think about this with cool head.

Cannot src/Makefile in the fixed package come back before for mingw/cygwin pat without affective for
Unix build ?

My previous patch works correctly.

Using previous the Makefile that I made a patch before , the fixed.oct linked the following 
Linking fixed.oct
g++ -shared -Wl,--export-all-symbols -Wl,--enable-auto-import -Wl,--enable-runtime-pseudo-reloc -o
fixed.oct fixed-int.o fixedColVector.o fixedRowVector.o fixedMatrix.o fixedComplex.o fixedCColVector.o
fixedCRowVector.o fixedCMatrix.o Array-f.o fixed-conv.o ov-fixed.o ov-fixed-mat.o fixedNDArray.o
fixedCNDArray.o ov-fixed-complex.o ov-fixed-cx-mat.o op-fs-fs.o op-fs-fm.o op-fm-fs.o op-fm-fm.o
op-fs-fcs.o op-fs-fcm.o op-fm-fcs.o op-fm-fcm.o op-fcs-fs.o op-fcs-fm.o op-fcm-fs.o op-fcm-fm.o
op-fcs-fcs.o op-fcs-fcm.o op-fcm-fcs.o op-fcm-fcm.o fixed-var.o fixed.o
-Wl,--out-implib=liboctave_fixed.dll.a -L/usr/local/octave-3.0.0/lib/octave-3.0.0
-L/usr/local/octave-3.0.0/lib -loctinterp -loctave -lcruft -L/mingw/lib -L/usr/local/octave-3.0.0/lib
-L/GnuWin32/lib -L/GnuWin32/bin -llapack -ltmglib -lblas -lfftw3 -lreadline -ltermcap -lz -lm -luuid
-lgmp -lws2_32 -lkernel32 -L/mingw/lib -L/usr/local/octave-3.0.0/lib -L/GnuWin32/lib -L/GnuWin32/bin
-L/mingw/bin/../lib/gcc/mingw32/3.4.5 -L/mingw/bin/../lib/gcc
-L/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../mingw32/lib
-L/mingw/bin/../lib/gcc/mingw32/3.4.5/../../.. -lz -lm -luuid -lgmp -lfrtbegin -lg2c -lmingw32
-lmoldname -lmingwex -lmsvcrt -luser32 -lkernel32 -ladvapi32 -lshell32
Creating library file: liboctave_fixed.dll.a

Michael>This import lib is automatically generated by MSVC when there 
Michael>are exported symbols. This is not the case for MinGW, you need some 
Michael>additional compile flags.

You need some additional compile flags. ==> You need liboctave_fixed.dll.a

> How do you tell gcc that "oct" is a
> valid extension for a dll?

-shared -Wl,--export-all-symbols -Wl,--enable-auto-import -Wl,--enable-runtime-pseudo-reloc
--enable-auto-import -Wl, --out-implib=liboctave_fixed.dll.a   

The flag make it possible fixed.oct behaves as a dynamic link libraries.

Perhaps the MSVC case is similar, the difference is that the import lib is automatically generated by
MSVC as the Michael suggestion.  This was suggested in the long discussin with me, you and Michael.

I confirmed this like following

cd ../examples 
make

The make failed at the link, I manualy linked 
g++ -shared -Wl,--export-all-symbols -Wl,--enable-auto-import -Wl,--enable-runtime-pseudo-reloc -o
ffft.oct ffft.o -L/home/octaves/fixedSVN/fixed-0.7.5/src -loctave_fixed.dll
-L/usr/local/octave-3.0.0/lib/octave-3.0.0 -L/usr/local/octave-3.0.0/lib -loctinterp -loctave -lcruft
-L/mingw/lib -L/usr/local/octave-3.0.0/lib -L/GnuWin32/lib -L/GnuWin32/bin -llapack -ltmglib -lblas
-lfftw3 -lreadline -ltermcap -lz -lm -luuid -lgmp -lws2_32 -lkernel32 -L/mingw/lib
-L/usr/local/octave-3.0.0/lib -L/GnuWin32/lib -L/GnuWin32/bin -L/mingw/bin/../lib/gcc/mingw32/3.4.5
-L/mingw/bin/../lib/gcc -L/mingw/bin/../lib/gcc/mingw32/3.4.5/../../../../mingw32/lib
-L/mingw/bin/../lib/gcc/mingw32/3.4.5/../../.. -lz -lm -luuid -lgmp -lfrtbegin -lg2c -lmingw32
-lmoldname -lmingwex -lmsvcrt -luser32 -lkernel32 -ladvapi32 -lshell32

-L../ -> -L/home/octaves/fixedSVN/fixed-0.7.5/src

After that 
octave 
addpath ("../src") 
a = ffft(fixed(6,4,32*randn(64,1)))

The window messages said that the dynamic link libarary fixed.oct was not found. 
(in reality it was represented in Japanese)
Please note that the exetention dll is not required for the windows dynamic link library.

Then
export PATH=/home/octaves/fixedSVN/fixed-0.7.5/src:$PATH
octave 
addpath ("../src") 
a = ffft(fixed(6,4,32*randn(64,1)))

a =

  -25.0000 +  0.0000i
  -24.0000 + 12.0000i
    4.0000 + 36.5000i
    1.0000 + 20.0000i
   -4.0000 - 15.5000i
   -5.0000 - 13.5000i
   -2.5000 + 33.0000i
   -6.5000 - 34.0000i
   15.0000 -  0.5000i
  -28.0000 - 25.5000i
  -16.5000 + 28.0000i
  -27.0000 - 24.0000i
   35.5000 - 14.5000i
  -20.5000 -  6.5000i
    9.0000 -  2.0000i
   12.5000 -  9.0000i
   21.5000 - 24.5000i
  -24.5000 + 15.0000i
   -5.0000 + 18.5000i
   -2.5000 - 16.5000i
  -28.5000 + 28.0000i
  -53.0000 - 16.0000i
        :
        :


Regards

Tatsuro

--- dbateman <dbateman@...> wrote:

> 
> 
> 
> Tatsuro MATSUOKA-2 wrote:
> > 
> > Main problem is that new  Makefile by you  did not give a
> > liboctave_fixed.dll.a
> > so that the link seeme to be failed.
> > 
> 
> The idea was to try and link against the fixed.oct file rather than a
> separate library. That is what Michael did under MSVC, so I suspect there is
> some way to do it under mingw/cygwin. How do you tell gcc that "oct" is a
> valid extension for a dll?
> 
> 
> 
> > However my condition is not so good, I only just the report the results.
> > My feeling the previous fix is required for the cygwin/mingw.
> > For the dll point of view, the gcc exporting function is the same on the
> > cygwin and the mingw.
> > So that the treatments for dlls are the same.
> > 
> 
> This good in a way, as what work with mingw will alo work with cygwin. I
> hope you get better soon however..
> 
> Regards
> David
> -- 
> View this message in context:
> http://www.nabble.com/fixed-fails-to-build-on-linux-tp16220071p16367323.html
> Sent from the octave-dev mailing list archive at Nabble.com.
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar
http://pr.mail.yahoo.co.jp/toolbar/

Michael Goffioul-2 wrote:
> 
> I think you need to create the import library for fixed.oct (something
> like
> libfixed.a). This import lib is automatically generated by MSVC when there
> are exported symbols. This is not the case for MinGW, you need some
> additional compile flags.
> 
> Michael.
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> 

Ok, this is what I had to do when I created the separate library.. I don't
think I'll be able to debug this without a mingw/cygwin installation. Looks
like my first step is setting that up.

D.

-- 
View this message in context: http://www.nabble.com/fixed-fails-to-build-on-linux-tp16220071p16369484.html
Sent from the octave-dev mailing list archive at Nabble.com.

Tatsuro MATSUOKA-2 wrote:
> 
> After one day rest, my condition rather better so that I can think about
> this with cool head.
> 

Some good news :-)



> Cannot src/Makefile in the fixed package come back before for mingw/cygwin
> pat without affective for
> Unix build ?
> 
> My previous patch works correctly.
> 

The problem is that its not clear where the DLL should be installed, and it
doesn't easily fit in the scheme of the package manager to have a library
within an octave-forge package. So if possible I'd rather get rid of the
library. If we can have the libfixed.a import library created, I don't
believe it has to be installed and it will allow the example files t be
built.

I'll try to install a mingw and check if I can't figure this out..

Regards
David
-- 
View this message in context: http://www.nabble.com/fixed-fails-to-build-on-linux-tp16220071p16369723.html
Sent from the octave-dev mailing list archive at Nabble.com.

On Sat, Mar 29, 2008 at 1:12 PM, Tatsuro MATSUOKA <tmacchant@...> wrote:
>  Michael>This import lib is automatically generated by MSVC when there
>  Michael>are exported symbols. This is not the case for MinGW, you need some
>  Michael>additional compile flags.
>
>  You need some additional compile flags. ==> You need liboctave_fixed.dll.a

Don't use liboctave_fixed.dll.a, use libfixed.a instead. This allows you to link
against fixed.oct with -lfixed, which is compatible with MSVC case.

Michael.

Hello Michael

Every one waits you to comes back.
I understand that this is a mere file name handling problem of file.
Hi, David.  I would like to octave in windows platform treat problem in the sameframe work.
I think you are already proceed to this issue on mingw.

Can I consider the patch to the current svn source?
Revision 4814

Regards

Tatsuro 

--- Michael Goffioul <michael.goffioul@...> wrote:

> On Sat, Mar 29, 2008 at 1:12 PM, Tatsuro MATSUOKA <tmacchant@...> wrote:
> >  Michael>This import lib is automatically generated by MSVC when there
> >  Michael>are exported symbols. This is not the case for MinGW, you need some
> >  Michael>additional compile flags.
> >
> >  You need some additional compile flags. ==> You need liboctave_fixed.dll.a
> 
> Don't use liboctave_fixed.dll.a, use libfixed.a instead. This allows you to link
> against fixed.oct with -lfixed, which is compatible with MSVC case.
> 
> Michael.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Register now and save $200. Hurry, offer ends at 11:59 p.m., 
> Monday, April 7! Use priority code J8TLD2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
http://pr.mail.yahoo.co.jp/ganbare-nippon/

Hello

--- David wrote:

On Mon, Apr 07, 2008 at 12:44:33AM +0900, Tatsuro MATSUOKA wrote:
> Hello Michael
> 
> Every one waits you to comes back.
> I understand that this is a mere file name handling problem of file.
> Hi, David.  I would like to octave in windows platform treat problem in the sameframe work.
> I think you are already proceed to this issue on mingw.
> 
> Can I consider the patch to the current svn source?
> Revision 4814

I haven't addressed mingw yet, I've been busy on other things.. I think 
the fix is relatively easy, its just a matter of using the right flag to 
gcc to get it to create the import library at the time the fixed.oct 
file is created.  I'd be happy to see you propose a patch though as I 
haven't even gotten around to installing a mingw with compilers yet. 
This is one of teh things i think has to be fixed before the yet 
octave-forge release, together with getting the ginput command in 
octave-forge working with the wxt terminal under windows..

Cheers
David
***************

OK. You seem to be too busy. I will do it tonight (in JST or tomorrow morining, hopefully).

Regards

Tatsuro





--------------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
http://pr.mail.yahoo.co.jp/ganbare-nippon/

Hello

Sorry. I have tried this morning, but it has not work well yet.
Please wait a while.

Regards 

Tatsuro


--- Tatsuro MATSUOKA <tmacchant@...> wrote:

> Hello
> 
> --- David wrote:
> 
> On Mon, Apr 07, 2008 at 12:44:33AM +0900, Tatsuro MATSUOKA wrote:
> > Hello Michael
> > 
> > Every one waits you to comes back.
> > I understand that this is a mere file name handling problem of file.
> > Hi, David.  I would like to octave in windows platform treat problem in the sameframe work.
> > I think you are already proceed to this issue on mingw.
> > 
> > Can I consider the patch to the current svn source?
> > Revision 4814
> 
> I haven't addressed mingw yet, I've been busy on other things.. I think 
> the fix is relatively easy, its just a matter of using the right flag to 
> gcc to get it to create the import library at the time the fixed.oct 
> file is created.  I'd be happy to see you propose a patch though as I 
> haven't even gotten around to installing a mingw with compilers yet. 
> This is one of teh things i think has to be fixed before the yet 
> octave-forge release, together with getting the ginput command in 
> octave-forge working with the wxt terminal under windows..
> 
> Cheers
> David
> ***************
> 
> OK. You seem to be too busy. I will do it tonight (in JST or tomorrow morining, hopefully).
> 
> Regards
> 
> Tatsuro
> 
> 
> 
> 
> 
> --------------------------------------
> GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
> http://pr.mail.yahoo.co.jp/ganbare-nippon/
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Register now and save $200. Hurry, offer ends at 11:59 p.m., 
> Monday, April 7! Use priority code J8TLD2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
http://pr.mail.yahoo.co.jp/ganbare-nippon/

Hello

I have complete misled the matter yesterday.
I found it was very easy this morning.
I would like to cry how silly I was !!!!!!! :-(
 
BTW: The following Patch is OK for src/Makefile for mingw/cygwin.

*** Makefile.org	Thu Apr 10 08:28:11 2008
--- Makefile	Thu Apr 10 08:31:30 2008
***************
*** 4,14 ****
--- 4,17 ----
  FIXEDTARGET = fixed.oct 
  
  DLLDEF =
+ ADD_FLAGS =  
  ifneq (,$(findstring cygwin,$(canonical_host_type)))
     DLLDEF = -DFIXED_DLL
+    ADD_FLAGS = -Wl,--out-implib=libfixed.a
  endif
  ifneq (,$(findstring mingw,$(canonical_host_type)))
     DLLDEF = -DFIXED_DLL
+    ADD_FLAGS = -Wl,--out-implib=libfixed.a
  endif
  ifneq (,$(findstring msdosmsvc,$(canonical_host_type)))
     DLLDEF = -DFIXED_DLL


**************************
I have confirmed

cd main/fixed/src
./autogen.sh
./configure
make
cd ../examples
make
PATH=$PATH:../src
octave
addpath ("../src")
a = ffft(fixed(6,4,32*randn(64,1)))

in cygwin/mingw.

PATH to where fixed.oct is required because it plays both role as an oct and a dll file.)
So 
PATH=$PATH:../src
is addded.

I think we need to add path by
putenv('PATH', sprintf("\'%s\':***********", getenv('PATH')))

*********** is a PATH where fixed.oct is placed in octaverc something like that for windows
plataforms.

Hi,Micael!  Do you have a any good idea?

Regards

Tatsuro

 



--- Tatsuro MATSUOKA <tmacchant@...> wrote:

> Hello
> 
> Sorry. I have tried this morning, but it has not work well yet.
> Please wait a while.
> 
> Regards 
> 
> Tatsuro
> 
> 
> --- Tatsuro MATSUOKA <tmacchant@...> wrote:
> 
> > Hello
> > 
> > --- David wrote:
> > 
> > On Mon, Apr 07, 2008 at 12:44:33AM +0900, Tatsuro MATSUOKA wrote:
> > > Hello Michael
> > > 
> > > Every one waits you to comes back.
> > > I understand that this is a mere file name handling problem of file.
> > > Hi, David.  I would like to octave in windows platform treat problem in the sameframe work.
> > > I think you are already proceed to this issue on mingw.
> > > 
> > > Can I consider the patch to the current svn source?
> > > Revision 4814
> > 
> > I haven't addressed mingw yet, I've been busy on other things.. I think 
> > the fix is relatively easy, its just a matter of using the right flag to 
> > gcc to get it to create the import library at the time the fixed.oct 
> > file is created.  I'd be happy to see you propose a patch though as I 
> > haven't even gotten around to installing a mingw with compilers yet. 
> > This is one of teh things i think has to be fixed before the yet 
> > octave-forge release, together with getting the ginput command in 
> > octave-forge working with the wxt terminal under windows..
> > 
> > Cheers
> > David
> > ***************
> > 
> > OK. You seem to be too busy. I will do it tonight (in JST or tomorrow morining, hopefully).
> > 
> > Regards
> > 
> > Tatsuro
> > 
> > 
> > 
> > 
> > 
> > --------------------------------------
> > GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
> > http://pr.mail.yahoo.co.jp/ganbare-nippon/
> > 
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> > Register now and save $200. Hurry, offer ends at 11:59 p.m., 
> > Monday, April 7! Use priority code J8TLD2. 
> > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> > _______________________________________________
> > Octave-dev mailing list
> > Octave-dev@...
> > https://lists.sourceforge.net/lists/listinfo/octave-dev
> > 
> 
> 
> --------------------------------------
> GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
> http://pr.mail.yahoo.co.jp/ganbare-nippon/
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Register now and save $200. Hurry, offer ends at 11:59 p.m., 
> Monday, April 7! Use priority code J8TLD2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
http://pr.mail.yahoo.co.jp/ganbare-nippon/

Hello 
This is a minor correction. Regards, Tatsuro
--- Tatsuro MATSUOKA <tmacchant@...> wrote:
> Hello
> 
> I have complete misled the matter yesterday.
> I found it was very easy this morning.
> I would like to cry how silly I was !!!!!!! :-(
>  
> BTW: The following Patch is OK for src/Makefile for mingw/cygwin.
> 
> *** Makefile.org	Thu Apr 10 08:28:11 2008
> --- Makefile	Thu Apr 10 08:31:30 2008
> ***************
> *** 4,14 ****
> --- 4,17 ----
>   FIXEDTARGET = fixed.oct 
>   
>   DLLDEF =
> + ADD_FLAGS =  
>   ifneq (,$(findstring cygwin,$(canonical_host_type)))
>      DLLDEF = -DFIXED_DLL
> +    ADD_FLAGS = -Wl,--out-implib=libfixed.a
>   endif
>   ifneq (,$(findstring mingw,$(canonical_host_type)))
>      DLLDEF = -DFIXED_DLL
> +    ADD_FLAGS = -Wl,--out-implib=libfixed.a
>   endif
>   ifneq (,$(findstring msdosmsvc,$(canonical_host_type)))
>      DLLDEF = -DFIXED_DLL
> 
> 
> **************************
> I have confirmed
> 
> cd main/fixed/src
> ./autogen.sh
> ./configure
> make
> cd ../examples
> make
> PATH=$PATH:../src   ====> export PATH=$PATH:../src   
> octave
> addpath ("../src")
> a = ffft(fixed(6,4,32*randn(64,1)))
> 
> in cygwin/mingw.
> 
> PATH to where fixed.oct is required because it plays both role as an oct and a dll file.)
> So 
> PATH=$PATH:../src  ====> export PATH=$PATH:../src   
> is addded.
> 
> I think we need to add path by
> putenv('PATH', sprintf("\'%s\':***********", getenv('PATH')))
> 
> *********** is a PATH where fixed.oct is placed in octaverc something like that for windows
> plataforms  at the package install. (<===== add 'at the package install')
 > 
> Hi,Micael!  Do you have an any good idea?
> 
> Regards
> 
> Tatsuro
> 
>  
> 
> 
> 
> --- Tatsuro MATSUOKA <tmacchant@...> wrote:
> 
> > Hello
> > 
> > Sorry. I have tried this morning, but it has not work well yet.
> > Please wait a while.
> > 
> > Regards 
> > 
> > Tatsuro
> > 
> > 
> > --- Tatsuro MATSUOKA <tmacchant@...> wrote:
> > 
> > > Hello
> > > 
> > > --- David wrote:
> > > 
> > > On Mon, Apr 07, 2008 at 12:44:33AM +0900, Tatsuro MATSUOKA wrote:
> > > > Hello Michael
> > > > 
> > > > Every one waits you to comes back.
> > > > I understand that this is a mere file name handling problem of file.
> > > > Hi, David.  I would like to octave in windows platform treat problem in the sameframe
> work.
> > > > I think you are already proceed to this issue on mingw.
> > > > 
> > > > Can I consider the patch to the current svn source?
> > > > Revision 4814
> > > 
> > > I haven't addressed mingw yet, I've been busy on other things.. I think 
> > > the fix is relatively easy, its just a matter of using the right flag to 
> > > gcc to get it to create the import library at the time the fixed.oct 
> > > file is created.  I'd be happy to see you propose a patch though as I 
> > > haven't even gotten around to installing a mingw with compilers yet. 
> > > This is one of teh things i think has to be fixed before the yet 
> > > octave-forge release, together with getting the ginput command in 
> > > octave-forge working with the wxt terminal under windows..
> > > 
> > > Cheers
> > > David
> > > ***************
> > > 
> > > OK. You seem to be too busy. I will do it tonight (in JST or tomorrow morining, hopefully).
> > > 
> > > Regards
> > > 
> > > Tatsuro
> > > 
> > > 
> > > 
> > > 
> > > 
> > > --------------------------------------
> > > GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
> > > http://pr.mail.yahoo.co.jp/ganbare-nippon/
> > > 
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> > > Register now and save $200. Hurry, offer ends at 11:59 p.m., 
> > > Monday, April 7! Use priority code J8TLD2. 
> > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> > > _______________________________________________
> > > Octave-dev mailing list
> > > Octave-dev@...
> > > https://lists.sourceforge.net/lists/listinfo/octave-dev
> > > 
> > 
> > 
> > --------------------------------------
> > GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
> > http://pr.mail.yahoo.co.jp/ganbare-nippon/
> > 
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> > Register now and save $200. Hurry, offer ends at 11:59 p.m., 
> > Monday, April 7! Use priority code J8TLD2. 
> > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> > _______________________________________________
> > Octave-dev mailing list
> > Octave-dev@...
> > https://lists.sourceforge.net/lists/listinfo/octave-dev
> > 
> 
> 
> --------------------------------------
> GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
> http://pr.mail.yahoo.co.jp/ganbare-nippon/
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
http://pr.mail.yahoo.co.jp/ganbare-nippon/

On Thu, Apr 10, 2008 at 2:01 AM, Tatsuro MATSUOKA <tmacchant@...> wrote:
> Hello
>
>  I have complete misled the matter yesterday.
>  I found it was very easy this morning.
>  I would like to cry how silly I was !!!!!!! :-(
>
>  BTW: The following Patch is OK for src/Makefile for mingw/cygwin.
>
>  *** Makefile.org        Thu Apr 10 08:28:11 2008
>  --- Makefile    Thu Apr 10 08:31:30 2008
>  ***************
>  *** 4,14 ****
>  --- 4,17 ----
>   FIXEDTARGET = fixed.oct
>
>   DLLDEF =
>  + ADD_FLAGS =
>   ifneq (,$(findstring cygwin,$(canonical_host_type)))
>      DLLDEF = -DFIXED_DLL
>  +    ADD_FLAGS = -Wl,--out-implib=libfixed.a
>   endif
>   ifneq (,$(findstring mingw,$(canonical_host_type)))
>      DLLDEF = -DFIXED_DLL
>  +    ADD_FLAGS = -Wl,--out-implib=libfixed.a
>   endif
>   ifneq (,$(findstring msdosmsvc,$(canonical_host_type)))
>      DLLDEF = -DFIXED_DLL
>
>
>  **************************
>  I have confirmed
>
>  cd main/fixed/src
>  ./autogen.sh
>  ./configure
>  make
>  cd ../examples
>  make
>  PATH=$PATH:../src
>  octave
>  addpath ("../src")
>  a = ffft(fixed(6,4,32*randn(64,1)))
>
>  in cygwin/mingw.
>
>  PATH to where fixed.oct is required because it plays both role as an oct and a dll file.)
>  So
>  PATH=$PATH:../src
>  is addded.
>
>  I think we need to add path by
>  putenv('PATH', sprintf("\'%s\':***********", getenv('PATH')))
>
>  *********** is a PATH where fixed.oct is placed in octaverc something like that for windows
>  plataforms.
>
>  Hi,Micael!  Do you have a any good idea?

You don't need this in a normal install. When calling "fixed" from
octave prompt,
octave will find and load fixed.oct as it would with any other
oct-file. When calling
"ffft" from octave prompt, octave will find and load ffft.oct and
resolve directly the
fixed.oct dependency as fixed.oct is already loaded in memory. So the only
requirement is that octave loads fixed.oct before ffft.oct. In
practice this will
always be the case, because you need a "fixed" object to pass as argument
to ffft.

Of course you could complain that something like:

ffft([])

won't work, because fixed.oct before. But that's not suppose to work anyway...
And this kind of dependency will exists on all platforms, so it's not a
Windows-only problem.

Michael.

Hello

Thank you for Michael

Regards

--- Michael Goffioul <michael.goffioul@...> wrote:

> On Thu, Apr 10, 2008 at 2:01 AM, Tatsuro MATSUOKA <tmacchant@...> wrote:
> > Hello
> >
> >  I have complete misled the matter yesterday.
> >  I found it was very easy this morning.
> >  I would like to cry how silly I was !!!!!!! :-(
> >
> >  BTW: The following Patch is OK for src/Makefile for mingw/cygwin.
> >
> >  *** Makefile.org        Thu Apr 10 08:28:11 2008
> >  --- Makefile    Thu Apr 10 08:31:30 2008
> >  ***************
> >  *** 4,14 ****
> >  --- 4,17 ----
> >   FIXEDTARGET = fixed.oct
> >
> >   DLLDEF =
> >  + ADD_FLAGS =
> >   ifneq (,$(findstring cygwin,$(canonical_host_type)))
> >      DLLDEF = -DFIXED_DLL
> >  +    ADD_FLAGS = -Wl,--out-implib=libfixed.a
> >   endif
> >   ifneq (,$(findstring mingw,$(canonical_host_type)))
> >      DLLDEF = -DFIXED_DLL
> >  +    ADD_FLAGS = -Wl,--out-implib=libfixed.a
> >   endif
> >   ifneq (,$(findstring msdosmsvc,$(canonical_host_type)))
> >      DLLDEF = -DFIXED_DLL
> >
> >
> >  **************************
> >  I have confirmed
> >
> >  cd main/fixed/src
> >  ./autogen.sh
> >  ./configure
> >  make
> >  cd ../examples
> >  make
> >  PATH=$PATH:../src
> >  octave
> >  addpath ("../src")
> >  a = ffft(fixed(6,4,32*randn(64,1)))
> >
> >  in cygwin/mingw.
> >
> >  PATH to where fixed.oct is required because it plays both role as an oct and a dll file.)
> >  So
> >  PATH=$PATH:../src
> >  is addded.
> >
> >  I think we need to add path by
> >  putenv('PATH', sprintf("\'%s\':***********", getenv('PATH')))
> >
> >  *********** is a PATH where fixed.oct is placed in octaverc something like that for windows
> >  plataforms.
> >
> >  Hi,Micael!  Do you have a any good idea?
> 
> You don't need this in a normal install. When calling "fixed" from
> octave prompt,
> octave will find and load fixed.oct as it would with any other
> oct-file. When calling
> "ffft" from octave prompt, octave will find and load ffft.oct and
> resolve directly the
> fixed.oct dependency as fixed.oct is already loaded in memory. So the only
> requirement is that octave loads fixed.oct before ffft.oct. In
> practice this will
> always be the case, because you need a "fixed" object to pass as argument
> to ffft.
> 
> Of course you could complain that something like:
> 
> ffft([])
> 
> won't work, because fixed.oct before. But that's not suppose to work anyway...
> And this kind of dependency will exists on all platforms, so it's not a
> Windows-only problem.
> 
> Michael.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Octave-dev mailing list
> Octave-dev@...
> https://lists.sourceforge.net/lists/listinfo/octave-dev
> 


--------------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
http://pr.mail.yahoo.co.jp/ganbare-nippon/