On Sun, Oct 30, 2011 at 08:59:12PM +0100, Peter Dyballa wrote:
> 
> Am 30.10.2011 um 20:21 schrieb Jack Howarth:
> 
> > ps The fact that you end up linking in from /opt/local strongly suggests 
> > that the emacs configure is looking in /opt/local
> > for includes and shared libs which effectively causes fink to be mixed with 
> > MacPorts which simply won't work.
> 
> How often do I need to state that I was using *some* modern compiler to build 
> a (MacPorts affiliated, because its the only provider of Open Source 64-bit 
> binaries) 64-bit version of GNU Emacs on purpose? And just as I imagined only 
> a very small number of "Fink files" was used, all parts of the compiler 
> packages. This worked pretty well in the 32-bit world of my G4 hardware.

Pater,
   As David noted, mixing MacPorts and fink is simply too ill-defined to 
support. Each distribution struggles
enough with coherency in its own package set with the extra burden of pinning 
down subtle differences in the
configure options used to build the same shared libraries or where one 
distribution may be slightly ahead
or behind in the upstream version being used. Any of these could cause 
unresolved symbols, etc. This issue
isn't unique to fink and MacPorts. Fedora users for instance have to avoid 
mixing the multiple third party
yum repos (such as rpmfusion and atkmods) where each may build the same code 
differently.
            Jack

> 
> --
> Greetings
> 
>   Pete
> 
> Don't just do something, sit there.

------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World™ now supports Android™ Apps 
for the BlackBerry® PlayBook™. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________
Fink-users mailing list
[email protected]
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to