Eric Knauel <email@example.com> writes:
> - I think there is a need for some machinery that helps to bring
> information acquired during the `./configure'-step back into the
> scope of pkg-def.scm. Load.scm, for example, should not hardcode
> the shared module extension to ".so", that's wrong on some
> platforms. (It's not clear to me whether this is only a cosmetical
> problem and or if it's harming functionality.) However, configure
> finds out about the correct extension and it would be smartish if
> the Packaging proposal describes a method for accessing arbitrary
> information from configure.
But this is wrong: load.scm should work on any platform so you cannot
obtain the extension from configure or any other tool that runs at
installation time. You really need to extract it from libtool's .la
file. I hope David Frese will write this functionality soon.