Guenter wrote:

> hmm, but then the remaining two includes wouldnt be found either - but
they are, so this is not a prob; however for whatever reason it broke
all ares autobuilds (and memdebug?), and if nobody has a quick fix handy
I guess I better change back, or?

I did not know the testcurl.pl script, but I just checked it and found
the problem: since curlbuild.h is created at configure time, it goes to
the ./build-xxxx/include/curl directory, while other include files
remain in ./curl/include/curl. So my statement "curl.h and curlbuild.h
are in the same directory" is wrong in this special case. The other two
includes are OK because they really are in the same directory.

But please note that testcurl.pl adds a special -I option for that. This
is not needed for regular buildconf+configure+make cases (and the later
work perfectly with the pathless curlbuild.h inclusion).

So I think for the moment, you better change it back, and add a comment
!

Unless someone decides to change this dual include directory situation
in testcurl.pl builds, I would apply a specific patch at install time
for the OS400.

Thanks for your help.
Cheers
Patrick
Received on 2009-08-31