[Date Prev][Date Next] [Chronological] [Thread] [Top]
RE: configure problems on solaris x86 and What are LDFLAGS and CPPFLAGS?

To: "Dan Cox" <dancox@teleport.com>, <openldap-software@OpenLDAP.org>
Subject: RE: configure problems on solaris x86 and What are LDFLAGS and CPPFLAGS?
From: "Matthew Hardin" <mhardin@symas.com>
Date: Tue, 18 Jun 2002 10:36:13 -0700
Importance: Normal
In-reply-to: <3D0F23CD.1090602@teleport.com>
In your environment, set CC=gcc and then export it. The commands look like
this:

CC=gcc
export CC

Then re-run configure.

CFLAGS, CPPFLAGS, and LDFLAGS don't always need to be set by you. In
building OpenLDAP, CFLAGS and CPPFLAGS are most often used to tell the
compiler where to look for the include files for the support packages (i.e.,
Kerberos). LDFLAGS is used to tell the compiler where the libraries for the
supporting packages are located. Say you installed all of the packages in
/usr/local. You would set the compiler flags to the following values:

CFLAGS=-I/usr/local/include
CPPFLAGS=-I/usr/local/include
LDFLAGS=-L/usr/local/lib
export CFLAGS CPPFLAGS LDFLAGS

Since configure uses the compiler to figure out a lot of stuff about your
system, it is important that the variables be properly set when you run it.

There are many other uses for these variables, but this is probably what you
need. Only set them if configure is having trouble locating one of the
support packages.

In looking at your configure options, I noticed some of them don't make a
lot of sense. If you are new to OpenLDAP, I suggest starting with as few
configure options as possible. Then as you get comfortable you can rebuild
it with additional features that you need for your application.




-Matthew Hardin
Symas Corporation

Symas: Premier Open Source Development and Support



-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Dan Cox
Sent: Tuesday, June 18, 2002 5:13 AM
To: openldap-software@OpenLDAP.org
Subject: configure problems on solaris x86 and What are LDFLAGS and
CPPFLAGS?

When I try to:

./configure --enable-debug --enable-syslog --enable-slapd --enable-crypt
--enable-spasswd --with-tls --with-syrus-sasl --enable-kpasswd
--enable-wrappers --enable-slurpd --enable-sql --enable-passwd
--enable-lbdm --enable-ldap --enable-dnssrv --enable-local --enable-cache.

I get this:

checking for sys/un.h... grep: conftest.out: No such file or directory
yes
checking for krb5.h... grep: conftest.out: No such file or directory
yes
checking for heim_err.h... grep: conftest.out: No such file or directory
yes
checking for main in -ldes... no
checking for main in -lkrb5... no
configure: error: Required Kerberos 5 support not available.

    I do have kerberos installed and found krb.h in many directories.
Also the  "grep: conftest.out" shows up quite a bit during the
./configure. If anybody can help me out I'd greatly appreciate it. Also
can anybody tell me what LDFLAGS and CPPFLAGS are? Why are they
important to set? Please use small words, everything I can find on the
subject seems to be written for experienced programmers (something I am
defiantly not). Some of the output from ./configure is below.

The output:

checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
checking whether -lc should be explicitly linked in... yes
creating libtool
checking for mawk... (cached) gawk
checking whether ln works... yes
checking whether ln -s works... (cached) yes
checking for sendmail... /usr/lib/sendmail
checking for vi... /usr/bin/vi
checking how to run the C preprocessor...  -E
checking for Cygwin environment... (cached) no
checking for mingw32 environment... (cached) no
checking for executable suffix... (cached) no
checking for object suffix... (cached) o
checking for be_app in -lbe... no
checking for gcc option to accept ANSI C... none needed
checking for gcc depend flag... -M
checking for afopen in -ls... no
checking for EBCDIC... grep: conftest.out: No such file or directory
yes
checking for ANSI C header files... grep: conftest.out: No such file or
directory
no
configure: warning: could not locate Standard C compliant headers
checking for dirent.h that defines DIR... yes
checking for opendir in -ldir... no
checking for sys/wait.h that is POSIX.1 compatible... yes
checking POSIX termios... yes
checking whether use of TIOCGWINSZ requires sys/ioctl.h... no
checking for arpa/inet.h... grep: conftest.out: No such file or directory
yes
checking for arpa/nameser.h... grep: conftest.out: No such file or directory
yes
checking for assert.h... grep: conftest.out: No such file or directory
yes
checking for conio.h... grep: conftest.out: No such file or directory
yes
checking for crypt.h... grep: conftest.out: No such file or directory
yes
checking for direct.h... grep: conftest.out: No such file or directory
yes
checking for errno.h... grep: conftest.out: No such file or directory
yes
checking for fcntl.h... grep: conftest.out: No such file or directory
yes
checking for filio.h... grep: conftest.out: No such file or directory
yes
checking for getopt.h... grep: conftest.out: No such file or directory
yes
checking for grp.h... grep: conftest.out: No such file or directory
yes
checking for io.h... grep: conftest.out: No such file or directory
yes
checking for libutil.h... grep: conftest.out: No such file or directory
yes
checking for limits.h... grep: conftest.out: No such file or directory
yes
checking for locale.h... grep: conftest.out: No such file or directory
yes
checking for netinet/tcp.h... grep: conftest.out: No such file or directory
yes
checking for malloc.h... grep: conftest.out: No such file or directory
yes
checking for memory.h... grep: conftest.out: No such file or directory
yes
checking for psap.h... grep: conftest.out: No such file or directory
yes
checking for pwd.h... grep: conftest.out: No such file or directory
yes
checking for process.h... grep: conftest.out: No such file or directory
yes
checking for resolv.h... grep: conftest.out: No such file or directory
yes
checking for sgtty.h... grep: conftest.out: No such file or directory
yes
checking for shadow.h... grep: conftest.out: No such file or directory
yes
checking for stddef.h... grep: conftest.out: No such file or directory
yes
checking for string.h... grep: conftest.out: No such file or directory
yes
checking for strings.h... grep: conftest.out: No such file or directory
yes
checking for sysexits.h... grep: conftest.out: No such file or directory
yes
checking for sys/file.h... grep: conftest.out: No such file or directory
yes
checking for sys/filio.h... grep: conftest.out: No such file or directory
yes
checking for sys/errno.h... grep: conftest.out: No such file or directory
yes
checking for sys/ioctl.h... grep: conftest.out: No such file or directory
yes
checking for sys/param.h... grep: conftest.out: No such file or directory
yes
checking for sys/resource.h... grep: conftest.out: No such file or directory
yes
checking for sys/select.h... grep: conftest.out: No such file or directory
yes
checking for sys/socket.h... grep: conftest.out: No such file or directory
yes
checking for sys/syslog.h... grep: conftest.out: No such file or directory
yes
checking for sys/time.h... grep: conftest.out: No such file or directory
yes
checking for sys/types.h... grep: conftest.out: No such file or directory
yes
checking for syslog.h... grep: conftest.out: No such file or directory
yes
checking for termios.h... grep: conftest.out: No such file or directory
yes
checking for unistd.h... grep: conftest.out: No such file or directory
yes
checking for winsock.h... grep: conftest.out: No such file or directory
yes
checking for winsock2.h... grep: conftest.out: No such file or directory
yes
checking for dlopen... (cached) yes
checking for sigset in -lV3... no
checking for winsock... no
checking for socket... no
checking for main in -lsocket... yes
checking for main in -lnet... no
checking for main in -lnsl_s... no
checking for main in -lnsl... yes
checking for socket in -linet... no
checking for main in -lgen... yes
checking for select... yes
checking for regex.h... grep: conftest.out: No such file or directory
yes
checking for library containing regfree... none required
checking for compatible POSIX regex... yes
checking for sys/uuid.h... grep: conftest.out: No such file or directory
yes
checking for library containing uuid_to_str... no
checking to see if -lrpcrt4 is needed for win32 UUID support... no
checking for res_query... no
checking for __res_query... no
checking for res_query in -lbind... no
checking for __res_query in -lbind... no
checking for res_query in -lresolv... yes
checking for getaddrinfo... yes
checking for gai_strerror... yes
checking for inet_ntop... yes
checking INET6_ADDRSTRLEN... no
checking for sys/un.h... grep: conftest.out: No such file or directory
yes
checking for krb5.h... grep: conftest.out: No such file or directory
yes
checking for heim_err.h... grep: conftest.out: No such file or directory
yes
checking for main in -ldes... no
checking for main in -lkrb5... no
configure: error: Required Kerberos 5 support not available
Follow-Ups:
- RE: configure problems on solaris x86 and What are LDFLAGS and CPPFLAGS?
  - From: "Howard Chu" <hyc@highlandsun.com>
References:
- configure problems on solaris x86 and What are LDFLAGS and CPPFLAGS?
  - From: Dan Cox <dancox@teleport.com>
Prev by Date: Re: OpenLDAP reference implementation of LDAPv3?
Next by Date: RE: configure problems on solaris x86 and What are LDFLAGS and CPPFLAGS?
Index(es):
- Chronological
- Thread