help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: undeclared variable error


From: David Doria
Subject: Re: undeclared variable error
Date: Thu, 21 Jul 2011 10:36:56 -0400

2011/7/21 David Doria <address@hidden>:
>> The problem seems to hinge there. I believe I've seen you in Debian
>> mailing lists, so perhaps "apt-cache policy libcurl4-openssl-dev" will
>> tell us which one you've installed. I seem to be using 7.21.0.
>
> This is actually a RHEL machine. The curl package I have is:
> curl-devel.x86_64          7.15.5-9.el5_6.2
>
>> From reading the source in my version of curl, under
>> /usr/include/curl/curl.h,
>>
>>
>>     /* Backwards compatibility with older names */
>>     /* These are scheduled to disappear by 2011 */
>>
>>     /* This was added in version 7.19.1 */
>>     #define CURLOPT_POST301 CURLOPT_POSTREDIR
>>
>>     /* These are scheduled to disappear by 2009 */
>>
>>     /* The following were added in 7.17.0 */
>>     #define CURLOPT_SSLKEYPASSWD CURLOPT_KEYPASSWD
>>     #define CURLOPT_FTPAPPEND CURLOPT_APPEND
>>     #define CURLOPT_FTPLISTONLY CURLOPT_DIRLISTONLY
>>     #define CURLOPT_FTP_SSL CURLOPT_USE_SSL
>>
>> so it looks like all we need to do is change that symbol to
>> CURLOPT_FTPLISTONLY, because it got deprecated some time ago. Can you
>> confirm your curl version?
>
> So you're suggest that you will add some of these defines in Octave
> rather than rely on the Curl version being > 7.17? Could there also be
> a configure error that checked for the Curl version?
>
> David
>

I just tried to build octave against the latest Curl. It seems to get
past the error I was seeing, but now I get:

/home/ddoria/src/octave-3.4.2/doc/interpreter//matrix.texi:1429:
Unknown command `leq'.
/home/ddoria/src/octave-3.4.2/doc/interpreter//matrix.texi:1429: Misplaced {.
/home/ddoria/src/octave-3.4.2/doc/interpreter//matrix.texi:1429: Misplaced }.
makeinfo: Removing output file
`/home/ddoria/src/octave-3.4.2/doc/interpreter/octave.info' due to
errors; use --force to preserve.

Any thoughts?

David


reply via email to

[Prev in Thread] Current Thread [Next in Thread]