On Sun, 2009-07-05 at 21:08 +0200, Vivien Malerba wrote:

> 
> 
> 
> 2009/7/1 Bas Driessen <[email protected]>
> 
>         Hello,
>         
>         I am trying to compile branch LIBGDA_4.0 On the make install I
>         get the following error:
>         
>         ..
>         ..
>         
>         usr/sbin:/sbin:/home/bas/bin:/sbin" ldconfig
>         -n /home/bas/work/libgda/lib
>         ----------------------------------------------------------------------
>         Libraries have been installed in:
>            /home/bas/work/libgda/lib
>         
>         If you ever happen to want to link against installed libraries
>         in a given directory, LIBDIR, you must either use libtool, and
>         specify the full pathname of the library, or use the
>         `-LLIBDIR'
>         flag during linking and do at least one of the following:
>            - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
>              during execution
>            - add LIBDIR to the `LD_RUN_PATH' environment variable
>              during linking
>            - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
>            - have your system administrator add LIBDIR to
>         `/etc/ld.so.conf'
>         
>         See any operating system documentation about shared libraries
>         for
>         more information, such as the ld(1) and ld.so(8) manual pages.
>         ----------------------------------------------------------------------
>         test -z "/home/bas/work/libgda/share/libgda-4.0/dtd"
>         || /bin/mkdir -p "/home/bas/work/libgda/share/libgda-4.0/dtd"
>         /usr/bin/install -c -m 644 libgda-array.dtd
>         libgda-paramlist.dtd libgda-server-operation.dtd
>         '/home/bas/work/libgda/share/libgda-4.0/dtd'
>         test -z "/home/bas/work/libgda/include/libgda-4.0/libgda"
>         || /bin/mkdir -p
>         "/home/bas/work/libgda/include/libgda-4.0/libgda"
>         /usr/bin/install -c -m 644 gda-marshal.h gda-enum-types.h
>         gda-attributes-manager.h gda-batch.h gda-blob-op.h
>         gda-column.h gda-config.h gda-connection-event.h
>         gda-connection.h gda-connection-private.h
>         gda-data-comparator.h gda-data-handler.h
>         gda-data-model-array.h gda-data-model.h gda-data-model-bdb.h
>         gda-data-model-dir.h gda-data-model-extra.h
>         gda-data-model-import.h gda-data-model-iter.h
>         gda-data-model-iter-extra.h gda-data-model-private.h
>         gda-data-access-wrapper.h gda-data-proxy.h gda-data-select.h
>         gda-debug-macros.h gda-decl.h gda-easy.h gda-enums.h
>         gda-holder.h gda-lockable.h gda-log.h gda-marshal.h
>         gda-meta-store.h gda-meta-struct.h gda-mutex.h
>         gda-quark-list.h gda-row.h gda-set.h gda-server-operation.h
>         gda-server-provider.h
>         '/home/bas/work/libgda/include/libgda-4.0/libgda'
>         /usr/bin/install: will not overwrite just-created
>         `/home/bas/work/libgda/include/libgda-4.0/libgda/gda-marshal.h' with 
> `gda-marshal.h'
>         make[2]: *** [install-gdaincludeHEADERS] Error 1
>         make[2]: Leaving directory `/home/bas/work/git/libgda/libgda'
>         make[1]: *** [install-am] Error 2
>         make[1]: Leaving directory `/home/bas/work/git/libgda/libgda'
>         make: *** [install-recursive] Error 1
>         [...@ams libgda]$ 
>         
>         
>         It appears that gda-marshal.h is listed twice. (highlighted in
>         bold above). Can this please get corrected so I can compile
>         and test the new GdaDataSelect feature?
> 
> I've just corrected this in git LIBGDA_4.0 branch. Can you check it?
> 
> The strange thing is that instead of one single long line which
> installs all the header files, when I run "make install" I get one
> line per header file installed, which is the reason I never found out
> about that bug...


That appears to work fine now.

Thanks for getting that organized,

Bas.
_______________________________________________
gnome-db-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-db-list

Reply via email to