Instalação do Brasero

Iniciado por Mavitoro, 01 de Setembro de 2011, 09:40

tópico anterior - próximo tópico

Mavitoro

Amigos, estou tentando instalar o Brasero na minha maquina ( Ubuntu 11.04 )...etapas: ./configure
tadeu@tadeu-MS-7518:~/brasero-3.0.0$ ./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... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
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 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 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... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
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 dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
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 for dlfcn.h... yes
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... yes
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) 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... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking gnome-doc-utils >= 0.3.2... yes
checking for gtkdoc-check... no
checking for gtkdoc-rebase... no
checking for gtkdoc-mkpdf... no
checking whether to build gtk-doc documentation... no
checking whether gcc understands -Wno-sign-compare... yes
checking what warning flags to pass to the C compiler... -Wall -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wno-sign-compare
checking what language compliance flags to pass to the C compiler...
checking what warning flags to pass to the C++ compiler...
checking what language compliance flags to pass to the C++ compiler...
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for ANSI C header files... (cached) yes
checking camlib.h usability... no
checking camlib.h presence... no
checking for camlib.h... no
checking for sg_io_hdr_t... yes
checking for scsireq_t... no
checking for struct uscsi_cmd... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for BRASERO_GSTREAMER... no
configure: error: Package requirements (   gstreamer-0.10 >= 0.10.15   gstreamer-interfaces-0.10            gstreamer-plugins-base-0.10 >= 0.10.0) were not met:

No package 'gstreamer-0.10' found
No package 'gstreamer-interfaces-0.10' found
No package 'gstreamer-plugins-base-0.10' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables BRASERO_GSTREAMER_CFLAGS
and BRASERO_GSTREAMER_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details

No package 'gstreamer-0.10' found
No package 'gstreamer-interfaces-0.10' found
No package 'gstreamer-plugins-base-0.10' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

tadeu@tadeu-MS-7518:~/brasero-3.0.0$ make
make: *** Nenhum alvo indicado e nenhum arquivo make encontrado.  Pare.
tadeu@tadeu-MS-7518:~/brasero-3.0.0$  make install
make: *** Sem regra para processar o alvo `install'.  Pare.
tadeu@tadeu-MS-7518:~/brasero-3.0.0$
Porque está sem regra para processar o alvo? o que significa isso?

Tota

Ola

CitarConsider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

"Considere ajustar o caminho da variavel de ambiente para seu software"

CitarNo package 'gstreamer-0.10' found
No package 'gstreamer-interfaces-0.10' found
No package 'gstreamer-plugins-base-0.10' found

O sistema não encontrou estas dependências. Ou voce as instala ou altera o arquivo .configure para apontar para as bibliotecas de seu sistema.

[]'s

Creto

Olá a todos,

Fazendo os mesmos testes para tentar ajudar na instalação, com o meu Lucid Lynx o único problema que encontrei foi esse:

Citarconfigure: error: glib-compile-schemas not found.

bigbusca.com ==>> http://www.forumdebian.com.br/topico-problema-para-instalar-o-gnac

Que não é o mesmo aplicativo, porém é a mesma dependência faltando libglib-dev que parece só ter nos repositórios sid.