Due to my mistake a part of the communication felt outside the mailing list. Maybe it can help others, so I'd like to share the information with you.
I wrote:
@Mike, thanks a lot. With your patches I was able to build libsigc++.
I
continued building glibmm (see attached patch and spec file). During
the build it was trying to use libsigc-2.0 from my host system (9.04),
after temporary moving this lib file I was able to build it. However I
cannot figure out why it's trying to use the lib from my host system.
After building glibmm, I started with gtkmm (see attachment
for modified spec file). Here I run into the same problem, but this time
moving the file temporary wasn't sufficient.
With libsigc++ on my host system and when temporary moved libsigc++ from my host system I get the same result:
make[3]: Entering directory `/home/***/***/ltib/rpm/BUILD/gtkmm-2.4.5/tools/extra_defs_gen'
/bin/bash
../../libtool --mode=link g++ -g -O2 -Wall -o generate_extra_defs
generate_defs_gtk.o -L/home/***/***/ltib/rootfs/usr/lib
-lglibmm-2.4 -lsigc-2.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0
-lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0
-lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0
-lglibmm_generate_extra_defs-2.4
libtool: link: warning: library `/home/***/***ltib/rootfs/usr/lib/
libglibmm-2.4.la' was moved.
libtool: link: warning: library `/home/***/***/ltib/rootfs/usr/lib/
libsigc-2.0.la' was moved.
libtool: link: warning: library `/home/***/***ltib/rootfs/usr/lib/
libglibmm_generate_extra_defs-2.4.la' was moved.
libtool: link: warning: library `/home/***/***ltib/rootfs/usr/lib/
libglibmm-2.4.la' was moved.
libtool: link: warning: library `/home/***/***ltib/rootfs/usr/lib/
libsigc-2.0.la' was moved.
libtool: link: warning: library `/home/***/***ltib/rootfs/usr/lib/
libglibmm_generate_extra_defs-2.4.la' was moved.
g++ -g -O2 -Wall -o generate_extra_defs generate_defs_gtk.o -L/home/***/***/ltib/rootfs/usr/lib /home/***/***/ltib/rootfs/usr/lib/
libglibmm-2.4.so /home/***/***/ltib/rootfs/usr/lib/
libsigc-2.0.so
-lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0
-lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype
-lfontconfig /home/***/***/ltib/rootfs/usr/lib/
libglibmm_generate_extra_defs-2.4.so /usr/lib/
libsigc-2.0.so -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -Wl,--rpath -Wl,/home/***/***/ltib/rootfs/usr/lib -Wl,--rpath -Wl,/home/***/***/ltib/rootfs/usr/lib
arm-none-linux-gnueabi-g++: error: /usr/lib/
libsigc-2.0.so: No such file or directory
Some other topics gave me a hint, so I added the following line in the spec file. But with no result.
perl -pi -e 's,^sys_lib_search_path_spec=.*,sys_lib_search_path_spec=,' libtool
Your help is very much appreciated,
Br,
Tom
Mike wrote back to me:
> @Mike, thanks a lot. With your patches I was able to build libsigc++.
>
> I continued building glibmm (see attached patch and spec file). During the
> build it was trying to use libsigc-2.0 from my host system (9.04), after
> temporary moving this lib file I was able to build it. However I cannot
> figure out why it's trying to use the lib from my host system.
This is usually indicative of some spec files not explicitly removing
the *.la files during install. So if a library that glibmm depends on
has a *.la file present in the rootfs, it will have a host path in it,
so libtool tries to use it. The only solution is to 'find roortfs
-name *.la' to find the offending files and add the delete routine to
the end of the install stage for that spec file:
find $RPM_BUILD_ROOT/%{pfx}/%{_
prefix}/lib/ -name "*.la" | xargs rm -f
You can delete them manually for a quick fix.
Oh, please keep replies to the list. I'm just a volunteer.
---------------------
Starting fresh this morning, I followed Mike's tips and got it all working (libsigc++, glibmm and gtkmm).
For those interested see attachments for patch and spec files.
Br,
Tom
gtkmm.spec