[Fink-users] compiling: qt3-3.3.8-2000 failed

2010-05-16 Thread frj0
Hi, I've a problem with update qt3. And I don't found any information on the FAQ nor on the users-list. Can you help me, please. Thank's /bin/mv -f libqui.1.0.0.dylib libqui.dylib libqui.1.dylib libqui. 1.0.dylib ../../../lib/ cd designer make -f Makefile

Re: [Fink-users] compiling: qt3-3.3.8-2000 failed

2010-05-16 Thread Alexander Hansen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/16/10 6:02 AM, frj0 wrote: Hi, I've a problem with update qt3. And I don't found any information on the FAQ nor on the users-list. Can you help me, please. Thank's /bin/mv -f libqui.1.0.0.dylib libqui.dylib libqui.1.dylib libqui.

Re: [Fink-users] compiling: qt3-3.3.8-2000 failed

2010-05-16 Thread François Giron
Le 16 mai 10 à 15:13, Alexander Hansen a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/16/10 6:02 AM, frj0 wrote: Hi, I've a problem with update qt3. And I don't found any information on the FAQ nor on the users-list. Can you help me, please. Thank's /bin/mv -f

[Fink-users] versions hold in fink

2010-05-16 Thread Oliver Cordes
Hi, I'm looking for a mechanism to force fink not to update some packages. Is this possible? I know that due to some dependencies I cannot update other packages as well, but this is a small price to pay, because the update e.g. python-sip will break the usaage of other packages python-qt4 ...

Re: [Fink-users] versions hold in fink

2010-05-16 Thread Alexander Hansen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/16/10 5:16 PM, Oliver Cordes wrote: Hi, I'm looking for a mechanism to force fink not to update some packages. Is this possible? I know that due to some dependencies I cannot update other packages as well, but this is a small price to pay,

Re: [Fink-users] Failed: phase compiling: mono-2.6.1-3 failed

2010-05-16 Thread Benjamin Reed
2010/3/24 Benjamin Reed rangerr...@befunk.com: It is a problem unique to 10.5/ppc that I have not been able to figure out yet.  I have a bug open to the mono folks but have been unable to get traction on figuring out how to fix it.  It's deep in powerpc assembly, which I am nowhere near