Fink

--
Unstable:	0.8.4-11
gstinfo.c: In function `_gst_debug_nameof_funcptr':
gstinfo.c:1044: error: `Dl_info' undeclared (first use in this function)
gstinfo.c:1044: error: (Each undeclared identifier is reported only once
gstinfo.c:1044: error: for each function it appears in.)
gstinfo.c:1044: error: parse error before "dlinfo"
gstinfo.c:1054: warning: implicit declaration of function `dladdr'
gstinfo.c:1054: error: `dlinfo' undeclared (first use in this function)
make[4]: *** [libgstreamer_0.8_la-gstinfo.lo] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
### execution of make failed, exit code 2

--
Hardware Overview:
Machine Model:	Power Mac G5
CPU Type:	PowerPC 970  (2.2)
Number Of CPUs:	2
CPU Speed:	2 GHz
L2 Cache (per CPU):	512 KB
Memory:	1.5 GB
Bus Speed:	1 GHz
Boot ROM Version:	5.1.4f0

--
Package manager version: 0.24.1
Distribution version: 0.7.1.rsync
Mac OS X version: 10.3.8
December 2002 Developer Tools or later
gcc version: 3.3
make version: 3.79
Feedback Courtesy of FinkCommander

Kyle Wheeler said:
>
> When I attempt to run "fink update gnome-vfs2" I get the following
> errors:

I see only warnings here.

> [kyle@... ~]$ fink update gnome-vfs2
>
> WARNING: The package gnome-vfs2 Depends on popt,
>          but popt only allows things to BuildDepend on it.
[...]
> The following package will be removed:
>  openssl097-dev
> Do you want to continue? [Y/n]
>
> Why on earth would it CONFLICT with openssl?

It actually *Build*Conflicts with openssl0997-*dev* (the -dev are
compile-time headers). You chose gnome-vfs2 not gnome-vfs2-ssl,
meaning you want the version with ssl disabled (why?).  Probably
gnome-vfs2* auto-detects openssl headers at compile-time: to avoid
linking to the ssl libs, the headers need to be not-present when the
package is being built.

> Why does it break the popt rules about BuildDepends?

Popt has a portability problem that prevents us from making a package
that both followed fink policy and worked. We chose the "make it work"
option, but that meant it (and by extension anything that used it) had
to break policy. Our popt was patched to fix the underlying problem a
few months ago, so if you install popt-1.7-5 you'll be all set with
it.  All the packages that had to break policy to use the old poopt
will still work, but they have to be manually updated back into
compliance. Which I just did for gnome-vfs2-2.6.1.1-16 (please always
mention version information in bug reports so we know what you're
talking about).

dan

-- 
Daniel Macks
dmacks@...
http://www.netspace.org/~dmacks