I have RISC-V native compiler on target image, but when I am compiling automake on target image it needs automake on target. This is the main problem. In the same way I am trying to install texinfo on target image it also need automake on target. Suggest me how I can break this circular dependency.
Thanks On Fri, 19 Nov, 2021, 7:41 pm Bob Friesenhahn, <bfrie...@simple.dallas.tx.us> wrote: > On Thu, 18 Nov 2021, Billa Surendra wrote: > > > Dear All, > > > > I have cross-compiled Automake-1.16.2 package with RISC-V cross compiler, > > but when I am executing binaries on RISC-V target OS image its gives > errors > > like "not found". > > Is there a reason why you need to "cross compile" Automake for the > target rather than add the few pre-requisites to the target and native > "compile" Automake there. The pre-requisites needed to actually > execute the "compiled" Automake on the target are similar to what is > needed to cross-compile it so I am not seeing a win by trying to cross > compile a script-based build tool. > > If you had a working cross-compiler for RISC-V then you could compile > the software for the target (e.g. using Automake) without needing to > add build tools to it. > > Bob > -- > Bob Friesenhahn > bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ > Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt >
