Problem compiling the C/C++ reference for Kdevelop

2003-06-05 Thread J. Seth Henry
I recently started playing around with Kdevelop 2.x on my server, and
found it much improved over the older releases. Getting into it, I decided
to download and compile the C/C++ reference documentation, and ran into a
snag. I'm not sure if it is because the configure script is having
problems running on a FreeBSD box or what, but here is what I get:

alexandria# ./configure
checking build system type... i386-unknown-freebsd4.8
checking host system type... i386-unknown-freebsd4.8
checking target system type... i386-unknown-freebsd4.8
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 mawk... no
checking for gawk... no
checking for nawk... nawk
checking whether make sets ${MAKE}... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc
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++... gcc
checking whether g++ supports -fno-exceptions... yes
checking whether g++ supports -fno-check-new... yes
checking whether g++ supports -fexceptions... yes
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -frepo... yes
checking for ld used by GCC... /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
checking for /usr/libexec/elf/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 dependant libraries... pass_all
checking for ranlib... ranlib
checking for strip... strip
checking whether -lc should be explicitly linked in... (skipping, using
no) no
checking for objdir... .libs
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
finding the maximum length of command line arguments... 36865
checking if gcc supports -c -o file.o... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/libexec/elf/ld) supports shared
libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd4.8 ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for dlopen in -ldl... no
checking for dlopen... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
creating libtool
updating cache /dev/null
checking host system type... i386-unknown-freebsd4.8
checking build system type... i386-unknown-freebsd4.8
ltcf-cxx: with_gcc=yes ; with_gnu_ld=yes
checking for objdir... .libs
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
finding the maximum length of command line arguments... 36865
checking if g++ supports -c -o file.o... yes
checking if g++ supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/libexec/elf/ld) supports shared
libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd4.8 ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for dlopen in -ldl... no
checking for dlopen... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... no
appending configuration tag "CXX" to libtool
checking for msgfmt... /usr/local/bin/msgfmt
checking for gmsgfmt... /usr/local/bin/msgfmt
checking for xgettext... /usr/local/bin/xgettext
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... no
checking for unistd.h... yes
checking for main in -lutil... yes
checking for main in -lcompat... yes
checking for crypt in -lcrypt... yes
checking for socklen_t... socklen_t
checking for dnet_ntoa in -ldnet... no
ch

Problem compiling the C/C++ reference for Kdevelop

2003-06-05 Thread Jon Noack
> (find / | grep libqt resulted in libqt-mt.so, but no libqt.so)

I remember seeing something about this in the archives over at 
http://freebsd.kde.org.  We compile the multi-threaded version of the 
library; thus the -mt.  Not sure on the best way to fix it, but you try 
symlinking libqt.so to libqt-mt.so for the build and see what happens...

Hope that helps,
Jon
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Problem compiling the C/C++ reference for Kdevelop

2003-06-05 Thread Joshua Oreman
On Wed, Jun 04, 2003 at 12:57:24PM -0400 or thereabouts, J. Seth Henry seemed to write:
> I recently started playing around with Kdevelop 2.x on my server, and
> found it much improved over the older releases. Getting into it, I decided
> to download and compile the C/C++ reference documentation, and ran into a
> snag. I'm not sure if it is because the configure script is having
> problems running on a FreeBSD box or what, but here is what I get:
> 
> alexandria# ./configure
> checking build system type... i386-unknown-freebsd4.8
> checking host system type... i386-unknown-freebsd4.8
> checking target system type... i386-unknown-freebsd4.8
> 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 mawk... no
> checking for gawk... no
> checking for nawk... nawk
> checking whether make sets ${MAKE}... yes
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for executable suffix...
> checking for object suffix... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking dependency style of gcc... gcc
> 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++... gcc
> checking whether g++ supports -fno-exceptions... yes
> checking whether g++ supports -fno-check-new... yes
> checking whether g++ supports -fexceptions... yes
> checking how to run the C++ preprocessor... g++ -E
> checking whether g++ supports -frepo... yes
> checking for ld used by GCC... /usr/libexec/elf/ld
> checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
> checking for /usr/libexec/elf/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 dependant libraries... pass_all
> checking for ranlib... ranlib
> checking for strip... strip
> checking whether -lc should be explicitly linked in... (skipping, using
> no) no
> checking for objdir... .libs
> 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
> finding the maximum length of command line arguments... 36865
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -fno-rtti -fno-exceptions ... yes
> checking whether the linker (/usr/libexec/elf/ld) supports shared
> libraries... yes
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking dynamic linker characteristics... freebsd4.8 ld.so
> checking command to parse /usr/bin/nm -B output... ok
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> checking for dlopen in -ldl... no
> checking for dlopen... yes
> checking for dlfcn.h... yes
> checking whether a program can dlopen itself... yes
> checking whether a statically linked program can dlopen itself... no
> creating libtool
> updating cache /dev/null
> checking host system type... i386-unknown-freebsd4.8
> checking build system type... i386-unknown-freebsd4.8
> ltcf-cxx: with_gcc=yes ; with_gnu_ld=yes
> checking for objdir... .libs
> checking for g++ option to produce PIC... -fPIC -DPIC
> checking if g++ PIC flag -fPIC -DPIC works... yes
> checking if g++ static flag -static works... yes
> finding the maximum length of command line arguments... 36865
> checking if g++ supports -c -o file.o... yes
> checking if g++ supports -fno-rtti -fno-exceptions ... yes
> checking whether the linker (/usr/libexec/elf/ld) supports shared
> libraries... yes
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking dynamic linker characteristics... freebsd4.8 ld.so
> checking command to parse /usr/bin/nm -B output... ok
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> checking for dlopen in -ldl... no
> checking for dlopen... yes
> checking for dlfcn.h... yes
> checking whether a program can dlopen itself... no
> appending configuration tag "CXX" to libtool
> checking for msgfmt... /usr/local/bin/msgfmt
> checking for gmsgfmt... /usr/local/bin/msgfmt
> checking for xgettext... /usr/local/bin/xgettext
> 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

Re: Problem compiling the C/C++ reference for Kdevelop

2003-06-05 Thread J. Seth Henry
Argh - it appears that I have no libqt.so on my system. Interesting - I
installed from the package system. Having poked through the configure
script, I finally figured out what it was barfing on, and manually
searched to see if it was present, but perhaps in some odd location.
(find / | grep libqt resulted in libqt-mt.so, but no libqt.so)

Next question. Why don't I have a libqt.so?

In the meantime, I'm compiling from source using ports tree. If there is
source for libqt, then I'll know something is up.

Oh, and I accept the dumba** award for failing to notice the
--with-extra-libraries/includes option for the configure script. It now
finds the jpeg libraries.

Thanks,
Seth Henry

On Wed, 4 Jun 2003, Joshua Oreman wrote:

> On Wed, Jun 04, 2003 at 12:57:24PM -0400 or thereabouts, J. Seth Henry seemed to 
> write:
> > I recently started playing around with Kdevelop 2.x on my server, and
> > found it much improved over the older releases. Getting into it, I decided
> > to download and compile the C/C++ reference documentation, and ran into a
> > snag. I'm not sure if it is because the configure script is having
> > problems running on a FreeBSD box or what, but here is what I get:
> >
> > alexandria# ./configure
> > checking build system type... i386-unknown-freebsd4.8
> > checking host system type... i386-unknown-freebsd4.8
> > checking target system type... i386-unknown-freebsd4.8
> > 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 mawk... no
> > checking for gawk... no
> > checking for nawk... nawk
> > checking whether make sets ${MAKE}... yes
> > checking for style of include used by make... GNU
> > checking for gcc... gcc
> > checking for C compiler default output... a.out
> > checking whether the C compiler works... yes
> > checking whether we are cross compiling... no
> > checking for executable suffix...
> > checking for object suffix... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether gcc accepts -g... yes
> > checking dependency style of gcc... gcc
> > 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++... gcc
> > checking whether g++ supports -fno-exceptions... yes
> > checking whether g++ supports -fno-check-new... yes
> > checking whether g++ supports -fexceptions... yes
> > checking how to run the C++ preprocessor... g++ -E
> > checking whether g++ supports -frepo... yes
> > checking for ld used by GCC... /usr/libexec/elf/ld
> > checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
> > checking for /usr/libexec/elf/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 dependant libraries... pass_all
> > checking for ranlib... ranlib
> > checking for strip... strip
> > checking whether -lc should be explicitly linked in... (skipping, using
> > no) no
> > checking for objdir... .libs
> > 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
> > finding the maximum length of command line arguments... 36865
> > checking if gcc supports -c -o file.o... yes
> > checking if gcc supports -fno-rtti -fno-exceptions ... yes
> > checking whether the linker (/usr/libexec/elf/ld) supports shared
> > libraries... yes
> > checking how to hardcode library paths into programs... immediate
> > checking whether stripping libraries is possible... yes
> > checking dynamic linker characteristics... freebsd4.8 ld.so
> > checking command to parse /usr/bin/nm -B output... ok
> > checking if libtool supports shared libraries... yes
> > checking whether to build shared libraries... yes
> > checking whether to build static libraries... no
> > checking for dlopen in -ldl... no
> > checking for dlopen... yes
> > checking for dlfcn.h... yes
> > checking whether a program can dlopen itself... yes
> > checking whether a statically linked program can dlopen itself... no
> > creating libtool
> > updating cache /dev/null
> > checking host system type... i386-unknown-freebsd4.8
> > checking build system type... i386-unknown-freebsd4.8
> > ltcf-cxx: with_gcc=yes ; with_gnu_ld=yes
> > checking for objdir... .libs
> > checking for g++ option to produce PIC... -fPIC -DPIC
> > checking if g++ PIC flag -fPIC -DPIC works... yes
> > checking if g++ static flag -static works... yes
> > finding the maximum length of command line arguments... 36865
> > checking if g++ supports -c -o file.o... yes
> > checking if g++ supports -fno-rtti -fno-exceptions ... yes
> > checking whether the linker (/usr/libexec/elf/ld) supports shared
> > libraries... yes
> > checking how to hardcode library paths into programs... immediate
> > checking whether stripping librar