From: Paul O. <new...@ki...> - 2009-03-24 23:16:26
|
As far as I know, configure scripts don't look for libltdl using pkg-config infrastructutre, rather they assume libltdl.a is available in system lib directories. Try to set LDFLAGS and LIBS shell variables to -L/path/to/your/crosscompiled/libraries before running any configure script. For my foxboards I have foxcross script which looks like that: #!/bin/sh PATH=/usr/local/cris/cris-axis-linux-gnu/bin:/mnt/flash/usr/bin:$PATH \ CFLAGS="-fPIC -isystem /usr/local/cris/etrax/sys-include -I/mnt/flash/usr/include" \ CXXFLAGS="-fPIC -isystem /usr/local/cris/etrax/sys-include -I/mnt/flash/usr/include" \ LIBS="-L/mnt/flash/usr/lib -lltdl" \ LDFLAGS="-L/mnt/flash/usr/lib -lltdl" \ PKG_CONFIG_PATH=/mnt/flash/lib/pkgconfig \ bash Paul On Tue, 24 Mar 2009, Damiano Vittor wrote: > Hi thanks for you help. > When I compile libtools no .pc files are creater, I've created a new one > manually and added to PKG_CONFIG_PATH the right path.. "pkg-config > --cflags libtool" etc returns me now the right values for includes. > Sadly the problem remains. > Some other clues? > > Paul Osmialowski ha scritto: >> On Mon, 23 Mar 2009, Brian Gerkey wrote: >> >> >>> On Mar 23, 2009, at 8:12 AM, Damiano Vittor wrote: >>> >>> Note that pkg-config is not cross-compilation-aware. It will happily >>> find packages on the build system that are out outside of the host >>> system's toolchain. I've found that it's best to avoid the use of pkg- >>> config when cross-compiling. Alternatively, you could build your own >>> pkg-config for your toolchain, and adjust your PATH so that the new >>> pkg-config gets picked up. >>> >>> brian. >>> >> This can be easily fixed by setting PKG_CONFIG_PATH shell variable, .pc >> files for libraries are taken first from location pointed that way, then >> if not found already, pkg-config looks for them in /usr/lib/pkgconfig >> >> Paul >> >> ------------------------------------------------------------------------------ >> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are >> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and >> easily build your RIAs with Flex Builder, the Eclipse(TM)based development >> software that enables intelligent coding and step-through debugging. >> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> > > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > |