ufraw Not Build

David Evans devans at macports.org
Thu Jan 8 10:17:33 PST 2009


Altoine Barker wrote:
> /usr/bin/g++-4.0  -O2   -L/opt/local/lib -o ufraw ufraw.o libufraw.a
> -R/opt/local/lib -Wl,-framework -Wl,CoreFoundation -L/opt/local/lib
> -lexiv2 -lintl -lc -liconv -lz -lexpat   -L/opt/local/lib -lglib-2.0
> -lintl -liconv   -L/opt/local/lib -llcms    -L/opt/local/lib -lpng12 -lz
>   -L/opt/local/lib -lgtkimageview -lgtk-quartz-2.0 -lgdk-quartz-2.0
> -latk-1.0 -lgio-2.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo
> -lpangoft2-1.0 -lpango-1.0 -lm -lpixman-1 -lfontconfig -lexpat
> -lfreetype -lpng12 -lz -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl
> -liconv   -ltiff -ljpeg -lbz2 -lz  -lintl
> Undefined symbols:
>   "_CMCloseProfile", referenced from:
>       _uf_get_display_profile in libufraw.a(uf_gtk.o)
>   "_CMFlattenProfile", referenced from:
>       _uf_get_display_profile in libufraw.a(uf_gtk.o)
>   "_CMGetProfileByAVID", referenced from:
>       _uf_get_display_profile in libufraw.a(uf_gtk.o)
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[2]: *** [ufraw] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Warning: the following items did not execute (for ufraw):
> org.macports.destroot org.macports.build
> Error: Unable to upgrade port: 1
> </snip>
>
> I upgraded my XCode SDK to XCode 3.1.2 and the problem is the same. TIA
>
> -Altoine
>
Altoine -

>From this I assume that you are building against gtk2 +quartz variant as
the code referenced above is
only built in that case.   The offending symbols are from ColorSync Manager
provided by the ApplicationServices framework which is not referenced by
this link
command.

I just tried building the current ufraw port (0.15) in the gtk2 +quartz
environment
and was unable to reproduce your problem.  The corresponding link command
included the ApplicationServices framework.

So I wonder if you are using the latest version of ufraw?

Please try

sudo port selfupdate
sudo port clean --all ufraw
sudo port upgrade ufraw

and see if you still have the problem.  If so you should probably file a
ticket against ufraw
citing the details.

Dave


More information about the macports-users mailing list