Martin Buchholz <martin(a)xemacs.org> writes:
No, we should not trust the output of `esd-config --libs`. We
should
be paranoid and test it, as my pseudocode non-working esd config patch
tries to do.
Maybe we should, but I really don't like where this going. What is
next, we check for every single header file we include?
Potato is not released yet. Let's try not working around other peoples
bugs when they still can be fixed.
Jan> Fix your setup. Or even better file a bug with your
Jan> distribution/vendor/sys-admin. Unfortunately configure failures are
Jan> always very indirect :-(
I disagree. The esd-config utility is shipped with the runtime
package, not the development package, which need not be installed.
Redhat 6.0:
urysohn:~> rpm -qf `which esd-config`
esound-devel-0.2.12-4
Are there any other distributions which get this wrong? In a released version?
Jan