16.10.2012 18:50, Yves Blusseau пишет: > Le 16/10/2012 17:42, Yves Blusseau a écrit : >> Le 16/10/2012 17:33, Andrew a écrit : >>> 16.10.2012 18:17, Yves Blusseau пишет: >>>> Le >>>> It's works ! >>>> I have compiled bash, busybox and openssh with the x86_64 toolchain and >>>> install them into the staging dir. Then i chroot to staging dir and bash >>>> and ssh commands works like a charm (they find their libraries). >>>> >>>> What i do to compile/install the packages is: >>>> 1) created a link in the staging directory $staging_dir/usr/lib64 -> >>>> staging_dir/usr/lib >>>> 2) created a link in the build directory: $buildir/$package/usr/lib64 -> >>>> $buildir/$package/usr/lib so when the package is installed all the 64 >>>> bits libraries are put in the lib directory >>>> >>>> For 1) we can do it automaticaly by buildtool.pl when the staging >>>> directory is created >>>> For 2) we need to add a ln command to add the link in every package that >>>> can create file under /usr/lib64 >>>> >>>> Are you ok with this ? >>>> >>>> Yves >>>> >>> Hi. >>> Do we actually need to do anything in build directory? I think that >>> it'll be enough to make symlink into staging dir, and all files that are >>> placed into /usr/lib64 will be placed into /usr/lib. >> Yes, look at the openssl package: >> after the make install: >> make -C $(SOURCE_DIR) INSTALL_PREFIX=$(TARGET_DIR) install_sw >> it does: >> -chmod -R 755 $(TARGET_DIR)/usr/lib/* >> -$(BT_STRIP) $(BT_STRIP_LIBOPTS) $(TARGET_DIR)/usr/lib/*.so >> -$(BT_STRIP) $(BT_STRIP_LIBOPTS) $(TARGET_DIR)/usr/lib/engines/*.so >> but in our case the /usr/lib doesn't exists (only the /usr/lib64) >> because make install will install all the libraries in /usr/lib64. >> >> The best will be to have a configure parameter that force to put all the >> libraries in /usr/lib instead of /usr/lib64 > I found how to do it with configure for openssl: --libdir=lib which > force to use /usr/lib as directory for dynamic libraries. > > Yves Good, it'll be enough for successful cross-compiling.
P.S. maybe we should place some common configure parameters (--host, --build, --libdir and possible some other) into single variable in masterinclude.mk? ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel