kile-devel doesn't start

[Ryan Schmidt]

On Nov 29, 2010, at 08:08, Thomas Schneider wrote:

> Well, I'm sorry that this is now difficult to sort out, but I really couldn't tell in the first place that the different sources would interfere with each other.

Ideally they wouldn't, but unfortunately in some cases they seem to, so the best answer we can give is don't mix and match. If you use MacPorts, don't use Fink or Homebrew, and don't put things in /usr/local or /Library/Frameworks.


>> Remove /Library/Frameworks/phonon.framework as well.
> 
> This yields:
> 
> $ kile.app/Contents/MacOS/kile
> dyld: Library not loaded: phonon.framework/Versions/4/phonon
>  Referenced from: /opt/local/lib/libkhtml.5.dylib
>  Reason: image not found
> Trace/BPT trap

Ok, this proves that /opt/local/lib/libkhtml.5.dylib (which according to "port provides" is provided by the kdelibs4 port) has been inadvertently linked to your standalone phonon framework, instead of with the phonon in MacPorts. Now that the standalone phonon framework is gone, rebuilding kdelibs4 ("sudo port -n upgrade --force phonon") should rebuild it properly. Though there may be other ports in addition to kdelibs4 in the same boat, which you'll discover as you go along, which would need to be rebuilt as well.


>> Remove all the Qt frameworks. I don't know what the remaining 11 are since I haven't seen their names.

> The frameworks remaining in /Library/Frameworks all have to do with other applications:
> 
> GHC.framework
> HPDeviceModel.framework
> HPPml.framework
> HPServicesInterface.framework
> HPSmartPrint.framework
> HaskellPlatform.framework
> MacFUSE.framework
> TSLicense.framework
> WesternDigital
> cisco-vpnclient.framework
> gecode.framework

Ok. The GHC and Haskell frameworks are part of the Glasgow Haskell Compiler; if you ever want to install any Haskell software with MacPorts you may have problems unless you remove these.

The HP frameworks are probably for a Hewlett-Packard printer, for which we don't have any software in MacPorts that I know of so thees should be fine.

The MacFUSE framework is on my system as well. I don't remember why I have it. MacPorts has a version of MacFUSE too, but I don't think it works anymore.

Don't know what TSLicense or gecode are. Don't think we have anything similar in MacPorts so these are probably fine.

The WesternDigital and cisco-vpnclient frameworks probably won't interfere with MacPorts either.


>> Linking to things in /System/Library/Frameworks is normal and expected. Linking to things in /Library/Frameworks may be problematic. (Or it may not, if that framework was installed by MacPorts.)
> 
> OK.
> 
> Is it indicated to start completely from scratch, i.e.:
> 
> * completely get rid of the previous Qt installation, 
> * completely erase the Fink installation including all installed packages and their entries in the Library and similar places,
> * probably do the same for MacPorts, and
> * start from a fresh MacPorts installation?

That would be one way to go, or you could just rebuild ports as you find ones that need to be rebuilt. Complete uninstallation and reinstallation might be simuler, if you don't have a lot of ports and/or if you have a fast Mac, as it would remove any doubt that everything has been rebuilt.


> If so, how do I clean up properly after Qt, Fink, and MacPorts?

For Qt and Fink, you'll have to ask them. For MacPorts, I see you already found the uninstall instructions in the guide.

http://guide.macports.org/chunked/installing.macports.uninstalling.html