Hi,

I would still like to cross compile hdf5 against x86_84 w/uClibc

I have managed to get passed the configuration stage but now. I get the 
following:
===============================================================
LD_LIBRARY_PATH="$LD_LIBRARY_PATH`echo  |                  \
        sed -e 's/-L/:/g' -e 's/ //g'`"                               \
 ./H5make_libsettings > H5lib_settings.c  ||                               \
    (test $HDF5_Make_Ignore && echo "*** Error ignored") ||          \
    (rm -f H5lib_settings.c ; exit 1)
/bin/sh: ./H5make_libsettings: /lib/ld64-uClibc.so.0: bad ELF interpreter: No 
such file or directory
make[3]: *** [H5lib_settings.c] Error 1
Makefile:1682: recipe for target 'H5lib_settings.c' failed
========================================================================

This is because you trying to execute a binary built for my target on my build 
host.  :(
I found the following in your Makefile:
===== src/Makefile snippet ============================================
In one case you are running an executable to generate a  "C"  file  :(
# Build configuration header file generation
# The LD_LIBRARY_PATH setting is a kludge.
# Things should have been all set during H5make_libsettings making.
# Remove the generated .c file if errors occur unless HDF5_Make_Ignore
# is set to ignore the error.
H5lib_settings.c: H5make_libsettings$(EXEEXT) libhdf5.settings
        LD_LIBRARY_PATH="$$LD_LIBRARY_PATH`echo $(LDFLAGS) |                  \
                sed -e 's/-L/:/g' -e 's/ //g'`"                               \
        $(RUNSERIAL) ./H5make_libsettings$(EXEEXT) > $@  ||                     
          \
            (test $$HDF5_Make_Ignore && echo "*** Error ignored") ||          \
            ($(RM) $@ ; exit 1)

=================================================================

Can you generate C files with a portable scripting language such as PERL ?

Can I proceed without this?  
I will be building for embedded linux.
I can setup LD_LIBRARY_PATH manually.

Or in some cases, I will do a static build with my application.

Looks like I will have a similar problem with:  H5detect.c  which claims to 
generate  "native.c"
But instead I see  "


# Number format detection
# The LD_LIBRARY_PATH setting is a kludge.
# Things should have been all set during H5detect making.
# Remove the generated .c file if errors occur unless HDF5_Make_Ignore
# is set to ignore the error.
H5Tinit.c: H5detect$(EXEEXT)
        LD_LIBRARY_PATH="$$LD_LIBRARY_PATH`echo $(LDFLAGS) |                  \
                sed -e 's/-L/:/g' -e 's/ //g'`"                               \
        $(RUNSERIAL) ./H5detect$(EXEEXT) > $@  ||                               
\
            (test $$HDF5_Make_Ignore && echo "*** Error ignored") ||          \
            ($(RM) $@ ; exit 1)

------------------------------------------------------------------------
May, I use  "HDF5_Make_Ignore"  to get around this for now?

What are the side effects?


Cheers,
Ernest


_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5

Reply via email to