This a packaging question, and belongs on fink-devel.

On 6/2/12 5:38 AM, Peter Dyballa wrote:
> Hello!
> 
> I am preparing ImageMagick 6.7.7 built with GCC >= 4.4. Build succeeds on Mac 
> OS X 10.6.8 in 32 bit with GCC 4.6.3 but *seems* to fail on Mac OS X 10.5.8 
> with GCC 4.6.3 because of:
> 
>       - Depends line is: imagemagick2-shlibs (= 6.7.7-2-1), gcc44 | gcc45 | 
> gcc46 | gcc47, lcms-shlibs (>= 1.11-1), libtiff-shlibs (>= 3.6.1-3), 
> libjasper.1-shlibs (>= 1.900.1-1), libpng14-shlibs, libdjvulibre21-shlibs (>= 
> 3.5.21-1003), libjpeg8-shlibs, fontconfig2-shlibs (>= 2.4.1-1), expat1-shlibs 
> (>= 2.0.0-1), bzip2-shlibs (>= 1.0.2-2), libxml2-shlibs (>= 2.6.30-1), 
> libiconv (>= 1.11-1), freetype219-shlibs (>= 2.3.5-1), libjbig-shlibs, 
> ghostscript | ghostscript, openexr, libwmf-shlibs (>= 0.2.8.4-2), x11-shlibs, 
> darwin (>= 9-1)
>       Writing control file...
>       

Why are you doing Depends: gcc44 | gcc45 | gcc46 | gcc47 ?

1) They're not BuildDependsOnly packages, but normally the only packages
that Depend on them do so to run their compilers.

2) The only time the "gcc44 | gcc45 | gcc46 | gcc47" construction is
legitimate is when you don't link to their libraries, e.g. a package
just wants "a gfortran" to build.

3) If you're in fact linking to their libraries, it is COMPLETELY WRONG
to have gcc44-shlibs | gcc45-shlibs | gcc46-shlibs | gcc47-shlibs,
because they install libraries with different install_names, and thus
cannot be swapped as dependencies.  Pick gcc47-shlibs and just use that.

>       Validating .deb dir /sw/build.build/root-imagemagick-6.7.7-2-1...
>       Error: The -framework flag may get munged by libtool. See the gcc 
> manpage for information about passing multi-word options to flags for 
> specific compiler passes.
>               Offending file: 
> /sw/lib/ImageMagick-6.7.7/modules-Q16/coders/pango.la
>               Offending line: inherited_linker_flags='  -fopenmp -pthread 
> -framework Carbon'
>       Removing runtime build-lock...
>       Removing build-lock package...
> 
> 



The issue is not Carbon, as such.  The issue is the use of '-framework
Carbon' instead of '-Wl,-framework,Carbon' in inherited_linker_flags.

<snip>

-- 
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/2012/02/21/got-job/

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to