Libraries have to meet several requirements to be prebound:
* all dependencies must be prebound * must use two-level namespace * can't have undefined symbols
Fink's prebinding support fortunately does all the hard work, maintainers just have to meet the above requirements. Simply setting "SetLDFLAGS: -no-undefined" will allow many libtool based packages to be prebound, but it doesn't always work. Sometimes there really are undefined symbols that can't be avoided or the two-level namespace causes conflicts with another library.
So these conflicts are only seen when linking another application with this shared library and potentially another one? So is it correct to say that the problem is that you can't tell if you built a good package just seeing if the package compiles, but you have to wait to see if any packages that depend on it work?
Hope that helps.
Yes, definitely. That's some good info.
Blair
-- Blair Zajac <[EMAIL PROTECTED]> Plots of your system's performance - http://www.orcaware.com/orca/
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
