-   Linux - Newbie (
-   -   k3b install problem (

bruse 08-31-2005 08:17 AM

k3b install problem
mandrake 10.0

i am compiling the k3b from source.

[root@localhost k3b-0.11.1]# ./configure --enable-x
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 for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking CoreAudio/CoreAudio.h presence... no
checking for CoreAudio/CoreAudio.h... no
checking if res_init needs -lresolv... yes
checking if res_init is available... yes
checking for killpg in -lucb... no
checking for int... yes
checking size of int... 4
checking for short... yes
checking size of short... 2
checking for long... yes
checking size of long... 4
checking for char *... yes
checking size of char *... 4
checking for dlopen in -ldl... (cached) yes
checking for shl_unload in -ldld... no
checking for size_t... yes
checking size of size_t... 4
checking for unsigned long... yes
checking size of unsigned long... 4
checking sizeof size_t == sizeof unsigned long... yes
checking crt_externs.h usability... no
checking crt_externs.h presence... no
checking for crt_externs.h... no
checking for _NSGetEnviron... no
checking for vsnprintf... yes
checking for snprintf... yes
checking for X... configure: error: Can't find X includes. Please check your installation and add the correct paths!
[root@localhost k3b-0.11.1]#

i have the few line from error.

[root@localhost k3b-0.11.1]# ./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

-h, --help display this help and exit
--help=short display options specific to this package
--help=recursive display the short help of all the included packages
-V, --version display version information and exit
-q, --quiet, --silent do not print `checking...' messages
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for `--cache-file=config.cache'
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or `..']

Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX

By default, `make install' will install all the files in
`/usr/local/kde/bin', `/usr/local/kde/lib' etc. You can specify
an installation prefix other than `/usr/local/kde' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--datadir=DIR read-only architecture-independent data [PREFIX/share]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--infodir=DIR info documentation [PREFIX/info]
--mandir=DIR man documentation [PREFIX/man]

Program names:
--program-prefix=PREFIX prepend PREFIX to installed program names
--program-suffix=SUFFIX append SUFFIX to installed program names
--program-transform-name=PROGRAM run sed PROGRAM on installed program names

System types:
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]
--target=TARGET configure for building compilers for TARGET [HOST]

Optional Features:
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--disable-fast-perl disable fast Makefile generation (needs perl)
--enable-debug=ARG enables debug symbols (yes|no|full) default=no
--disable-debug disables debug output and debug symbols default=no
--enable-strict compiles with strict compiler options (may not work!)
--disable-warnings disables compilation with -Wall and similiar
--enable-profile creates profiling infos default=no
--disable-dependency-tracking Speeds up one-time builds
--enable-dependency-tracking Do not reject slow dependency extractors
--enable-pch enables precompiled header support (currently only KCC) default=no
--enable-final build size optimized apps (experimental - needs lots of memory)
--enable-closure delay template instantiation
--enable-nmcheck enable automatic namespace cleanness check
build shared libraries [default=yes]
build static libraries [default=no]
--enable-libsuffix /lib directory suffix (64,32,none=default)
optimize for fast installation [default=yes]
--disable-libtool-lock avoid locking (might break parallel builds)
--enable-embedded link to Qt-embedded, don't use X
--enable-qtopia link to Qt-embedded, link to the Qtopia Environment
--enable-mac link to Qt/Mac (don't use X)
--disable-mt link to non-threaded Qt (deprecated)
--disable-threading disables threading even if libpthread found
--disable-rpath do not use the rpath feature of ld
--disable-path-check don't try to find out, where to install

Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-gnu-ld assume the C compiler uses GNU ld [default=no]
--with-pic try to use only PIC/non-PIC objects [default=use
include additional configurations [automatic]
adds non standard include paths
--with-extra-libs=DIR adds non standard library paths
--with-qt-dir=DIR where the root of Qt is installed
--with-qt-includes=DIR where the Qt includes are.
--with-qt-libraries=DIR where the Qt library is installed.
--without-arts build without aRts default=yes
--with-k3bsetup=ARG do compile K3bSetup2 KControl Module (default=yes)

Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
headers in a nonstandard directory <include dir>
CPP C preprocessor
CXX C++ compiler command
CXXFLAGS C++ compiler flags
CXXCPP C++ preprocessor
F77 Fortran 77 compiler command
FFLAGS Fortran 77 compiler flags

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.

[root@localhost k3b-0.11.1]#

which option should i add to compile.?

samael26 08-31-2005 09:10 AM

Don't take it bad, but just one question : do you try to compile k3b for fun, because
you want to try gcc or just because you need it it ? Because if you need it there are
pre-compiled programs called rpms which would install it with no problem.
I ask because I did not find Mandrake the best distro to compile from source.
Each time I tried was a failure. You might think of using Slackware if you want tools
that actually let you install from source. Or Debian, perhaps. In Slack it worked much

Edit : You might have a look at this site to help you in your installs :

koodoo 08-31-2005 04:22 PM

Hi Bruse,

When I tried to compile k3b on Fedora Core 1, I also had a bunch of problems. One of them was the one you mentioned.

I think you should take a look at this thread, it might be helpful.
getting X includes and other problems

One more thing, when I compiled k3b on Slackware, it went on without a hitch.

Hope this helps.

All times are GMT -5. The time now is 04:48 PM.