[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: hdf5 problem on cygwin octave is solved by illgal? way
From: |
Tatsuro MATSUOKA |
Subject: |
Re: hdf5 problem on cygwin octave is solved by illgal? way |
Date: |
Sat, 1 Sep 2007 06:19:02 +0900 (JST) |
Hello Michael and Benjamin
I have tested on mingw octave. The result is the same as
cygwin. Pherhaps this is not cygwin ability but is the
gcc.
>Benjamin
Did you aware -hdf5 should be deleted when hdf5 statically
build or did you build hdf5 dynamically?
Tatsuro Matsuoka
--- Michael Goffioul <address@hidden>
> On 8/31/07, Tatsuro MATSUOKA <address@hidden>
> wrote:
> > > Michael.
> >
> > > The problem with the static library is that any
> > > package that uses HDF5
> > > library (like fixed package) will produce
> multiple
> > > definition errors. So
> > > the only patch I can think of is to remove the
> > > ability to save in HDF5 format
> > > in octave-forge packages... (but maybe I'm
> > > overlooking something).
> > >
> >
> >
> > I have succeded to build the communications-1.0.2
> and
> > fixed-0.7.2 only to erase '-hdf5' in
> mkoctfile-2.9.13
>
> Maybe it's due to the fact that cygwin does export
> all symbols
> by default. So liboctinterp.dll exports all symbols
> from the HDF5
> library. This wouldn't have worked with MSVC.
>
> Michael.
>
--------------------------------------
Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar
http://pr.mail.yahoo.co.jp/toolbar/