On Tue, Sep 09, 2008 at 03:28:15PM -0600, Greg Woods wrote:
On Tue, 2008-09-09 at 15:24 -0400, John Dennis wrote:
Wildcards passed to commands must always be quoted or escaped
Well, no, not always any more. If I did something like cd /root first,
then the yum commands work just fine. It's
Hi,
asked me if I would try building the current pre-release. Since some of
the things supposedly fixed were compile problems on systems similar to
mine, I went ahead and went through the extra effort. Hopefully the
feedback provided from that was useful.
yes. but, as I mentioned, would you
On Wed, 2008-09-10 at 08:20 +0100, [EMAIL PROTECTED] wrote:
would you prefer to have a nightly
tarball of the files to be able to perform this function
rather than having to be familiar with a revision control
system which might not be present for your chosen platform?
All other things
Greg Woods wrote:
All other things being equal: yes, it would be nice not to have to
install an entire revision control system just to fetch the most recent
version of the code.
I've been trying to keep the git repository pushed to github:
I am running on CentOS 5.2 on an x86_64 architecture. I note a previous
report for a similar system here on the list, but this is not the same
error. That one was an error compiling radmin, this is an error
compiling the server:
gcc -g -O2 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall
Greg Woods wrote:
I am running on CentOS 5.2 on an x86_64 architecture. I note a previous
report for a similar system here on the list, but this is not the same
error. That one was an error compiling radmin, this is an error
compiling the server:
...
Alan DeKok wrote:
Greg Woods wrote:
I am running on CentOS 5.2 on an x86_64 architecture. I note a previous
report for a similar system here on the list, but this is not the same
error. That one was an error compiling radmin, this is an error
compiling the server:
...
1.1.7 also requires ltdl
(CentOS 5.x)
Alan DeKok wrote:
Greg Woods wrote:
I am running on CentOS 5.2 on an x86_64 architecture. I note a previous
report for a similar system here on the list, but this is not the same
error. That one was an error compiling radmin, this is an error
compiling
On Tue, 2008-09-09 at 16:53 +0100, [EMAIL PROTECTED] wrote:
yep, you havent got all the required development packages installed.
libtool-ltdl-devel
libtool-ltdl
Thanks, that was it. However, I discovered what I think is a bug in yum
in the process. I tried yum list *ltdl* and this failed to
Marinko Tarlac wrote:
1.1.7 also requires ltdl
The only changes made to 1.1.x from now on will be security related.
i.e. no new features. no build fixes, etc.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Greg Woods wrote:
After this I ran into the previously-noted issue compiling radmin. In
Makefile.inc, define LIBREADLINE as -lreadline -lncurses.
Which is also fixed in git.freeradius.org.
But I now have 2.1.0 compiled so I can work on setting up dynamic
clients, which is a feature we
Hi,
Marinko Tarlac wrote:
1.1.7 also requires ltdl
The only changes made to 1.1.x from now on will be security related.
i.e. no new features. no build fixes, etc.
I dont think it was a build fix request - more a comment
that 1.1.7 needs ltdl on some platforms due to the way
that
On Tue, 2008-09-09 at 19:50 +0200, Alan DeKok wrote:
Please checkout and build git.freeradius.org.
If I get time to do this before 2.1.1 comes out, I'll give it a shot,
but there are no git packages for CentOS and I've never used it before,
so I'll have to install git on my Fedora 9
On Tue, 2008-09-09 at 18:54 +0100, [EMAIL PROTECTED] wrote:
generally, its blindingly obvious when you see something like
Error - libfoo.h missing
you think, hmmm, i dont have an include.
But if libfoo.h actually exists in the source tree (as in the case of
ltdl.h), then it's not so
Yes I know... (
Last few weeks I'm trying to build test system for 2.x.x version. I want
to test DHCP functions.
All systems we have are already in use and I don't have enough space
to do some testings :)
Alan DeKok wrote:
Marinko Tarlac wrote:
1.1.7 also requires ltdl
The
On Tue, 2008-09-09 at 19:50 +0200, Alan DeKok wrote:
Please checkout and build git.freeradius.org.
OK, I got this done. It configures and makes on my system (CentOS
release 5.2 (Final) -- x86_64) with no problems. Now on to some fun with
dynamic clients.
--Greg
-
List
On Tue, 2008-09-09 at 11:24 -0600, Greg Woods wrote:
On Tue, 2008-09-09 at 16:53 +0100, [EMAIL PROTECTED] wrote:
yep, you havent got all the required development packages installed.
libtool-ltdl-devel
libtool-ltdl
Thanks, that was it. However, I discovered what I think is a bug in
On Tue, 2008-09-09 at 19:43 +0100, John Horne wrote:
Does something a bit more generic like 'yum list *td*' show you a list
of installed and available packages? It works for me on CentOS 5.2,
AAAUGH! I got it figured out. I was in the freeradius-server directory
when I tried this, so it turns
John Dennis wrote:
I know the freeradius source tree and source tarball contains rpm spec
files and some suse and redhat specific info but I wonder if that is the
right place for that information, the distribution in question will have
up to date spec files specific to their distributions, I'm
Hi,
But if libfoo.h actually exists in the source tree (as in the case of
ltdl.h), then it's not so blindingly obvious that the problem is a
missing -devel package rather than a configuration/compilation issue.
but you chose to use the system stuff in the configure stage
rather than the
Hi,
OK, I got this done. It configures and makes on my system (CentOS
congrats! - GIT is far nicer than some of the older methods of
source retrieval.
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
Nah! We've all done things like this more times than we care to admit.
Welcome to the club, your turn to bring refreshments next time :-)
hey! you cant skip *your* turn! ;-)
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Tue, 2008-09-09 at 15:24 -0400, John Dennis wrote:
Wildcards passed to commands must always be quoted or escaped
Well, no, not always any more. If I did something like cd /root first,
then the yum commands work just fine. It's a bash feature that if the
wildcard doesn't actually match
On Tue, 2008-09-09 at 15:17 -0400, John Dennis wrote:
I'm inclined to think for those people who wish to build from upstream
they are better off using the autotools configure script included in
the freeradius source distribution and not use rpm mechanisms
Yes, but there are still packages
On Tue, 2008-09-09 at 21:56 +0100, [EMAIL PROTECTED] wrote:
but you chose to use the system stuff in the configure stage
rather than the supplied version, yes?
Much of the time, by the time I get around to wanting to build
freeradius, it's been months since the server was installed, so I don't
Hi,
CentOS box for configure and make. Just a bit more of a pain than
downloading a release tar file.
but thats the point...the stuff you want isnt in a release tar
just yet - a nightly tarball, i guess, would be what you would
prefer for this sort of action?
alan
-
List
Hi,
Much of the time, by the time I get around to wanting to build
freeradius, it's been months since the server was installed, so I don't
really know what's installed on it unless I check. I do know that when
include files are not found, it might mean a -devel package needs to be
installed.
On Tue, 2008-09-09 at 22:48 +0100, [EMAIL PROTECTED] wrote:
a nightly tarball, i guess, would be what you would
prefer for this sort of action?
What I generally prefer is to wait for a stable release. For my own
needs, I could well have done that this time too. But in this case, Alan
asked me
Greg Woods wrote:
Hopefully the feedback provided from that was useful.
Yes.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
29 matches
Mail list logo
