[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Help-octave Digest, Vol 48, Issue 36
|
From: |
Journeaux, Ian |
|
Subject: |
RE: Help-octave Digest, Vol 48, Issue 36 |
|
Date: |
Tue, 16 Mar 2010 08:09:58 -0500 |
Sent from my U.S. Cellular® Windows® phone.
-----Original Message-----
From: address@hidden <address@hidden>
Sent: Tuesday, March 16, 2010 7:29 AM
To: address@hidden <address@hidden>
Subject: Help-octave Digest, Vol 48, Issue 36
Send Help-octave mailing list submissions to
address@hidden
To subscribe or unsubscribe via the World Wide Web, visit
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
or, via email, send a message with subject or body 'help' to
address@hidden
You can reach the person managing the list at
address@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Help-octave digest..."
Today's Topics:
1. Re: Installation error from development sources (xnand)
2. Re: Installation error from development sources (xnand)
3. Re: pointers and recursive algorithms (Jaroslav Hajek)
4. Re: problem building octave 3.3.50 with MacPorts dependancies
(Liam Groener)
5. Block comments inside block comments (Carn? Draug)
6. Re: who uses Octave? (Jaroslav Hajek)
7. Re: Block comments inside block comments (David Grundberg)
----------------------------------------------------------------------
Message: 1
Date: Tue, 16 Mar 2010 01:58:02 -0700 (PDT)
From: xnand <address@hidden>
Subject: Re: Installation error from development sources
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii
David Grundberg-3 wrote:
>
> xnand wrote:
>>
>> LUK ShunTim-3 wrote:
>>
>>> xnand wrote:
>>>
>>>> xnand wrote:
>>>>
>>>>> David Grundberg-3 wrote:
>>>>>
>>>>>> xnand wrote:
>>>>>>
>>>>>>> Hi all.
>>>>>>>
>>>>>>> I am installing octave from the development sources. Below is the
>>>>>>> ending
>>>>>>> part of the output I got for the command "make":
>>>>>>>
>>>>>>> /bin/sh ../build-aux/ylwrap lex.ll lex.octave_.c lex.cc -- flex -I
>>>>>>> -I
>>>>>>> "/home/me/octave/src/lex.ll", line 27: unrecognized '%' directive
>>>>>>> "/home/me/octave/src/lex.ll", line 28: bad character: #
>>>>>>> "/home/me/octave/src/lex.ll", line 28: unknown error processing
>>>>>>> section
>>>>>>> 1
>>>>>>> "/home/me/octave/src/lex.ll", line 29: bad character: #
>>>>>>> "/home/me/octave/src/lex.ll", line 29: bad character: <
>>>>>>> "/home/me/octave/src/lex.ll", line 29: bad character: .
>>>>>>> "/home/me/octave/src/lex.ll", line 29: bad character: >
>>>>>>> "/home/me/octave/src/lex.ll", line 30: bad character: #
>>>>>>> "/home/me/octave/src/lex.ll", line 31: bad character: }
>>>>>>> make[2]: *** [lex.cc] Error 1
>>>>>>> make[2]: Leaving directory `/home/me/octave/src'
>>>>>>> make[1]: *** [all-recursive] Error 1
>>>>>>> make[1]: Leaving directory `/home/me/octave'
>>>>>>> make: *** [all] Error 2
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> Nands
>>>>>>>
>>>>>>>
>>>>>> What lexical analyzer generator are you running? And which version?
>>>>>> Check the configure output.
>>>>>>
>>>>>> hth,
>>>>>> David
>>>>>> _______________________________________________
>>>>>> Help-octave mailing list
>>>>>> address@hidden
>>>>>> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
>>>>>>
>>>>>>
>>>>>>
>>>>> Hi David.
>>>>>
>>>>> It's flex rpm package, version : 2.5.4a, release : 41.fc6.
>>>>> The lines related to lex in configure output were:
>>>>> checking for flex... flex
>>>>> checking lex output file root... lex.yy
>>>>> checking lex library... -lfl
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Nands
>>>>>
>>>>>
>>>>>
>>>> Hi all.
>>>>
>>>> I installed flex-2.5.35, and now I am getting this:
>>>>
>>>> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../libgnu -I../libgnu
>>>> -I../libcruft/misc -I../liboctave -I../liboctave -I. -I. -g -O2
>>>> -DHAVE_CONFIG_H -I/usr/include/freetype2 -Wall -W -Wshadow
>>>> -Wold-style-cast
>>>> -Wformat -g -O2 -pthread -g -O2 -MT
>>>> DLD-FUNCTIONS/DLD_FUNCTIONS_convhulln_la-convhulln.lo -MD -MP -MF
>>>> DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_convhulln_la-convhulln.Tpo -c
>>>> DLD-FUNCTIONS/convhulln.cc -fPIC -DPIC -o
>>>> DLD-FUNCTIONS/.libs/DLD_FUNCTIONS_convhulln_la-convhulln.o
>>>> DLD-FUNCTIONS/convhulln.cc:45:27: error: qhull/qhull_a.h: No such file
>>>> or
>>>> directory
>>>>
>>> It seems the qhull headers are not found. You may need to install the
>>> development package of qhull (usually called libqhull-dev or
>>> libqhull-devel) of your linux(?) distribution.
>>>
>>> Regards,
>>> ST
>>> --
>>>
>>>
>>> _______________________________________________
>>> Help-octave mailing list
>>> address@hidden
>>> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
>>>
>>>
>>>
>>
>> Hi all.
>>
>> Thanks to LUK ShunTim, I installed development package of qhull and got
>> cured of the error. But now, new error:
>>
>> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../libgnu -I../libgnu
>> -I../libcruft/misc -I../liboctave -I../liboctave -I. -I. -g -O2
>> -DHAVE_CONFIG_H -I/usr/include/freetype2 -Wall -W -Wshadow
>> -Wold-style-cast
>> -Wformat -g -O2 -pthread -g -O2 -MT
>> DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo -MD -MP -MF
>> DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_urlwrite_la-urlwrite.Tpo -c
>> DLD-FUNCTIONS/urlwrite.cc -fPIC -DPIC -o
>> DLD-FUNCTIONS/.libs/DLD_FUNCTIONS_urlwrite_la-urlwrite.o
>> DLD-FUNCTIONS/urlwrite.cc: In member function 'string_vector
>> curl_handle::list() const':
>> DLD-FUNCTIONS/urlwrite.cc:405: error: 'CURLOPT_DIRLISTONLY' was not
>> declared
>> in this scope
>> DLD-FUNCTIONS/urlwrite.cc:412: error: 'CURLOPT_DIRLISTONLY' was not
>> declared
>> in this scope
>> make[3]: *** [DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo] Error
>> 1
>> make[3]: Leaving directory `/home/me/octave/src'
>> make[2]: *** [all] Error 2
>> make[2]: Leaving directory `/home/me/octave/src'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/home/me/octave'
>> make: *** [all] Error 2
>>
>> Thanks.
>>
>> Nanddeep
>>
>>
>
> I think you need a newer version of curl. If you don't feel like having
> urlwrite/urlread support, you can disable curl (--without-curl) at
> configuration.
>
> David
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
>
>
Hi David.
I also thought that it must be because of old curl version. So installed
curl-7.20.0, but the error persists.
Thanks.
Nands
--
View this message in context:
http://old.nabble.com/Installation-error-from-development-sources-tp27876372p27914838.html
Sent from the Octave - General mailing list archive at Nabble.com.
------------------------------
Message: 2
Date: Tue, 16 Mar 2010 01:59:23 -0700 (PDT)
From: xnand <address@hidden>
Subject: Re: Installation error from development sources
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii
David Grundberg-3 wrote:
>
> xnand wrote:
>>
>> LUK ShunTim-3 wrote:
>>
>>> xnand wrote:
>>>
>>>> xnand wrote:
>>>>
>>>>> David Grundberg-3 wrote:
>>>>>
>>>>>> xnand wrote:
>>>>>>
>>>>>>> Hi all.
>>>>>>>
>>>>>>> I am installing octave from the development sources. Below is the
>>>>>>> ending
>>>>>>> part of the output I got for the command "make":
>>>>>>>
>>>>>>> /bin/sh ../build-aux/ylwrap lex.ll lex.octave_.c lex.cc -- flex -I
>>>>>>> -I
>>>>>>> "/home/me/octave/src/lex.ll", line 27: unrecognized '%' directive
>>>>>>> "/home/me/octave/src/lex.ll", line 28: bad character: #
>>>>>>> "/home/me/octave/src/lex.ll", line 28: unknown error processing
>>>>>>> section
>>>>>>> 1
>>>>>>> "/home/me/octave/src/lex.ll", line 29: bad character: #
>>>>>>> "/home/me/octave/src/lex.ll", line 29: bad character: <
>>>>>>> "/home/me/octave/src/lex.ll", line 29: bad character: .
>>>>>>> "/home/me/octave/src/lex.ll", line 29: bad character: >
>>>>>>> "/home/me/octave/src/lex.ll", line 30: bad character: #
>>>>>>> "/home/me/octave/src/lex.ll", line 31: bad character: }
>>>>>>> make[2]: *** [lex.cc] Error 1
>>>>>>> make[2]: Leaving directory `/home/me/octave/src'
>>>>>>> make[1]: *** [all-recursive] Error 1
>>>>>>> make[1]: Leaving directory `/home/me/octave'
>>>>>>> make: *** [all] Error 2
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> Nands
>>>>>>>
>>>>>>>
>>>>>> What lexical analyzer generator are you running? And which version?
>>>>>> Check the configure output.
>>>>>>
>>>>>> hth,
>>>>>> David
>>>>>> _______________________________________________
>>>>>> Help-octave mailing list
>>>>>> address@hidden
>>>>>> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
>>>>>>
>>>>>>
>>>>>>
>>>>> Hi David.
>>>>>
>>>>> It's flex rpm package, version : 2.5.4a, release : 41.fc6.
>>>>> The lines related to lex in configure output were:
>>>>> checking for flex... flex
>>>>> checking lex output file root... lex.yy
>>>>> checking lex library... -lfl
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Nands
>>>>>
>>>>>
>>>>>
>>>> Hi all.
>>>>
>>>> I installed flex-2.5.35, and now I am getting this:
>>>>
>>>> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../libgnu -I../libgnu
>>>> -I../libcruft/misc -I../liboctave -I../liboctave -I. -I. -g -O2
>>>> -DHAVE_CONFIG_H -I/usr/include/freetype2 -Wall -W -Wshadow
>>>> -Wold-style-cast
>>>> -Wformat -g -O2 -pthread -g -O2 -MT
>>>> DLD-FUNCTIONS/DLD_FUNCTIONS_convhulln_la-convhulln.lo -MD -MP -MF
>>>> DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_convhulln_la-convhulln.Tpo -c
>>>> DLD-FUNCTIONS/convhulln.cc -fPIC -DPIC -o
>>>> DLD-FUNCTIONS/.libs/DLD_FUNCTIONS_convhulln_la-convhulln.o
>>>> DLD-FUNCTIONS/convhulln.cc:45:27: error: qhull/qhull_a.h: No such file
>>>> or
>>>> directory
>>>>
>>> It seems the qhull headers are not found. You may need to install the
>>> development package of qhull (usually called libqhull-dev or
>>> libqhull-devel) of your linux(?) distribution.
>>>
>>> Regards,
>>> ST
>>> --
>>>
>>>
>>> _______________________________________________
>>> Help-octave mailing list
>>> address@hidden
>>> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
>>>
>>>
>>>
>>
>> Hi all.
>>
>> Thanks to LUK ShunTim, I installed development package of qhull and got
>> cured of the error. But now, new error:
>>
>> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I../libgnu -I../libgnu
>> -I../libcruft/misc -I../liboctave -I../liboctave -I. -I. -g -O2
>> -DHAVE_CONFIG_H -I/usr/include/freetype2 -Wall -W -Wshadow
>> -Wold-style-cast
>> -Wformat -g -O2 -pthread -g -O2 -MT
>> DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo -MD -MP -MF
>> DLD-FUNCTIONS/.deps/DLD_FUNCTIONS_urlwrite_la-urlwrite.Tpo -c
>> DLD-FUNCTIONS/urlwrite.cc -fPIC -DPIC -o
>> DLD-FUNCTIONS/.libs/DLD_FUNCTIONS_urlwrite_la-urlwrite.o
>> DLD-FUNCTIONS/urlwrite.cc: In member function 'string_vector
>> curl_handle::list() const':
>> DLD-FUNCTIONS/urlwrite.cc:405: error: 'CURLOPT_DIRLISTONLY' was not
>> declared
>> in this scope
>> DLD-FUNCTIONS/urlwrite.cc:412: error: 'CURLOPT_DIRLISTONLY' was not
>> declared
>> in this scope
>> make[3]: *** [DLD-FUNCTIONS/DLD_FUNCTIONS_urlwrite_la-urlwrite.lo] Error
>> 1
>> make[3]: Leaving directory `/home/me/octave/src'
>> make[2]: *** [all] Error 2
>> make[2]: Leaving directory `/home/me/octave/src'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/home/me/octave'
>> make: *** [all] Error 2
>>
>> Thanks.
>>
>> Nanddeep
>>
>>
>
> I think you need a newer version of curl. If you don't feel like having
> urlwrite/urlread support, you can disable curl (--without-curl) at
> configuration.
>
> David
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
>
>
Hi David.
I also thought that it must be because of old curl version. So installed
curl-7.20.0, but the error persists.
Thanks.
Nands
--
View this message in context:
http://old.nabble.com/Installation-error-from-development-sources-tp27876372p27914857.html
Sent from the Octave - General mailing list archive at Nabble.com.
------------------------------
Message: 3
Date: Tue, 16 Mar 2010 10:03:03 +0100
From: Jaroslav Hajek <address@hidden>
Subject: Re: pointers and recursive algorithms
To: C?ssio M. M. Pereira <address@hidden>
Cc: address@hidden
Message-ID:
<address@hidden>
Content-Type: text/plain; charset=ISO-8859-1
2010/3/15 C?ssio M. M. Pereira <address@hidden>:
>
> Dear list,
>
> I would like to implement a recursive tree algorithm in octave.
> As far as I know, Octave does not support pointer types.
> It seems to me that the most appropriate structure to implement a tree
> in octave would be a (nested) cell array.
>
> However, how can I, for instance, make a recursive binary search in a tree
> (implemented as a cell array) and return a pointer to the cell where the
> information is stored?
>
> If pointers are not available, is there another way to get around this?
>
> Thank you,
> C?ssio Pereira
I would suggest using indices into an array instead of pointers.
For instance, you can have three arrays, holding indices of the
left/right child, and node values.
A binary search can then look like this:
i = 1;
v = searched value;
while i > 0
x = values(j = i);
if (x > v)
i = left (i);
else
i = right (i);
endif
endwhile
# j now holds the leaf index, x its value.
but before you do this, I'd suggest you really make sure that you
can't do what you need with the ordinary array binary search using
"lookup".
--
RNDr. Jaroslav Hajek, PhD
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
------------------------------
Message: 4
Date: Tue, 16 Mar 2010 02:19:35 -0700
From: Liam Groener <address@hidden>
Subject: Re: problem building octave 3.3.50 with MacPorts dependancies
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii
On Mar 15, 2010, at 6:05 PM, Liam Groener wrote:
> Hi,
> I'm trying to build the development version using MacPort dependancies on OS
> X 10.6.2. The error I get is:
> ../../run-octave -f -q -H -p . --eval "geometryimages ('voronoi', 'txt');"
> dyld: Symbol not found:
> __ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEE7seekoffElSt12_Ios_SeekdirSt13_Ios_Openmode
> Referenced from:
> /Users/liamg/build45/octave/src/.libs/liboctinterp-3.3.50+.dylib Expected
> in: flat namespace
>
> Sure enough, looking at the library symbol table
> "__ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEE7seekoffElSt12_Ios_SeekdirSt13_Ios_Openmode"
> is not there.
>
> However, there is a DWARF subdirectory created and the symbol list of the
> library in there reads:
>
>
> /Users/liamg/build45/octave/src/.libs/liboctinterp-3.3.50+.dylib.dsym/contents/resources/dwarf/liboctinterp-3.3.50+.dylib:
> Indirect symbols for (__TEXT,__symbol_stub1) 6588 entries (entries extends
> past the end of the indirect symbol table)
> address index name
> Indirect symbols for (__DATA,__nl_symbol_ptr) 661 entries (entries start past
> the end of the indirect symbol table) (reserved1 field greater than the table
> size)
> address index name
> Indirect symbols for (__DATA,__la_symbol_ptr) 6588 entries (entries start
> past the end of the indirect symbol table) (reserved1 field greater than the
> table size)
> address index name
>
> This would seem to imply that dynamic library symbol tables are limited to to
> 6588 entries while 7249 symbols were created during link. Is this true? If
> so, is there a way to increase the limit?
>
> Liam G.
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
Well, I looked at the symbol table a little more and see that my guess was all
wet. The table has 6588 entries for (__TEXT,__symbol_stub1), 661 entries for
(__DATA,__nl_symbol_ptr), and 6588 entries for (__DATA,__la_symbol_ptr). The
corresponding numbers for Octave 3.2.3 (which works fine) are 6495, 855, and
6495. So what does it all mean?
------------------------------
Message: 5
Date: Tue, 16 Mar 2010 01:45:10 -0400
From: Carn? Draug <address@hidden>
Subject: Block comments inside block comments
To: address@hidden
Message-ID:
<address@hidden>
Content-Type: text/plain; charset=ISO-8859-1
Hi
I just realized that when inside a block comment, octave still notices
the start of another block comment. If this happens, then it's needed
to close it again. Not sure if I'm clear so here's an example what I
mean
printf ("Not comment 1\n");
#{
printf ("Comment 1\n");
#{
printf ("Comment 2\n");
#}
printf ("I'd have guessed NOT a comment but it is a comment and gives
warning of unclosed block comment\n");
Is this a feature or a bug? My idea on how comments work is that
everything is ignored until the end of the comment (end of the line,
in one line comments, or end of block character) but I may be wrong.
Carn? Draug
------------------------------
Message: 6
Date: Tue, 16 Mar 2010 07:53:00 +0100
From: Jaroslav Hajek <address@hidden>
Subject: Re: who uses Octave?
To: address@hidden, Matt Taylor <address@hidden>,
Sergei Steshenko <address@hidden>,
address@hidden, address@hidden, W J
KREAMER <address@hidden>
Message-ID:
<address@hidden>
Content-Type: text/plain; charset=ISO-8859-1
Great, I think this will do.
Many thanks to all who responded and I wish you all a success in your
work, whether using Octave or not.
best regards
--
RNDr. Jaroslav Hajek, PhD
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz
------------------------------
Message: 7
Date: Tue, 16 Mar 2010 13:26:51 +0100
From: David Grundberg <address@hidden>
Subject: Re: Block comments inside block comments
To: Carn? Draug <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Carn? Draug wrote:
> Hi
>
> I just realized that when inside a block comment, octave still notices
> the start of another block comment. If this happens, then it's needed
> to close it again. Not sure if I'm clear so here's an example what I
> mean
>
> printf ("Not comment 1\n");
> #{
> printf ("Comment 1\n");
> #{
> printf ("Comment 2\n");
> #}
> printf ("I'd have guessed NOT a comment but it is a comment and gives
> warning of unclosed block comment\n");
>
> Is this a feature or a bug? My idea on how comments work is that
> everything is ignored until the end of the comment (end of the line,
> in one line comments, or end of block character) but I may be wrong.
>
> Carn? Draug
>
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
>
That depends on the language, ML has recursive block comments as an
example. However, most imperative languages have block comments that can
be found with a regular expression (i.e. not recursive). How does matlab
interpret %{ }% comments?
David
------------------------------
_______________________________________________
Help-octave mailing list
address@hidden
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
End of Help-octave Digest, Vol 48, Issue 36
*******************************************
This electronic message contains information from NewPage Corporation or
subsidiary companies,
which may be confidential, privileged or otherwise protected from disclosure.
The information is
intended to be used solely by the recipient(s) named. If you are not an
intended recipient, be
aware that any review, disclosure, copying, distribution or use of this
transmission or its
contents is prohibited. If you have received this transmission in error, please
notify NewPage
immediately at address@hidden
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- RE: Help-octave Digest, Vol 48, Issue 36,
Journeaux, Ian <=