Re: Automake for RISC-V

2021-11-22 Thread Billa Surendra
On Sun, Nov 21, 2021 at 12:09 PM Daniel Herring wrote: > Hi Billa, > > It sounds like you are trying to build from a source repo instead of a > release tarball. > > Building with automake or autoconf is a multi-step process. Run automake > on a ".am" file to generate a makefile. Run make on the

Re: Automake for RISC-V

2021-11-21 Thread Bob Friesenhahn
On Sun, 21 Nov 2021, Billa Surendra wrote: With these steps I am not able to install. Error message is "aclocal-1-15 not found". This means that Autools generated files (a collection of packages, one of which is Automake) are being regenerated for some reason. In this case, it is having a p

Re: Automake for RISC-V

2021-11-21 Thread Billa Surendra
With these steps I am not able to install. Error message is "aclocal-1-15 not found". On Sun, 21 Nov, 2021, 5:38 pm Peter Johansson, wrote: > > On 21/11/21 16:32, Billa Surendra wrote: > > Then how-to install automake in target image. > > > Download the tarball from https://ftp.gnu.org/gnu/autom

Re: Automake for RISC-V

2021-11-21 Thread Peter Johansson
On 21/11/21 16:32, Billa Surendra wrote: Then how-to install automake in target image. Download the tarball from https://ftp.gnu.org/gnu/automake/ unpack and follow the instructions in INSTALL; typically somethings like ./configure make sudo make install Peter

Re: Automake for RISC-V

2021-11-20 Thread Daniel Herring
Hi Billa, It sounds like you are trying to build from a source repo instead of a release tarball. Building with automake or autoconf is a multi-step process. Run automake on a ".am" file to generate a makefile. Run make on the makefile to build the executable. Automake has a special "mak

Re: Automake for RISC-V

2021-11-20 Thread Billa Surendra
Then how-to install automake in target image. On Sun, 21 Nov, 2021, 11:57 am Jacob Bachmeyer, wrote: > Billa Surendra wrote: > > On Sun, 21 Nov, 2021, 2:28 am Nick Bowler, wrote: > > > >> On 20/11/2021, Billa Surendra wrote: > >> > >>> I have RISC-V native compiler on target image, but when I

Re: Automake for RISC-V

2021-11-20 Thread Jacob Bachmeyer
Billa Surendra wrote: On Sun, 21 Nov, 2021, 2:28 am Nick Bowler, wrote: On 20/11/2021, Billa Surendra wrote: 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. Automake should n

Re: Automake for RISC-V

2021-11-20 Thread Billa Surendra
On Sun, 21 Nov, 2021, 2:28 am Nick Bowler, wrote: > On 20/11/2021, Billa Surendra wrote: > > 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. > > Automake should not be required to insta

Re: Automake for RISC-V

2021-11-20 Thread Nick Bowler
On 20/11/2021, Billa Surendra wrote: > 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. Automake should not be required to install automake if you are using a released version and have not mo

Re: Automake for RISC-V

2021-11-19 Thread Billa Surendra
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.

Re: Automake for RISC-V

2021-11-19 Thread Bob Friesenhahn
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 targ

Re: Automake for RISC-V

2021-11-18 Thread Jacob Bachmeyer
Billa Surendra wrote: Thanks for your reply. I have installed perl on target system but target image and build system perl version were different. And second, thing I have noticed that in aclocal script very first line is #! /bin/perl A simple workaround is to find perl on the target system

Re: Automake for RISC-V

2021-11-18 Thread Billa Surendra
Thanks for your reply. I have installed perl on target system but target image and build system perl version were different. And second, thing I have noticed that in aclocal script very first line is #! /bin/perl On Thu, 18 Nov, 2021, 11:48 pm Nick Bowler, wrote: > Hi Billa, > > On 18/11/2021,

Re: Automake for RISC-V

2021-11-18 Thread Nick Bowler
Hi Billa, On 18/11/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". Automake is written in Perl so it does not really get "compil

Automake for RISC-V

2021-11-18 Thread Billa Surendra
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". Here I am giving more information The command used for cross-compile Automake: $ ./configure --prefix=/usr --host=