Eric:

I agree.  And I had to add yet another package to my system, through Fink which 
pkgconfig picked up nicely: libIDL2.  Now the build 'crashes' on building 
mozilla with an error on line 467 of gtk2xtbin.c:

'GMainContext' undeclared.

This did not happen on my builds of M107.  Maybe I need to apply the macosx08 
patches?

BTW, I will be out of the office next week and may not be able to test any 
builds.  Only time will tell.

James McKenzie

-----Original Message-----
From: Eric Hoch <[EMAIL PROTECTED]>
Sent: Jun 10, 2005 8:10 AM
To: [email protected]
Subject: Re: [porting-dev] Mac OS X: Building SRC680m108 - are any patches 
necessary for a successful build?

Hi James, 
Am Fri, 10 Jun 2005 06:41:23 -0700, schrieb James McKenzie:
> Eric Hoch wrote:
> 
>> So there is no bug in gnucopy but for me one in OOo. But so far
>> 
>> nobody seemed to agree with me and all are happy with using gnu-copy. 
>>  
> Add my vote to eliminate the need for gnu-copy.  I build mine 
> from source (it now builds for Darwin 8 AKA Tiger.) 


> However there is no additional functionality added by using gnu-copy over 
> MacOSX cp.

Exactly. The additional functions that gnu-copy provides aren't 
used in the build process. The only problem is that Mac OS X cp and 
gnu-copy use different parameters for the same action which causes 
the coders to add additional .IFDEFs. 

But so far I can only see one change needed in moz and in 
instsetoo_native where two times nearly at the end gnu-cp is 
needed. 

The change in instsetoo_native/util/makefile.mk needs to be done 
after line 185. See the post from Tino today. There he quoted my 
mail that has the needed changes. 

The other site is that when using gnu-copy the source code is a bit 
cleaner and more "plattform" independent. 

Regards, 
Eric Hoch

-- 
## Ansprechpartner Anwenderunterst�tzung, users-Mailingliste, MacOSX
## de.OpenOffice.org - Office f�r MacOS X, Linux, Solaris & Windows
## Openoffice.org - ich steck mit drin!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to