Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am, obviously, a newbe with Linux and have to build the source code for a text-to-speech application (Flite). I am a member on a senior project team where the project is to assemble a handfull of applications together and then port them to a development board which is linux based so we are running the desktop with Linux to speak to the board.
Currently running Fedora
In the last step of this chain of apps we run a TTS (Flite-1.3 from CMU). Where I am getting lost is building the Flite source code into an executable program.
The documentation is pretty much limited to:
Quote:
tar zxvf flite-XXX.tar.gz
cd flite-XXX
./configure
make
So I extract the .tar.gz with ARK to a folder, open that folder and launch the terminal. In the Terminal I ran the "./configure" and then "make".
After "make" it came back with the command line and I did not see anything that explicitly looked like an error.
Now what do I do? After "make" I still need to complie right? Where should I look for the file(s) which I need to compile?
I've noticed that this source code contains many folders and at least 4 of the subfolders contain makefiles. Would I need to go to each folder and run "make"?
now I've hit my head on the classic error, a file or directory is missing midway thru the install which stops it and returns "Error 2"
Is there a way to find out what these error messages mean?
Error 2 is a make error, the error you're interested in will be from the compiler or the linker and will appear further up. Look for something starting "In file..." that isn't immediately followed by "Warning" (we're interested in errors not warnings).
If you want, post some output here, but put it between [code ] [/code ] tags (remove the space in those)
I am running the whole process again with a new download copy in a clean folder. When I configure it runs through the "checking" and ends up with a bunch of "no" returns. Mainly from my lack of a sound card.
Watching the make I saw no errors occur. There was, however, a plethora of warnings.
With make install I get:
Code:
Installing
mkdir -p /usr/local/bin
mkdir -p /usr/local/lib
mkdir -p /usr/local/include/flite
/usr/bin/install -c -m 644 include/*h /usr/local/include/flite
make: *** lib: No such file or directory. Stop.
make: *** [install] Error 2
When I tared I used
Code:
tar zxvf filename.tar.gz
I am within the folder it created when I try to run the make install
I dove back into the flite readme file and found that it wanted GNU make. I have no clue whether this computer is running it or what the difference is in the make that is on here so I installed the one off the GUN ftp. GNU make installed without a problem. I am now retrying the install.
Thank you all for bearing with me and my newbe questions
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.