Jump to content

Recommended Posts

Люди добрые, я первые 3 часа в линуксе. Установил мандриву 2008, и возник вопрос, как устанавливать программы из файла? Через инет установил sim, но у меня диск с софтом, а из него я ничего установить не могу.

Разархивировал прогу из тар.гз, набираю в консоли ./configure и тут выводит:

[andrey@localhost wireshark-0.99.6]$ ./configure

checking build system type... i686-pc-linux-gnuoldld

checking host system type... i686-pc-linux-gnuoldld

checking target system type... i686-pc-linux-gnuoldld

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for gawk... gawk

checking whether make sets $(MAKE)... no

checking for gcc... no

checking for cc... no

checking for cl.exe... no

configure: error: no acceptable C compiler found in $PATH

See `config.log' for more details.

[andrey@localhost wireshark-0.99.6]$

Оболочка на сколько я понял KDE.

Че делать??????????

Share this post


Link to post
Share on other sites

1. Надо было покупать PowerPack с книжкой.

2. Если книжки нет - то иди в панель управления, управление пакетами, добавление источников пакетов. Нужно добавить источники. После из установка-удаление программ поставить нужную программу.

Share this post


Link to post
Share on other sites

у меня диск, "мир linux" называется. так там несколько дистрибутивов и все они подточины под cd. Оригинал мандривы на сколько я знаю занимает всю dvd болванку, а тут cd. Я думаю, что этих покетов там нет вовсе...

Share this post


Link to post
Share on other sites

Ниче не нашел. Установил кое какие пакеты из интернета, и вот что пишет:

[andrey@localhost wireshark-0.99.6]$ ./configure

checking build system type... i686-pc-linux-gnu

checking host system type... i686-pc-linux-gnu

checking target system type... i686-pc-linux-gnu

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking for gcc... gcc

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 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 how to run the C preprocessor... gcc -E

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 recognise dependent libraries... pass_all

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 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 how to run the C++ preprocessor... g++ -E

checking for g77... g77

checking whether we are using the GNU Fortran 77 compiler... yes

checking whether g77 accepts -g... yes

checking the maximum length of command line arguments... 32768

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... no

checking if gcc supports -c -o file.o... yes

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 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 if libtool supports shared libraries... yes

checking whether to build shared libraries... yes

checking whether to build static libraries... no

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... no

checking if g++ supports -c -o file.o... yes

checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes

checking dynamic linker characteristics... GNU/Linux ld.so

checking how to hardcode library paths into programs... immediate

appending configuration tag "F77" to libtool

checking if libtool supports shared libraries... yes

checking whether to build shared libraries... yes

checking whether to build static libraries... no

checking for g77 option to produce PIC... -fPIC

checking if g77 PIC flag -fPIC works... yes

checking if g77 static flag -static works... no

checking if g77 supports -c -o file.o... yes

checking whether the g77 linker (/usr/bin/ld) supports shared libraries... yes

checking dynamic linker characteristics... GNU/Linux ld.so

checking how to hardcode library paths into programs... immediate

checking for bison... no

checking for byacc... no

checking for flex... no

checking for lex... no

checking for perl... /usr/bin/perl

checking for pod2man... /usr/bin/pod2man

checking for pod2html... /usr/bin/pod2html

checking for htmlview... no

checking for flex... no

checking for python... /usr/bin/python

checking for doxygen... no

checking for doxygen... no

checking for libgnutls-config... /usr/bin/libgnutls-config

checking for libgnutls - version >= 1.0.0... yes

gnuTLS found, enabling ssl decryption

checking for libgcrypt-config... /usr/bin/libgcrypt-config

checking for LIBGCRYPT - version >= 1.1.42... yes

libgcrypt found, enabling ipsec decryption

checking for xsltproc... no

checking for xsltproc... no

checking for xmllint... /usr/bin/xmllint

checking for xmllint... yes

checking for fop... no

checking for fop... no

checking for hhc.exe... no

checking for hhc.exe... no

checking for pkgproto... no

checking for pkgmk... no

checking for pkgtrans... no

checking for rpm... yes

checking to see if we can redefine _topdir... yes

checking whether we can add -Wall -W to CFLAGS... yes

checking whether we can add -Wdeclaration-after-statement to CFLAGS... yes

checking whether we can add -Wendif-labels to CFLAGS... yes

checking whether we can add -Wpointer-arith to CFLAGS... yes

checking whether we can add -Wno-pointer-sign to CFLAGS... yes

checking whether we should treat compiler warnings as errors... no

checking for platform-specific compiler flags... none needed

checking for platform-specific linker flags... none needed

checking whether to use /usr/local for headers and libraries... yes

checking for GNU sed as first sed in PATH... yes

checking if profile builds must be generated... no

checking for pkg-config... /usr/bin/pkg-config

checking for GTK+ - version >= 2.0.0... no

*** Could not run GTK+ test program, checking why...

*** The test program failed to compile or link. See the file config.log for the

*** exact error that occured. This usually means GTK+ is incorrectly installed.

configure: error: GTK+ isn't available, so Wireshark can't be compiled

[andrey@localhost wireshark-0.99.6]$

Чего не хватает?

Share this post


Link to post
Share on other sites

да перестаньте играться с установкой из исходников. Устанавливайте штатными средствами установки пакетов.

Share this post


Link to post
Share on other sites

DrCHipolinoDeath писал(а) Mon, 09 June 2008 09:42

А что это за пакеты? Через источники в нете я и сам разобрался как устанавливать.

Есть же, даже научились как ставить. Или инет дорогой? Если анлим, то не мучайтесь с исходниками, качайте из инета. Если нет возможности качать, то надо еще все равно доустановить GTK+ - version >= 2.0.0

Share this post


Link to post
Share on other sites

качать и ставить недостоющие вещи.... врят ли у тебя все пакеты есть нужные

тебе придется качать и пытаться собирать.... не забывай про зависимости Smile с которыми ты уже сталкнулся...

народ прально говорит заюзай ты apt-get или что там в мандрейке и не парь мозГ.... он сам все скачает и поставит...

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...