Hi,
I just faced a problem during the installation of image-1.0.7.tar.gz
under octave-3.0.1
octave:2> pkg install image-1.0.7.tar.gz
/usr/bin/ld: cannot find -lMagick
collect2: ld returned 1 exit status
make: *** [__magick_read__.oct] Error 1
error: 'make' returned the following error: make: Ent
On Mon, Aug 25, 2008 at 11:22 AM, Tatsuro MATSUOKA
<[EMAIL PROTECTED]> wrote:
> Hello
>
> I have failed to install some components of new octave-forge release on
> cygwin (octave-3.0.2).
>
> First one is ann-1.0.1 pakages
>
> Configure
> octave-forge is configured with
> octave: octave (ve
Hmm, the package doesn't seem to build on my machine at work. It seems
to me that the SWIG generated packages have been giving some problems,
so if you plan on distributing cygwin binaries, I'd recommend to skip
this package for now. When I get home tonight, I'll see if the package
builds t
Hello
I have failed to install some components of new octave-forge release on cygwin
(octave-3.0.2).
First one is ann-1.0.1 pakages
Configure
octave-forge is configured with
octave: octave (version 3.0.2)
mkoctfile: mkoctfile for Octave 2
swig:
make
$ make
make -C ann
Quoting David Bateman <[EMAIL PROTECTED]>:
> Now that this octave-forge release is done, should we target future
> octave-forge release for the 3.1.x/3.2.x tree? If so can I commit
> the patch that moves the quaternions, control, and ?? toolboxes into
> octave-forge. There are also several ot
Søren Hauberg wrote:
> søn, 24 08 2008 kl. 16:12 -0700, skrev Sergei Steshenko:
>
>
>> http://octave.sourceforge.net/packages.html still points to 2008-04-29 .
>>
>>
> Fixed!
>
> Thanks,
> Søren
>
>
Now that this octave-forge release is done, should we target future
octave-forge releas
