CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I opened "./configure --help" , and among the options I read the "LDFLAGS" and "CPPFLAGS" but they are not explained there. When I looked it up on other compilation samples, I see different paths to those, like:
LDFLAGS="-L/usr/lib64/sasl2" but also "-L/usr/local/lib"
The same goes for "CPPFLAGS"
So, I am confused as to what those flags must contain.
I opened "./configure --help" , and among the options I read the "LDFLAGS" and "CPPFLAGS" but they are not explained there. When I looked it up on other compilation samples, I see different paths to those, like:
LDFLAGS="-L/usr/lib64/sasl2" but also "-L/usr/local/lib"
The same goes for "CPPFLAGS"
So, I am confused as to what those flags must contain.
Thanks in advance!
Running "./configure --help" gives:
Code:
./configure --help
<snip>
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
you have headers in a nonstandard directory <include dir>
Meaning that you'll need LDFLAGS/CPPFLAGS only if you are compiling openldap against s/w that is not installed in the standard places (usually under /usr).
This could happen if you're not using official packages, so the compiler cannot find the needed libraries in /usr/lib and/or /usr/lib64 and the header files in /usr/include
Also note that if you want to compile s/w from sources, you'll need to use your package manager in order to install the development packages of core stuff.
./configure --help
<snip>
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
you have headers in a nonstandard directory <include dir>
Meaning that you'll need LDFLAGS/CPPFLAGS only if you are compiling openldap against s/w that is not installed in the standard places (usually under /usr).
This could happen if you're not using official packages, so the compiler cannot find the needed libraries in /usr/lib and/or /usr/lib64 and the header files in /usr/include
Also note that if you want to compile s/w from sources, you'll need to use your package manager in order to install the development packages of core stuff.
What does "s/w" mean?
Also, I have installed it under "/app" , a newly created directory.
Also, I have installed it under "/app" , a newly created directory.
So I am guessing I need those two flags?
( I am newish to OpenLDAP )
You don't understand the usage of those 2 env. variables.
You'll need to define them when you're compiling openldap, if you have installed any of its dependencies under a non standard directory.
If you have installed openldap in /app, then it should work fine, because it already found its dependencies in the standard directories.
However, if later on you're going to compile some other software that depends on openldap, then you'll have to define those 2 variables in that software's ./configure script.
You don't understand the usage of those 2 env. variables.
You'll need to define them when you're compiling openldap, if you have installed any of its dependencies under a non standard directory.
If you have installed openldap in /app, then it should work fine, because it already found its dependencies in the standard directories.
However, if later on you're going to compile some other software that depends on openldap, then you'll have to define those 2 variables in that software's ./configure script.
I hope it's clear now
Regards
I find it difficult to understand, to be honest, but it is really my fault. I am new to OpenLDAP.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.