Installing Apache2 on MacBook Pro issue

[Julien KRIVACSY]

Hello Again,

Here what I got with the first two commands :
> Last login: Tue Oct 31 15:40:06 on ttyp1
> Welcome to Darwin!
> MacBook:~ julien$ sudo port -f uninstall libiconv
> Password:
> Error: port uninstall failed: Registry error: libiconv not  
> registered as installed.
> MacBook:~ julien$ sudo port clean --all libiconv
> --->  Cleaning libiconv
> MacBook:~ julien$

And here is the result of the install command (which was the same  
result as usual). This is all that I got (previous text was dropped  
from iTerm) : http://www.emprint.fr/port/port.log


Thank you, Julien

Le 31 oct. 06 à 16:13, Ryan Schmidt a écrit :

> On Oct 31, 2006, at 02:34, Julien KRIVACSY wrote:
>
>>>>>> But while compiling libiconv (in apache2), I've got an error  
>>>>>> and I don't know what to do. Apparently, port is trying to  
>>>>>> compile a PPC version and I have got a MacBook Pro 1.83.
>>>>>>
>>>>>> Here's the error :
>>>>>> MacBook:/tmp/libiconv-1.11 root# port install apache2
>>>>>> --->  Staging libiconv into destroot
>>>>> [snip]
>>>>>> /usr/bin/ld: warning /opt/local/lib/libiconv.dylib cputype  
>>>>>> (18, architecture ppc) does not match cputype (7) for  
>>>>>> specified -arch flag: i386 (file not loaded)
>
>>>>> I believe the recommended way is to download  
>>>>> DarwinPorts-1.3.1-10.4.dmg from http://svn.macosforge.org/ 
>>>>> repository/macports/downloads/Darwinports-1.3.1/
>>>>
>>>> That's the one I took.
>
>>> However, the real question is why the DP version of libiconv  
>>> didn't work for you. Why do you have a PPC /opt/local/lib/ 
>>> libiconv.dylib on a i386 system?
>>
>> Actually, I don't understand why is it...
>> I have a fresh XCode 2.4 install (from Apple Website) and I  
>> successfully selfupdated macports (which require compiling and  
>> which was successfull in using -arch i686). By compiling apache2  
>> dependencies, it compilled several packages like expat and I don't  
>> remember others., everything went right, so libiconv seems to  
>> brings out some problems on my machine. If you want me to try  
>> something to check, do not hesitate because I'm stuck...
>
> If you haven't already, I'd try completely removing MacPorts's  
> libiconv and rebuilding it, see what happens. Something like...
>
> sudo port -f uninstall libiconv
> sudo port clean --all libiconv
> sudo port -v install libiconv
>
>
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users
>