Problemas al compilar usando make (no existe Makefile, sino Makefile.in/am)[solucionado]

Dudas y comentarios relacionadas con paquetes o programas específicos (obtención, uso, actualizaciones, versiones, problemas de instalación, etc.)

Moderadores: doc, Deckon

Responder
danijmj
Forista Nuevo
Forista Nuevo
Mensajes: 2
Registrado: Jue Feb 11, 2010 5:44 pm

Problemas al compilar usando make (no existe Makefile, sino Makefile.in/am)[solucionado]

Mensaje por danijmj » Jue Feb 11, 2010 6:17 pm

Buenas a todos, resulta que tengo un problema y ya no se donde buscar la solución, así que he recurrido a ustedes. Les expongo mi problema.
Como dije en el titulo, tengo un problema al ejecutar la serie de comandos ./configure; make; sudo make install; el configure lo hace, pero no genera ningún Makefile sino que se quedan los Makefile.in, y Makefile.am, que ya existian. voy a reportar lo que me salia en el configure:
xxx @xxx /gtk-doc-1.13$ ./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 whether to enable maintainer-specific portions of Makefiles... no
checking whether ln -s works... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking gnome-doc-utils >= 0.3.2... yes
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... gcc3
checking for library containing strerror... none required
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 build system type... i686-pc-linux-gnu
checking host system type... i686-pc-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 the maximum length of command line arguments... 1572864
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... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
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... yes
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.19... yes
checking for perl... /usr/bin/perl
checking if Perl version >= 5.6.0... yes
checking for a Python interpreter with version >= 2.3... python
checking for python... /usr/bin/python
checking for python version... 2.6
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.6/dist-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.6/dist-packages
checking for openjade... no
checking for jade... no
configure: WARNING: Could not find openjade or jade, so SGML is not supported
checking for xsltproc... /usr/bin/xsltproc
checking for dblatex... no
checking for fop... no
configure: WARNING: neither dblatex nor fop found, so no pdf output from xml
checking for XML catalog (/etc/xml/catalog)... found
checking for xmlcatalog... /usr/bin/xmlcatalog
checking for DocBook XML DTD V4.3 in XML catalog... found
checking for DocBook XSL Stylesheets in XML catalog... not found
configure: error: could not find DocBook XSL Stylesheets in XML catalog
xxx@xxx/gtk-doc-1.13$ make
make: *** No se especificó ningún objetivo y no se encontró ningún makefile. Alto.
en los archivos readme e INSTALL no me viene nada fuera de lo común, lo referente a la instalación es esto:
Briefly, the shell commands `./configure; make; make install' should
configure, build, and install this package. The following
more-detailed instructions are generic; see the `README' file for
instructions specific to this package.

el archivo README contiene esto... siento ser tan cansino, XD
GTK+ DocBook Documentation Generator
====================================

GTK-Doc is used to document C code. It is typically used to document the public
API of libraries, such as the GTK+ and GNOME libraries, but it can also be
used to document application code.

Note that GTK-Doc wasn't originally intended to be a general-purpose
documentation tool, so it can be a bit awkward to setup and use.
For a more polished general-purpose documentation tool you may want to look
at Doxygen (http://www.doxygen.org/). However GTK-Doc has some special code
to document the signals and properties of GTK+ widgets and GObject classes
which other tools may not have.

GTK-Doc allows your documentation to be written in 2 ways:
a) Embedded inside the source code in specially-formatted comments.
or
b) Added to the 'template' files which gtk-doc outputs after scanning all
the header files and parsing the declarations.

From these source code comments and template files GTK-Doc generates a Docbook
XML (or SGML) document, which is then transformed into HTML.
The generated HTML documentation can be browsed in an ordinary web browser or
by using the special Devhelp API browser
(see http://developer.imendio.com/wiki/Devhelp).


Requirements
============

Perl v5 - the main scripts are in Perl.
http://www.perl.com/


For XML output (recommended):

The DocBook XML DTD.
http://www.oasis-open.org/docbook/

The DocBook XSL Stylesheets.
http://docbook.sourceforge.net/projects/xsl/

libxslt & libxml2 2.3.6.
http://xmlsoft.org/


For SGML output (not actively maintained any more):

The DocBook SGML DTD.
http://www.oasis-open.org/docbook/

Jade v1.1 or OpenJade 1.3.1.
http://www.jclark.com/jade
http://sourceforge.net/projects/openjade

The DocBook DSSSL Stylesheets (I've got 1.40, but v1.19+ may be OK).
I've customized the DSSSL code slightly, in gtk-doc.dsl, to colour
the program code listings/declarations, and to support global
cross-reference indices in the generated HTML.
http://docbook.sourceforge.net/projects/dsssl/


Most distributions now have packages for all of these, so I would strongly
advise that you grab those.

See the documentation in the help/manual directory for more information. You can
read it e.g. with yelp file://$PWD/help/manual/C/gtk-doc-manual.xml
y dado que esto no es la primera vez que me pasa... para nada, pues necesito ayuda, pues estoy perdido. decir que tengo ubuntu 9.10
gracias de antemano.
Última edición por danijmj el Sab Feb 13, 2010 1:59 pm, editado 1 vez en total.
fpuga
Forista Mayor
Forista Mayor
Mensajes: 798
Registrado: Sab Ago 25, 2007 7:00 am
Ubicación: Galicia - España
Contactar:

Re: Problemas al compilar usando make (no existe Makefile, sino Makefile.in/am)

Mensaje por fpuga » Jue Feb 11, 2010 7:05 pm

Si te fijas en la última línea de la salida del configure pone esto
configure: error: could not find DocBook XSL Stylesheets in XML catalog
Es decir que te falta tener docbook como dependencia y por tanto no puedes compilar
Mi blog: [url=http://conocimientoabierto.es]Conocimiento Abierto[/url]
danijmj
Forista Nuevo
Forista Nuevo
Mensajes: 2
Registrado: Jue Feb 11, 2010 5:44 pm

Problemas solucionado

Mensaje por danijmj » Sab Feb 13, 2010 1:58 pm

Gracias, al final era eso, MUUCHAS GRACIAS!! pues la verdad que me has solucionado la vida, XD estaré por aquí haber si le soy útil a alguien, gracias.
Responder
  • Similar Topics
    Respuestas
    Vistas
    Último mensaje