Re: Cross compile click packages
Sascha Alexander Jopen <[email protected]>
| Newsgroups | gmane.network.routing.click |
|---|---|
| Message-ID | <[email protected]> |
But you installed click on the build machine into the same directory where it would be installed on the target/host machine, didn't you? If i compile the click base package with, say, --prefix=/usr, but install it with make install DESTDIR=/some/other/prefix this won't work for additional packages. I can not install click into the build system at all, but only into a cross compile sandbox folder. Regards, Sascha On 11/08/11 14:06, Markku Savela wrote: > On 11/08/2011 02:09 PM, Sascha Alexander Jopen wrote: >> does anybody cross compile click packages? > > Well, sort of.. doing > > autoconf > ./configure --enable-userlevel --disable-linuxmodule > --host=mips64-octeon-linux-gnu --build=i686-linux --enable-tools=mixed > --enable-octeon64 --enable-user-multithread > > --enable-octeon64 is own addition to configure.in to add some > parameters, and irrelevant to the cross-compile issue. > _______________________________________________ > click mailing list > [email protected] > https://amsterdam.lcs.mit.edu/mailman/listinfo/click