On Sat, 15 Sep 2007, Domenico Andreoli wrote:

> curl 7.17.0 breaks the build of openoffice.org. Rene has already found the
> cause, it is described below.

Eh, no. curl 7.17.0 does *not* break this as you will see below.

> Is it only a formal error by the curl side or openoffice.org requires to be
> upgraded to the new API?

The error code CURLE_FTP_USER_PASSWORD_INCORRECT has been moved to the list of
codes that will be removed in the future, and thus it isn't present if you
define CURL_NO_OLDIES when you build.

So if you want backwards-compatible style you *don't* define CURL_NO_OLDIES
and you can use that define fine still. If you define it, you should be
prepared to edit some of the codes to the up-to-date versions.

>>> | g++ -fmessage-length=0 -c -O2 -fno-strict-aliasing -DCURL_NO_OLDIES -I.

So why do these guys explicitly switch off compatibility?

>> It seems that curl wanted to keep compatibility but actually broke it
>> because the subsitution doesn't work?

Nope. We still support the option as described above.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html