Hi all.
Today I have enough free time to spent it for LEAF toolchain.
Now I finished very basic rework on it, it looks like now it should
successfully compile C applications and has working C++ compiler w/o c++
libraries (I planned to replace libstdc++ to uClibcpp). Now compiler has
native architecture - so it'll be no pain with cross-compilation in
future and it'll be easy to build all for new architectures that are
binary-incompatible with x86. Also it reduces count of ugly tricks in
toolchain.
I updated dropbear package for compiling on new toolchain - it looks
like all is OK, and executable is working (in chroot of course - I
didn't build 'native' uClibc libraries that are working in toolchain place).
So now if anybody will have time to fix packages - welcome, I'll be glad
for help. It's preferred if building system will be x64 - it's much
easier to check if package is built right.
In other case - use ldd to verify if executable is linked with uClibc,
not with system libs. It's output should look like:
# ldd dbclient
libgcc_s.so.1 =>
/path-to-old-LEAF-buildenv/staging/lib/libgcc_s.so.1 (0xf776c000)
libc.so.0 => /path-to-old-LEAF-buildenv/staging/lib/libc.so.0
(0xf7723000)
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0xf7784000)
------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook
in minutes. BlackBerry App World™ now supports Android™ Apps
for the BlackBerry® PlayBook™. Discover just how easy and simple
it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
