mozilla-dev fails to build

[Daniel Oberhoff]

Hi,

Ok, yes, I had lots of those darwin_8 thingies. While deinstalling  
openssl macports just broke (it seems the whole ports system depended  
on openssl) so now I had to shoot it and reinstall, and lost interest  
along the way :o (other things where more interesting ^^). Anyhow, I  
wanted the mozilla-dev to build the mugshot tracker, for which there  
is no osx version yet, and it uses gecko-sdk, which again bases on the  
mozilla-sdk.
Once I get back on track with this I will update here if it works.

Best

Daniel

Am 28.12.2007 um 16:44 schrieb Ryan Schmidt:

> On Dec 28, 2007, at 02:08, Daniel Oberhoff wrote:
>
>> I can't get mozilla-dev built. It gives lots and lots of errors. I  
>> started fixing some, but after an while I kinda though I'd first  
>> ask if anyone has succeeded with it before, so that maybe it's just  
>> a local misconfiguration. Among the things I fixed so far are:
>>
>> 1) some of the headers of the package confuse signal.h (they  
>> #define some things that mess up signal.h) so I had to move  
>> signal.h to the top of the include list in those cases.
>>
>> 2) the interface to freetype is broken. the mozilla-dev uses  
>> funtion pointers with non-const arguments, while ft2 seems to  
>> expect them to be with const arguments (moveto, lineto,  
>> cubicto...), so I added const qualifiers in the correesponding  
>> function declarations.
>>
>> another thing I didn't fix yet is NSOID being undefined in lots of  
>> places. I just couldn't find where it is defined. This only shows  
>> btw. when there is an array of NSOID defined. The compiler merilly  
>> compiles pointer statements (NSOID *).
>>
>> My system is osx leopard on a core2duo mbp. I took over the  
>> macports tree from my tiger installation, but that had no  
>> problems...so far :). I recently did selfupdate (to 1.6) and  
>> upgrade outdated successfully.
>
> mozilla and mozilla-devel ports are not being maintained, and appear  
> to be old. Why do you want to install mozilla 1.8b1?
>
> Migrating a MacPorts tree from Tiger to Leopard (or across any major  
> OS release version, or from one architecture processor to another)  
> can be problematic. In the case of moving from Tiger to Leopard, you  
> probably still have a lot of ports installed that have the  
> "darwin_8" variant. Examine "port installed" to see. You should  
> forcibly uninstall each of those (sudo port -f uninstall foo)  
> (making note of which other variants you selected), then reinstall  
> them (sudo port install foo +whatever), so they lose the now- 
> inappropriate darwin_8 variant and gain (if necessary) the darwin_9  
> variant.
>