On Tue, Jun 29, 2010 at 10:48 PM, CHEN XUEQIN <che...@star-net.cn> wrote: > Hi Mabeett: > > I have found the solution of SDK absolution path problem. > Just create a temporary user and compile the SDK, then remove > the temporary user and his home directory. > > The key is the absolute path of SDK buiding host. For example, > the official sdk is built in path: > /home/agb/openwrt/ppc44x/staging_dir/toolchain-powerpc_gcc4.2.4/lib/gcc/powerpc-linux-uclibc/4.2.4/ > > When I use this sdk in my ubuntu host, it works fine. Run > cli command "powerpc-linux-gcc -print-search-dirs", gcc search > library in multi path. The final two are > > /home/agb/openwrt/ppc44x/staging_dir/toolchain-powerpc_gcc4.2.4/powerpc-linux-uclibc/lib/powerpc-linux-uclibc/4.2.4/ > /home/agb/openwrt/ppc44x/staging_dir/toolchain-powerpc_gcc4.2.4/powerpc-linux-uclibc/lib/. > > The two path doesn't exist in my ubuntu host, so gcc search library > and header file in my host path such as > home/chenxq/openwrt/OpenWrt-SDK-ppc44x-for-Linux-x86_64/staging_dir/toolchain-powerpc_gcc4.2.4/bin/../lib/gcc/powerpc-linux-uclibc/4.2.4/. > And everything is ok. > > If my ubuntu host has the directory > /home/agb/openwrt/ppc44x/staging_dir/toolchain-powerpc_gcc4.2.4/powerpc-linux-uclibc/lib/powerpc-linux-uclibc/4.2.4/ > and don't have read permission for user who compiles > problem. The gcc will report error and quit. That's the absolute path > problem. > When building sdk in a temporary user, then remove the compiling > directory, > gcc will use relative path.
I found an simplier way. 1) work in /usr/src/my_dir/ svn there, compilation, SDK, etc 2) When you want to use the SDK, with *any* computer, create the needed(s) symbolic link(s) for completing the absolute path. > > > Regards, > Chen Xueqin > > > 于 2010年06月10日 09:50, MAbeeTT 写道: > >> On Wed, Jun 9, 2010 at 10:44 PM, CHEN XUEQIN<che...@star-net.cn> wrote: >>> >>> Hi mabeett: >>> >>> I have the same problem with Backfire's SDK which I have asked >>> in this maillist named " How openwrt team build SDK which released >>> officially on openwrt.org"。I haven't resolved this problem up till >>> now. >> >> >> Minuts ago I saw it. >> >> Did you open a ticket in the tracker? >> >> Does somebody where to start for fixing it? >> >> [...] >> >> >> > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > -- .::MAbeeTT::. mabeett [at] gmail [ dot] com some time ago: mtspcchaiaeia [at] gmail [dot] com _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
