On 7/30/10 3:25 PM, Jean-François Mertens wrote:
> 
> On 30 Jul 2010, at 20:49, Alexander Hansen wrote:
> 
>> I just selfupdated less than an hour ago and tried a build of qt4-x11 on
>> 10.5.8/i386.  I haven't finished my build yet, but with 'make' from
>> Xcode-3.1.4, I got
>>
>> "Separate debug info support disabled."
> So that seems to rule out a side effect of the change in kde4-buildenv...
> Remains to understand
> 1) how the same pkg on apparently identical machines
> leads to to different settings for this _ which more than probably do
> affect the deb...
> 2) make's seg-fault. I'll re--create a build-dir of my successfull build
> on 64bit, in order to do a diff of the 2 Makefiles
> 
>> After I verify that the build runs to completion, I'll try it again with
>> fink's make.
> I'd suggest it is probably not worthwhile: the problem here was independent
> of the make command used; both are 3.81.
> The interesting thing would be to compare with a make 3.82 ..
> 
>> I'm not sure why you had to use force-depends, since
>> qt4-x11 doesn't BuildDepend on it.
> 
> But a number of fink pkgs do depend on "make" (probably unjustified in a
> number of pkg/system_version configurations), and I don't want to
> recursively remove _ and then reinstall! _ a number of pkgs for
> such a small experiment!
> 

Sure, that makes sense.  I was just making sure that your *qt4* didn't
want it for some reason.

> Thanks a lot !
> 
> Jean-Francois
> 


-- 
Alexander Hansen
Fink User Liaison

------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to