I'm trying HDF5 1.10.1, and new H5PL* routines are of particular interest for me -- thanks for adding those!
H5PLappend/H5PLprepend seem to work fine. However, I'm puzzled by the following. In my Windows system I have
>set HDF5_PLUGIN_PATH
HDF5_PLUGIN_PATH=E:\ACD\utils\lcuvms
but both
H5PLsize and H5PLget(0, ...) return zero.
It is expected that the contents of HDF5_PLUGIN_PATH loaded during library initialization are exposed through H5PLsize/H5PLget. Is it (hopefully) a temporary bug?
Best wishes,
Andrey Paramonov
···
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
I added a check for initial paths in the plugin.c test and verfied that the table is initialized with the settings from the HDF5_PLUGIN_PATH env var.
Allen
···
On Wednesday, July 26, 2017 3:54:14 AM CDT Андрей Парамонов wrote:
Hello!
I'm trying HDF5 1.10.1, and new H5PL* routines are of particular
interest for me -- thanks for adding those!
H5PLappend/H5PLprepend seem to work fine. However, I'm puzzled by the
following. In my Windows system I have
>set HDF5_PLUGIN_PATH
HDF5_PLUGIN_PATH=E:\ACD\utils\lcuvms
but both
H5PLsize and H5PLget(0, ...) return zero.
It is expected that the contents of HDF5_PLUGIN_PATH loaded during
library initialization are exposed through H5PLsize/H5PLget. Is it
(hopefully) a temporary bug?
I added a check for initial paths in the plugin.c test and verfied that the table is initialized with the settings from the HDF5_PLUGIN_PATH env var.
Maybe the problem is in my OS (Windows 10)?
However I do not completely dismiss the possibility of my erroneous code. Is there a minimal test program I could run to check?
Best wishes,
Andrey Paramonov
···
On Wednesday, July 26, 2017 3:54:14 AM CDT Андрей Парамонов wrote:
Hello!
I'm trying HDF5 1.10.1, and new H5PL* routines are of particular
interest for me -- thanks for adding those!
H5PLappend/H5PLprepend seem to work fine. However, I'm puzzled by the
following. In my Windows system I have
>set HDF5_PLUGIN_PATH
HDF5_PLUGIN_PATH=E:\ACD\utils\lcuvms
but both
H5PLsize and H5PLget(0, ...) return zero.
It is expected that the contents of HDF5_PLUGIN_PATH loaded during
library initialization are exposed through H5PLsize/H5PLget. Is it
(hopefully) a temporary bug?
Best wishes,
Andrey Paramonov
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Allen
On Thursday, July 27, 2017 9:45:48 AM CDT Андрей Парамонов wrote:
Hi Allen!
27.07.2017 17:08, Allen Byrne пишет:
> I added a check for initial paths in the plugin.c test and verfied that the table is initialized with the settings from the HDF5_PLUGIN_PATH env var.
Maybe the problem is in my OS (Windows 10)?
However I do not completely dismiss the possibility of my erroneous
code. Is there a minimal test program I could run to check?
Best wishes,
Andrey Paramonov
> On Wednesday, July 26, 2017 3:54:14 AM CDT Андрей Парамонов wrote:
>> Hello!
>>
>> I'm trying HDF5 1.10.1, and new H5PL* routines are of particular
>> interest for me -- thanks for adding those!
>>
>> H5PLappend/H5PLprepend seem to work fine. However, I'm puzzled by the
>> following. In my Windows system I have
>> >set HDF5_PLUGIN_PATH
>> HDF5_PLUGIN_PATH=E:\ACD\utils\lcuvms
>> but both
>> H5PLsize and H5PLget(0, ...) return zero.
>> It is expected that the contents of HDF5_PLUGIN_PATH loaded during
>> library initialization are exposed through H5PLsize/H5PLget. Is it
>> (hopefully) a temporary bug?
>>
>> Best wishes,
>> Andrey Paramonov
>>
>>
>
>
>
Allen
On Thursday, July 27, 2017 9:45:48 AM CDT Андрей Парамонов wrote:
Hi Allen!
27.07.2017 17:08, Allen Byrne пишет:
I added a check for initial paths in the plugin.c test and verfied that the table is initialized with the settings from the HDF5_PLUGIN_PATH env var.
Maybe the problem is in my OS (Windows 10)?
However I do not completely dismiss the possibility of my erroneous
code. Is there a minimal test program I could run to check?
Best wishes,
Andrey Paramonov
On Wednesday, July 26, 2017 3:54:14 AM CDT Андрей Парамонов wrote:
Hello!
I'm trying HDF5 1.10.1, and new H5PL* routines are of particular
interest for me -- thanks for adding those!
H5PLappend/H5PLprepend seem to work fine. However, I'm puzzled by the
following. In my Windows system I have
>set HDF5_PLUGIN_PATH
HDF5_PLUGIN_PATH=E:\ACD\utils\lcuvms
but both
H5PLsize and H5PLget(0, ...) return zero.
It is expected that the contents of HDF5_PLUGIN_PATH loaded during
library initialization are exposed through H5PLsize/H5PLget. Is it
(hopefully) a temporary bug?
Best wishes,
Andrey Paramonov
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.