Jean-François Mertens wrote:
>
> On 02 Jan 2008, at 23:02, Alexandre Vial wrote:
>
>> Jonathan Stickel a écrit :
>>> Corey
>>>
>>> The latest octave-forge.info (20071212-1005) has a couple bugs.
>>>
>>> First, the perl command for correcting the octave_packages file does not
>>> work correctly, r
On 02 Jan 2008, at 23:02, Alexandre Vial wrote:
> Jonathan Stickel a écrit :
>> Corey
>>
>> The latest octave-forge.info (20071212-1005) has a couple bugs.
>>
>> First, the perl command for correcting the octave_packages file
>> does not
>> work correctly, resulting in octave not recognizing th
Jonathan Stickel a écrit :
> Corey
>
> The latest octave-forge.info (20071212-1005) has a couple bugs.
>
> First, the perl command for correcting the octave_packages file does not
> work correctly, resulting in octave not recognizing that any packages
> are installed.
>
> Second, the pkg prefixe
Alexander K. Hansen wrote:
> Jean-Francois Mertens wrote:
>> Jean-François Mertens wrote:
>>
>>> There is still something to fix in %p/share/octave/ls-R;
>>> 1) to make sure (PostInstScript) it gets re-updated correctly
>>> 2) perl -pi -e 's,%i,%p,'
>>>
>>
> I've been using this now for
Jean-Francois Mertens wrote:
> Jean-François Mertens wrote:
>
>> There is still something to fix in %p/share/octave/ls-R;
>> 1) to make sure (PostInstScript) it gets re-updated correctly
>> 2) perl -pi -e 's,%i,%p,'
>>
>
>
I've been using this now for a while--it seems OK.
One thing tha
Jean-François Mertens wrote:
> There is still something to fix in %p/share/octave/ls-R;
> 1) to make sure (PostInstScript) it gets re-updated correctly
> 2) perl -pi -e 's,%i,%p,'
No _ checked: this is a file of octave, and the refs are to octave's
blddir.
And the pkg seems functional w/o updating
Jean-François Mertens wrote:
> There is still something to fix in %p/share/octave/ls-R;
> 1) to make sure (PostInstScript) it gets re-updated correctly
> 2) perl -pi -e 's,%i,%p,'
No _ checked: this is a file of octave, and the refs are to octave's
blddir.
And the pkg seems functional w/o updating
On 10 Jul 2007, at 12:22, Alexander Hansen wrote:
> Jean-François Mertens wrote:
>>
>> On 08 Jul 2007, at 07:09, Jean-François Mertens wrote:
>>
>>>
>>> On 05 Jul 2007, at 23:22, Alexander Hansen wrote:
>>>
The current version of octave in 10.4/unstable has gone to a
package
mana
Jean-François Mertens wrote:
>
> On 08 Jul 2007, at 07:09, Jean-François Mertens wrote:
>
>>
>> On 05 Jul 2007, at 23:22, Alexander Hansen wrote:
>>
>>> The current version of octave in 10.4/unstable has gone to a package
>>> management system of its own to regulate installation of components of
>>
On 08 Jul 2007, at 07:09, Jean-François Mertens wrote:
>
> On 05 Jul 2007, at 23:22, Alexander Hansen wrote:
>
>> The current version of octave in 10.4/unstable has gone to a package
>> management system of its own to regulate installation of
>> components of
>> the octave-forge extensions. How
On 05 Jul 2007, at 23:22, Alexander Hansen wrote:
> The current version of octave in 10.4/unstable has gone to a package
> management system of its own to regulate installation of components of
> the octave-forge extensions. However, it also appears to be
> possible to
> do a monolithic version
On 2005-03-26, Christophe Favergeon wrote:
> Failed: compiling octave-forge-2004.02.12-3 failed
Try selfupdating.
The latest version of octave-forge is 2004.11.16-5, which should fix
this problem.
If a selfupdate doesn't cure this, please run
fink rebuild octave-forge 2>&1 | tee log
Christian Schaffner wrote:
> On 08.10.2004, at 00:05, Corey Halpin wrote:
>
>> octave-forge informed me today that it wants a maintainer.
>>
>> I'll volunteer for that, if nobody else wants it.
>
>
> I just noticed that you already have commit access to cvs. So, why don't
> you just go ahead
On 08.10.2004, at 00:05, Corey Halpin wrote:
octave-forge informed me today that it wants a maintainer.
I'll volunteer for that, if nobody else wants it.
I just noticed that you already have commit access to cvs. So, why
don't you just go ahead and add your name?
Chris.
-
Hi Corey
On 08.10.2004, at 00:05, Corey Halpin wrote:
octave-forge informed me today that it wants a maintainer.
I'll volunteer for that, if nobody else wants it.
That would be great. Do you have any updates for the packages (that you
want to put on the submission tracker) or shall i just put
On May 19, 2004, at 11:13 AM, Fabiano Sarracco wrote:
I got the following error while installing
Setting up fink (0.20.1-1) ...
Checking system... powerpc-apple-darwin7.3.0
Since you have gcc 3.3 installed, fink must be bootstrapped or updated using
that compiler. However, you currently have g
On April 19, 2004, Mathieu GUILLAUME wrote:
[]
galois.cc:1282: error: `TBM' undeclared (first use this function)
[]
Failed: compiling octave-forge-2004.02.12-2 failed
I succeed in installing this package from source for octave 2.1.53-1
(stable) but not for octave 2.1.57-2 (unstable).
On April 26,
On Mar 25, 2004, at 1:00 AM, Martin Costabel wrote:
Building octave-forge crashes for me because of a bad interaction with
lilypond (maintainer CCed): Lilypond installs a texinfo.tex file that
gets substituted for the real thing. This breaks texinfo which is used
for building octave-forge. I had
Linc Davis wrote:
With this package installed, I get the following error every time I run
apt:
You might want to run `apt-get -f install' to correct these:
Sorry, but the following packages have unmet dependencies:
octave-forge: Depends: X11 but it is not installable. For Fink users,
this of
On 18.03.2004, at 10:06, Yael Maguire wrote:
can't compile - problem with pngread.cc
Thanks for the feedback. However, we will need more information to help
you. Could you send the compile output with the exact error number?
Chris.
thanks and great job overall!
Yael Maguire
--
Package manager v
Hi Michael
On 08.03.2004, at 21:32, Michael Kluskens wrote:
fink install octave-forge gives:
...
ld: warning -prebind has no effect with -bundle
ld: can't locate file for: -lqhull
make[2]: *** [tsearch.oct] Error 1
make[1]: *** [geometry/] Error 2
make: *** [main/] Error 2
### execution of make f
On Mar 8, 2004, at 9:32 PM, Michael Kluskens wrote:
fink install octave-forge gives:
ld: can't locate file for: -lqhull
Thanks for the reminder _ the issue came up already before.
Fixed in cvs.
(if you can't wait, just add in the info file a line
SetLIBRARY_PATH: %p/lib )
JF Mertens
--
On fredag, jan 17, 2003, at 13:52 Europe/Stockholm, Jeff Whitaker wrote:
Maybe even better to make package octave add some lines to the global
startup script to check for the presence of a file named
'octave-forge-path' and read it. Jeff, comments?
I vote for this last solution - and putting
On Thu, 16 Jan 2003, Per Persson wrote:
> Hi,
> I just subitted an upated package for octave-forge to the tracker.
>
> There is one part that I don't particularly like and would like some
> feedback on:
> Octave-forge is a set of extensions to octave and must have its path
> added to octave's sear
24 matches
Mail list logo