Menu
▾
▴
ayttm-devel
|
From: Aniket S. <ki...@gm...> - 2010-04-18 18:18:42
|
Hi, I just now downloaded the ayttm project from sourceforge. I was following the steps in file INSTALL. The first step (*./configure*) worked, but when I typed *make* and pressed enter at the prompt, I got this error: > *ayt...@li...* > Any help? I'm comfortable using C/C++, but I'm new to Linux. Any suggestions? -- *Aniket Suryavanshi* B.Sc. (Computer Science) student, India. aniket.wordpress.com twitter.com/kietan www.facebook.com/aniket1 |
|
From: Siddhesh P. <sid...@gm...> - 2010-04-19 02:49:40
|
On Sun, Apr 18, 2010 at 11:48 PM, Aniket Suryavanshi <ki...@gm...> wrote: > The first step (./configure) worked, but when I typed make and pressed enter > at the prompt, I got this error: >> >> ayt...@li... > Could you paste the error again? You pasted the mailing list id again, probably by mistake. Also, did you download the tarball or did you clone the git repository? -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Aniket S. <ki...@gm...> - 2010-04-20 15:03:07
|
On Mon, Apr 19, 2010 at 8:19 AM, Siddhesh Poyarekar < sid...@gm...> wrote: > On Sun, Apr 18, 2010 at 11:48 PM, Aniket Suryavanshi <ki...@gm...> > wrote: > > The first step (./configure) worked, but when I typed make and pressed > enter > > at the prompt, I got this error: > >> > >> ayt...@li... > > > > Could you paste the error again? You pasted the mailing list id again, > probably by mistake. > > Also, did you download the tarball or did you clone the git repository? > > > -- > Siddhesh Poyarekar > http://siddhesh.in > > I accidentally pasted wrong text in my last email. Sorry for that. I downloaded the project from http://sourceforge.net/projects/ayttm/Downloaded file had a * .tar.bz2* extension. I extracted the folder, opened the terminal and *cd *to this folder. First I used the command *./configure* Then a number of messages were printed on screen. Then I used *make*. I got the following error: > make: *** No targets specified and no makefile found. Stop. > Any help on this? Also, I checked out the TODO file. I prefer to work on MSN. -- *Aniket Suryavanshi* B.Sc. (Computer Science) student, India. aniket.wordpress.com twitter.com/kietan www.facebook.com/aniket1 |
|
From: Kartik M. <kar...@gm...> - 2010-04-20 15:09:18
|
On Tue, Apr 20, 2010 at 8:32 PM, Aniket Suryavanshi <ki...@gm...> wrote: > First I used the command ./configure Then a number of messages were printed > on screen. > > Then I used make. I got the following error: > make: *** No targets specified and no makefile found. Stop. Hi Aniket, 'number of messages' must contain some error. ie. your ./configure is not finished. Please paste output of ./configure using pastebin.com or similar service. Thanks. -- Cheers, Kartik Mistry Debian GNU/Linux Developer 0xD1028C8D | Identica: @kartikm | IRC: kart_ Blogs: {gu: kartikm, en: ftbfs}.wordpress.com |
|
From: Aniket S. <ki...@gm...> - 2010-04-20 15:15:47
|
On Tue, Apr 20, 2010 at 8:38 PM, Kartik Mistry <kar...@gm...>wrote: > > > Hi Aniket, > > 'number of messages' must contain some error. ie. your ./configure is > not finished. Please paste output of ./configure using pastebin.com or > similar service. > > Thanks. > > -- > Cheers, > Kartik Mistry > Debian GNU/Linux Developer > 0xD1028C8D | Identica: @kartikm | IRC: kart_ > Blogs: {gu: kartikm, en: ftbfs}.wordpress.com > > Hi Kartik, All these messages were printed by *./configure*: [root@globex ayttm-0.6.2]# ./configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for style of include used by make... GNU > checking dependency style of gcc... gcc3 > checking for strerror in -lcposix... no > checking for flex... flex > checking lex output file root... lex.yy > checking lex library... -lfl > checking whether yytext is a pointer... yes > checking for flex... flex > checking for bison... bison -y > checking for bison... bison > checking how to run the C preprocessor... gcc -E > checking for g++... g++ > checking whether we are using the GNU C++ compiler... yes > checking whether g++ accepts -g... yes > checking dependency style of g++... gcc3 > checking for g++... g++ > checking for ranlib... ranlib > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking for a sed that does not truncate output... /bin/sed > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -E > checking for fgrep... /bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1966080 > checking whether the shell understands some XSI constructs... yes > checking whether the shell understands "+="... yes > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for ar... ar > checking for strip... strip > checking for ranlib... (cached) ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking whether we are using the GNU C++ compiler... (cached) yes > checking whether g++ accepts -g... (cached) yes > checking dependency style of g++... (cached) gcc3 > checking how to run the C++ preprocessor... g++ -E > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... no > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking for shl_load... no > checking for shl_load in -ldld... no > checking for dlopen... no > checking for dlopen in -ldl... yes > checking whether a program can dlopen itself... yes > checking whether a statically linked program can dlopen itself... yes > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for ld used by g++... /usr/bin/ld -m elf_x86_64 > checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes > checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking for g++ option to produce PIC... -fPIC -DPIC > checking if g++ PIC flag -fPIC -DPIC works... yes > checking if g++ static flag -static works... no > checking if g++ supports -c -o file.o... yes > checking if g++ supports -c -o file.o... (cached) yes > checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > Using Libtool for dynamic library loading > checking for windres... no > checking for _af_ulaw2linear in -laudiofile... no > checking for lt_dlopen in -lltdl... no > configure: error: Could not find Libtool Libraries > [root@globex ayttm-0.6.2]# > BTW I have a Fedora x64 version installed, which I had downloaded several months ago. Thanks, Aniket. -- *Aniket Suryavanshi* B.Sc. (Computer Science) student, India. aniket.wordpress.com twitter.com/kietan www.facebook.com/aniket1 |
|
From: Siddhesh P. <sid...@gm...> - 2010-04-20 15:20:11
|
On Tue, Apr 20, 2010 at 8:45 PM, Aniket Suryavanshi <ki...@gm...> wrote: >> checking for lt_dlopen in -lltdl... no >> configure: error: Could not find Libtool Libraries >> [root@globex ayttm-0.6.2]# > It says that you don;t have libtool libraries. You need to install libtool-ltdl-devel. -- Siddhesh Poyarekar http://siddhesh.in |
|
From: Aniket S. <ki...@gm...> - 2010-04-20 15:33:23
|
On Tue, Apr 20, 2010 at 8:50 PM, Siddhesh Poyarekar < sid...@gm...> wrote: > > > It says that you don;t have libtool libraries. You need to install > libtool-ltdl-devel. > > > -- > Siddhesh Poyarekar > http://siddhesh.in > > Hi Siddhesh, I'll get it fixed. Will email again when it's done or having any problems. Thanks. Regards, Aniket. -- Aniket Suryavanshi B.Sc. (Computer Science) student, India. aniket.wordpress.com twitter.com/kietan www.facebook.com/aniket1 |
|
From: Philip T. <phi...@gm...> - 2010-04-20 18:12:32
|
On 20 April 2010 08:15, Aniket Suryavanshi <ki...@gm...> wrote: > >> [root@globex ayttm-0.6.2]# ./configure >> checking for a BSD-compatible install... /usr/bin/install -c Hi Aniket, You really shouldn't be running configure as root. Run the configure and make commands in your own account, and only use root (better would be sudo) to do the make install step. Philip PS: If you want to start development, then you'll be better off getting the code from git. |
|
From: 2134918 <21...@gm...> - 2010-04-20 19:07:18
|
If you download sources from git repo, you'll need to run ./gen before ./configure. You will also need to install following packages, if you don't have them yet: yum install flex yum install bison yum install libtool* yum install enchant* yum install libXpm-devel yum install gettext plus packages mentioned on http://ayttm.sourceforge.net/dev.php Now interesting thing: the configure script from tar.gz file didn't say anything about gettext - even without it I was able to run make and compile it (but then crashed...). Only ./gen was able to warn me about lack of gettext. |
Thanks for helping keep SourceForge clean.
X