upgrade of doxygen-1.5.7 error

[Ryan Schmidt]

On Nov 11, 2008, at 08:44, Jonathan Stickel wrote:

> Ryan Schmidt wrote:
>> On Nov 10, 2008, at 14:12, Jonathan Stickel wrote:
>>> I get this error when upgrading doxygen to 1.5.7:
>>>
>>> c++ -c -pipe -D__FreeBSD__=6 -Wall -W -O2 -I../qtools -o ../ 
>>> objects/portable.o portable.cpp
>>> portable.cpp: In function 'size_t portable_iconv(void*, const  
>>> char**, size_t*, char**, size_t*)':
>>> portable.cpp:392: error: invalid conversion from 'char**' to  
>>> 'const char**'
>>> portable.cpp:392: error:   initializing argument 2 of 'size_t  
>>> libiconv(void*, const char**, size_t*, char**, size_t*)'
>>> gmake[2]: *** [../objects/portable.o] Error 1
>>>
>>> I have Mac OS 10.4.11.  Any suggestions?
>> iconv can be accessed in a couple different ways depending on  
>> iconv version and operating system. So it looks like doxygen is  
>> trying to use iconv in one way but on your system it wants the  
>> other way.
>> doxygen 1.5.7 builds fine for me on Mac OS X 10.4.11 so I think  
>> this problem is peculiar to your computer.
>> Do you have the libiconv port installed and activated? What  
>> version? It should have been done automatically for you, but use  
>> "port installed libiconv" to see.
>
> $ port installed libiconv
> The following ports are currently installed:
>   libiconv @1.12_0+darwin_8 (active)

Good, that's current...

>> Do you have anything in /usr/local/lib, in particular, a libiconv  
>> library? If so, remove it, and preferably anything else in /usr/ 
>> local. It often interferes with MacPorts-installed software.
>
> Nothing of significance in /usr/local/lib, but I do have:
>
> /Developer/SDKs/MacOSX10.3.9.sdk/usr/lib/libiconv.2.2.0.dylib
> /Developer/SDKs/MacOSX10.3.9.sdk/usr/lib/libiconv.2.dylib
> /Developer/SDKs/MacOSX10.3.9.sdk/usr/lib/libiconv.dylib
> /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libiconv.2.2.0.dylib
> /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libiconv.2.dylib
> /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libiconv.dylib

That's normal too.

Ok, can you please try cleaning and rebuilding doxygen once more,  
this time with debug output, and attach it here so I can compare it  
to my system's output?

sudo port clean doxygen
sudo port -d upgrade doxygen 2>&1 | tee ~/Desktop/doxygen.txt
bzip2 ~/Desktop/doxygen.txt

Then attach the file doxygen.txt.bz2 from your desktop to your reply.  
Thanks.