Hola Linuxeros. Alguien sabe como instalar stetic en edgy con mono 1.1.17

Sab Nov 11 00:33:07 GMT 2006

2006/11/7, jesus antonio martinez pedrero <o-idea en ya.com>:
> Saludos Lista :-) Me estoy volviendo loco, se supone que tengo ya el
> mono suficeinte para correr stetic, me lo bajo de svn, pero me da este
> error.

Desde la version 0.12 Monodevelop trae integrado Stetic como diseñador
de interface. El cual se encuentra en los repositorios de Ubuntu.

http://www.monodevelop.org/Release_notes_for_MonoDevelop_0.12

Atte.
Cristóbal Mardones Bucarey

> ejecuto esto:
>
>  sudo ./autogen.sh --prefix=/usr
>
> y se acaba sin hacer el makefile correcto.
>
> checking for autoconf >= 2.53...
>
>   testing autoconf2.50...
> not found.
>   testing autoconf...
> found 2.60
>
> checking for automake >= 1.6...
>
>   testing automake-1.6...
> not found.
>   testing automake-1.7...
> not found.
>   testing automake-1.8...
> not found.
>   testing automake-1.9...
> found 1.9.6
>
> checking for libtool >= 1.5...
>
>   testing libtoolize...
> found 1.5.22
>
> checking for pkg-config >= 0.14.0...
>
>   testing pkg-config...
> found 0.20
>
> Checking for required M4 macros...
>
>
> Checking for forbidden M4 macros...
>
>
> Processing ./configure.in
>
>
> Running libtoolize...
>
>
> Running aclocal-1.9...
>
>
> Running autoconf...
>
>
> Running autoheader...
>
>
> Running automake-1.9...
>
>
> Running ./configure --enable-maintainer-mode --prefix=/usr ...
>
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles...
> yes
> checking whether make sets $(MAKE)... (cached) yes
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for style of include used by make... GNU
> 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 dependency style of gcc... none
> 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 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 for g++... no
> checking for c++... no
> checking for gpp... no
> checking for aCC... no
> checking for CC... no
> checking for cxx... no
> checking for cc++... no
> checking for cl.exe... no
> checking for FCC... no
> checking for KCC... no
> checking for RCC... no
> checking for xlC_r... no
> checking for xlC... no
> checking whether we are using the GNU C++ compiler... no
> checking whether g++ accepts -g... no
> checking dependency style of g++... none
> checking for g77... no
> checking for f77... no
> checking for xlf... 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 f90... no
> checking for xlf90... no
> checking for pgf90... no
> checking for pghpf... no
> checking for epcf90... no
> checking for gfortran... no
> checking for g95... no
> checking for f95... no
> checking for fort... no
> checking for xlf95... 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... 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... yes
> 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...
> cat: /etc/ld.so.conf.d/*.conf: No such file or directory
> 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
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> appending configuration tag "F77" to libtool
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for MONO... configure: error: Package requirements (mono >=
> 1.1.2) were not met:
>
> No package 'mono' 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 MONO_CFLAGS
> and MONO_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> Pero si tengo mono, por que haciendo un PKG_CONFIG_PATH no lo soluciono.
>
> Gracias a todos. :-)
>
>
> --
> ubuntu-es mailing list
> ubuntu-es en lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-es
>