Summary: | showstopper: impossible to use cdf file | ||
---|---|---|---|
Product: | [Applications] kst | Reporter: | Nicolas Brisset <nicolas.brisset> |
Component: | general | Assignee: | kst |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.x | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nicolas Brisset
2004-11-07 00:16:12 UTC
On Saturday 06 November 2004 18:16, Nicolas Brisset wrote: > Probably due to recent changes in datasources or the datawizard, I can't > load a .cdf file any longer ! It seems that the priority mechanism/source > detection is broken. The wizard indicates ASCII as source type even though > cdf returns 76 when the file has an extension .cdf and ascii shouldn't > return more than 75 ! Yes, I have checked that the cdf datasource has been > built, which by the way shows that the modification George made to the > --with-cdf configure switch was right :-) > > Help on this is highly appreciated as it is a showstopper for me :-( I had this happen too. I think your LD_LIBRARY_PATH/library cache/rpath setup is incorrect. Try deleting the CDF .so and use the .a instead. It will probably work then. Or set LD_LIBRARY_PATH or add to /etc/ld.so.conf to point to the directory with CDF libraries. Thanks for the tip :-) Indeed, the libs were in a non-standard location (/usr/local/cdf/lib) and adding /usr/local/cdf/lib to LD_LIBRARY_PATH solved the problem. I will close this bug, with only a suggestion : couldn't we remove a datasource from the list in kst settings when loading it gives an error like in this case ? Since I could see it, I assume it was correctly installed and configured. On Sunday 07 November 2004 03:59, Nicolas Brisset wrote:
> 09:59 ------- Thanks for the tip :-) Indeed, the libs were in a
> non-standard location (/usr/local/cdf/lib) and adding /usr/local/cdf/lib to
> LD_LIBRARY_PATH solved the problem. I will close this bug, with only a
> suggestion : couldn't we remove a datasource from the list in kst settings
> when loading it gives an error like in this case ? Since I could see it, I
> assume it was correctly installed and configured.
We dont' know it's a problem until we first try to use it. Therefore we log
an error to KstDebug and leave it as-is. It would be unfortunate to force
the user to exit Kst and reload after he fixes the problem anyway.
|