Hi, Not sure whether this is the right list to be writing to (the website suggests it is), and I'm not following the suggested method (patch documentation, and post it here if I don't want to use git), but I wouldn't really know which document to patch with my suggestion. I wanted to (and eventually managed to) install freeradius 2.1.12 with a PostgreSQL backend. The existing docu, and the output of ./configure --help give no clues as to what's required. A run of ./configure w/o any parameters didn't pick up my postgres install (which has its headers and libs in fairly commonplace locations). Only grepping for -ril postgres I found configure options in the redhat.spec file, and using those radius built against Postgres just fine ... can this info either be added into the configure script, or the INSTALL document? Cheers, Andrej
On 10/23/2011 09:23 PM, Andrej wrote:
Hi,
Not sure whether this is the right list to be writing to (the website suggests it is), and I'm not following the suggested method (patch documentation, and post it here if I don't want to use git), but I wouldn't really know which document to patch with my suggestion.
I wanted to (and eventually managed to) install freeradius 2.1.12 with a PostgreSQL backend. The existing docu, and the output of ./configure --help give no clues as to what's required. A run of ./configure w/o any parameters didn't pick up my postgres install (which has its headers and libs in fairly commonplace locations).
Which location? What OS are you on? Plain ./configure works fine for me on RHEL5 and Fedora.
On 24 October 2011 21:50, Phil Mayers <p.mayers@imperial.ac.uk> wrote: Hi Phil, Thanks for taking the time to respond.
Which location?
/usr/lib64/postgresql /usr/include/postgresql
What OS are you on?
Slackware64 13.1 - postgres 9.1.1 built and installed from source.
Plain ./configure works fine for me on RHEL5 and Fedora.
That's good for you but kind of besides the point.. :} I *did* get it installed; what I'm saying is that the build process/build requirements w/ an RDBMS back-end aren't really documented. Cheers, Andrej
On 24/10/11 17:17, Andrej wrote:
On 24 October 2011 21:50, Phil Mayers<p.mayers@imperial.ac.uk> wrote: Hi Phil,
Thanks for taking the time to respond.
Which location?
/usr/lib64/postgresql /usr/include/postgresql
Hmm. What does: pg_config --includedir --libdir ...say for you?
What OS are you on?
Slackware64 13.1 - postgres 9.1.1 built and installed from source.
"Source" source or "Slackware package" source? (I can't remember how Slackware does it's packaging - isn't it some crazy tarball mashup?)
Plain ./configure works fine for me on RHEL5 and Fedora.
That's good for you but kind of besides the point.. :} I *did* get it
That depends on what you want to achieve... Personally I'd like ./configure to "just work", which I both why I asked your header locations, and cited the fact it DOES "just work" on some systems. I might take a look at calling "pg_config" in ./configure
installed; what I'm saying is that the build process/build requirements w/ an RDBMS back-end aren't really documented.
Well, ./configure --help says: --with-rlm-FOO-lib-dir=DIR Directory to look for library files used by module FOO --with-rlm-FOO-include-dir=DIR Directory to look for include files used by module FOO ...which I assume is what you used in the end? Anyway - if you want to document, document away. The place to do it is the Wiki, since the eventual goal is to include the Wiki docs with the server source AIUI. http://wiki.freeradius.org/Build Perhaps a "Building against non-standard header/library paths" under the "Building from source" section?
On 25 October 2011 06:24, Phil Mayers <p.mayers@imperial.ac.uk> wrote:
/usr/lib64/postgresql /usr/include/postgresql
Hmm.
What does:
pg_config --includedir --libdir
pg_config --includedir --l /usr/include /usr/lib64
Slackware64 13.1 - postgres 9.1.1 built and installed from source. "Source" source or "Slackware package" source?
(I can't remember how Slackware does it's packaging - isn't it some crazy tarball mashup?)
Source proper as downloaded ( ./configure && make && make install ) ... same way I installed postgres (on Slackware) for the last 7 or 8 years.
That's good for you but kind of besides the point.. :} I *did* get it
That depends on what you want to achieve... Personally I'd like ./configure to "just work", which I both why I asked your header locations, and cited the fact it DOES "just work" on some systems.
I might take a look at calling "pg_config" in ./configure
Interesting point. :} In the whole freeradius source tree the only file w/ pg_config in it is ./debian/rules ... I still don't understand HOW it just works on other systems ...
Well, ./configure --help says:
--with-rlm-FOO-lib-dir=DIR Directory to look for library files used by module FOO --with-rlm-FOO-include-dir=DIR Directory to look for include files used by module FOO
...which I assume is what you used in the end?
Anyway - if you want to document, document away. The place to do it is the Wiki, since the eventual goal is to include the Wiki docs with the server source AIUI.
http://wiki.freeradius.org/Build
Perhaps a "Building against non-standard header/library paths" under the "Building from source" section?
I might just do that :} Thanks for the encouraging words. Cheers, Andrej
On 10/24/2011 06:51 PM, Andrej wrote:
pg_config --includedir --l /usr/include /usr/lib64
This "pg_config" is the one from the source you built, yes? There isn't another copy of "pg_config" / the headers lying around? Because with those paths, the build really ought to have "just worked". Weird.
I might take a look at calling "pg_config" in ./configure
Interesting point. :}
In the whole freeradius source tree the only file w/ pg_config in it is ./debian/rules ... I still don't understand HOW it just works on other systems ...
The ./configure script in the rlm_sql_postgresql directory has a list of "directories to try" for the includes/libraries (a pretty common approach)
On Tue, Oct 25, 2011 at 12:51 AM, Andrej <andrej.groups@gmail.com> wrote:
On 25 October 2011 06:24, Phil Mayers <p.mayers@imperial.ac.uk> wrote:
/usr/lib64/postgresql /usr/include/postgresql
Hmm.
What does:
pg_config --includedir --libdir
pg_config --includedir --l /usr/include /usr/lib64
... and that may be your problem Where does your libpq.so.* located? /usr/lib64? /usr/lib64/postgresql? Where does postgres.h located? /usr/include? /usr/include/postgresql? The output of pg_config mismatched with what you said. If the file location matches what pg_config says, it should work. If not, that means you got broken pg_config. -- Fajar
Andrej wrote:
Plain ./configure works fine for me on RHEL5 and Fedora.
That's good for you but kind of besides the point.. :} I *did* get it installed; what I'm saying is that the build process/build requirements w/ an RDBMS back-end aren't really documented.
$ ./configure $ make $ make install This is documented. If the C compiler && linker on your system can't find the include files and libraries... there's little we can do to help. Install things in a standard location. I'll also note that for someone complaining about the lack of documentation, you *don't* say what you did to get it installed. So anyone else finding this thread will be upset at you for "solving" the issue, but then not documenting it. Alan DeKok.
participants (4)
-
Alan DeKok -
Andrej -
Fajar A. Nugraha -
Phil Mayers