Форум русскоязычного сообщества Ubuntu


Считаете, что Ubuntu недостаточно дружелюбна к новичкам?
Помогите создать новое Руководство для новичков!

Автор Тема: KDevelop не компилит  (Прочитано 1474 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн Robotex

  • Автор темы
  • Любитель
  • *
  • Сообщений: 85
    • Просмотр профиля
KDevelop не компилит
« : 29 Июля 2008, 05:19:13 »
Выдает вот такое вот:
cd '/home/robotex/Projects/probe3' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" make -f Makefile.cvs && mkdir '/home/robotex/Projects/probe3/debug' && cd '/home/robotex/Projects/probe3/debug' && CXXFLAGS="-O0 -g3" "/home/robotex/Projects/probe3/configure" --enable-debug=full && cd '/home/robotex/Projects/probe3/debug' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" make -k
aclocal
configure.in:8: warning: macro `AM_PROG_LIBTOOL' not found in library
autoheader
automake
autoconf
configure.in:8: error: possibly undefined macro: AM_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.
make: *** [all] Error 1
*** Exited with status: 2 ***
automake, autoconf и build-essential стоит

Оффлайн Robotex

  • Автор темы
  • Любитель
  • *
  • Сообщений: 85
    • Просмотр профиля
Re: KDevelop не компилит
« Ответ #1 : 29 Июля 2008, 05:31:28 »
Установил libtool. Скомпилило Hello, world.
При попытке компиляции SDL приложения выдает:
cd '/home/robotex/Projects/probe4' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" make -f Makefile.cvs && mkdir '/home/robotex/Projects/probe4/debug' && cd '/home/robotex/Projects/probe4/debug' && CXXFLAGS="-O0 -g3" "/home/robotex/Projects/probe4/configure" --enable-debug=full && cd '/home/robotex/Projects/probe4/debug' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" make -k
aclocal
configure.in:12: warning: underquoted definition of KDE_FIND_PATH
configure.in:12: run info '(automake)Extending aclocal'
configure.in:12: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
autoheader
automake
autoconf
installing -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
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 dependency style of gcc... gcc3
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 ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
linking file.o... (gcc)
checking whether the gcc linker (/usr/bin/ld) 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 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
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
linking file.o... (g++)
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for sdl-config... not found
configure: WARNING: Could not find libsdl anywhere, check http://www.sdl.org
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
make all-recursive
Making all in src
compiling probe4.cpp (g++)
/home/robotex/Projects/probe4/src/probe4.cpp:28:17: error: SDL.h: No such file or directory
/home/robotex/Projects/probe4/src/probe4.cpp: In function 'int main(int, char**)':
/home/robotex/Projects/probe4/src/probe4.cpp:36: error: 'SDL_INIT_AUDIO' was not declared in this scope
/home/robotex/Projects/probe4/src/probe4.cpp:36: error: 'SDL_INIT_CDROM' was not declared in this scope
/home/robotex/Projects/probe4/src/probe4.cpp:36: error: 'SDL_Init' was not declared in this scope
/home/robotex/Projects/probe4/src/probe4.cpp:37: error: 'SDL_GetError' was not declared in this scope
/home/robotex/Projects/probe4/src/probe4.cpp:38: error: 'SDL_Quit' was not declared in this scope
/home/robotex/Projects/probe4/src/probe4.cpp:42: error: 'SDL_CDNumDrives' was not declared in this scope
/home/robotex/Projects/probe4/src/probe4.cpp:44: error: 'SDL_CDName' was not declared in this scope
/home/robotex/Projects/probe4/src/probe4.cpp:47: error: 'SDL_Quit' was not declared in this scope
make[2]: Nothing to be done for `all-am'.
make[2]: *** [probe4.o] Error 1
make[2]: Target `all' not remade because of errors.
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
*** Exited with status: 2 ***
При компиляции Win32 приложения выдает:
cd '/home/robotex/Projects/probe2' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" make -f Makefile.cvs && cd '/home/robotex/Projects/probe2/debug' && CC="i586-mingw32msvc-c" CXX="i586-mingw32msvc-c++" LD="i586-mingw32msvc-ld" CXXFLAGS="-O0 -g3" "/home/robotex/Projects/probe2/configure" --enable-debug=full && cd '/home/robotex/Projects/probe2/debug' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" make
aclocal
autoheader
automake
autoconf
installing -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for C++ compiler default output file name...
configure: error: C++ compiler cannot create executables
See `config.log' for more details.
*** Exited with status: 77 ***
Сменить IDE просьба не предлагать

Оффлайн wl

  • Старожил
  • *
  • Сообщений: 1393
    • Просмотр профиля
И не должен
« Ответ #2 : 29 Июля 2008, 11:45:03 »
Вам подробно написано, какие ошибки возникли.

Проблема не в KDevelop, а в неправильных/отсутствующих файлах скриптов или пакетах или библиотеках.
KDevelop это всего лишь графический интерфейс, компиляторы - отдельно.

1.
Цитировать
configure.in:8: error: possibly undefined macro: AM_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.
m4_pattern_allow стоит?
В документации по Autoconf что по этому поводу сказано?

2.
Цитировать
/home/robotex/Projects/probe4/src/probe4.cpp:28:17: error: SDL.h: No such file or directory
SDL есть?

3.
Цитировать
configure: error: C++ compiler cannot create executables
See `config.log' for more details.
В логе что сказано?
Могу предположить, что пакет mingw32 не установлен.

А еще рекомендую приглядеться к CMake - ну очень приятная штука. Да, необходимость наличия компиляторов и библиотек не отменяет.
« Последнее редактирование: 29 Июля 2008, 12:01:40 от wl »
На свете феньки есть такие, брат Горацио, которых лохи просто не секут. (Шекспир, "Гамлет", вольный перевод)

Оффлайн Robotex

  • Автор темы
  • Любитель
  • *
  • Сообщений: 85
    • Просмотр профиля
Re: KDevelop не компилит
« Ответ #3 : 06 Августа 2008, 20:33:42 »
Да, с SDL ступил.

Но mingw32 стоит...

 

Страница сгенерирована за 0.076 секунд. Запросов: 23.