Thanks to the people who helped me figure this out (big thanks to Alan), this works perfectly on a fresh Fedora system. Download, compile and install openssl download freeradius 1.1.6 unpack in usr/src cd freeradius-1.1.6 ./configure --prefix=/usr --with-openssl-includes=/usr/local/ssl/include --with-openssl-libraries=/usr/local/ssl/lib/ --disable-libtool-lock --with-system-libtool --sysconfdir=/etc (^all one line) make make install That should also put everything where the rpm normally does (yuck) so should u upgrade later you wont have lib conflicts. All the best.
Hi,
Thanks to the people who helped me figure this out (big thanks to Alan), this works perfectly on a fresh Fedora system.
Download, compile and install openssl
download freeradius 1.1.6 unpack in usr/src cd freeradius-1.1.6
./configure --prefix=/usr --with-openssl-includes=/usr/local/ssl/include --with-openssl-libraries=/usr/local/ssl/lib/ --disable-libtool-lock --with-system-libtool --sysconfdir=/etc (^all one line)
make make install
you SHOULD be able to simply use the redhat spec file that is shipped as part of the contrib sources in that 1.1.6 tarball to make an RPM exactly as the distro should/would supply if they were doing 1.1.6 did you try this? alan
I personally hate rpms and will compile all apps so no, I try rpms as a last resort and Im not surprised when they fail with a big list of dependancies. I will look into it though and test on the next machine and report back. On 4/16/07, A.L.M.Buxey@lboro.ac.uk <A.L.M.Buxey@lboro.ac.uk> wrote:
Hi,
Thanks to the people who helped me figure this out (big thanks to Alan), this works perfectly on a fresh Fedora system.
Download, compile and install openssl
download freeradius 1.1.6 unpack in usr/src cd freeradius-1.1.6
./configure --prefix=/usr --with-openssl-includes=/usr/local/ssl/include --with-openssl-libraries=/usr/local/ssl/lib/ --disable-libtool-lock --with-system-libtool --sysconfdir=/etc (^all one line)
make make install
you SHOULD be able to simply use the redhat spec file that is shipped as part of the contrib sources in that 1.1.6 tarball to make an RPM exactly as the distro should/would supply if they were doing 1.1.6
did you try this?
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I should be more specific, I will compile all specially needed apps after doing a norm installation. Generic stuff like X etc, I dont care about unless it doesnt work. On 4/16/07, Jacob Jarick <mem.namefix@gmail.com> wrote:
I personally hate rpms and will compile all apps so no, I try rpms as a last resort and Im not surprised when they fail with a big list of dependancies.
I will look into it though and test on the next machine and report back.
On 4/16/07, A.L.M.Buxey@lboro.ac.uk <A.L.M.Buxey@lboro.ac.uk> wrote:
Hi,
Thanks to the people who helped me figure this out (big thanks to Alan), this works perfectly on a fresh Fedora system.
Download, compile and install openssl
download freeradius 1.1.6 unpack in usr/src cd freeradius-1.1.6
./configure --prefix=/usr --with-openssl-includes=/usr/local/ssl/include --with-openssl-libraries=/usr/local/ssl/lib/ --disable-libtool-lock --with-system-libtool --sysconfdir=/etc (^all one line)
make make install
you SHOULD be able to simply use the redhat spec file that is shipped as part of the contrib sources in that 1.1.6 tarball to make an RPM exactly as the distro should/would supply if they were doing 1.1.6
did you try this?
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Jacob Jarick wrote:
I personally hate rpms and will compile all apps so no, I try rpms as a last resort and Im not surprised when they fail with a big list of dependancies.
You were not told to pick up a random RPM on the net. The wiki explains how to build yourself a RPM from sources. The resulting package should run without problem on the host where it was compiled. Moreover, building a package allows you to uninstall the files later, so you can cleanly upgrade the version of FreeRADIUS. Residual files from previous installation do weird things, like the problem of "double free" for example. -- Nicolas Baradakis
It wasnt a random rpm and at the time I was unaware that the wiki had been updated to list the latest rpms etc. So binarys are fairly well supported by freeradius I take it. On 4/16/07, Nicolas Baradakis <nbk@sitadelle.com> wrote:
Jacob Jarick wrote:
I personally hate rpms and will compile all apps so no, I try rpms as a last resort and Im not surprised when they fail with a big list of dependancies.
You were not told to pick up a random RPM on the net. The wiki explains how to build yourself a RPM from sources. The resulting package should run without problem on the host where it was compiled.
Moreover, building a package allows you to uninstall the files later, so you can cleanly upgrade the version of FreeRADIUS. Residual files from previous installation do weird things, like the problem of "double free" for example.
-- Nicolas Baradakis
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Mon 16 Apr 2007, Jacob Jarick wrote:
It wasnt a random rpm and at the time I was unaware that the wiki had been updated to list the latest rpms etc. So binarys are fairly well supported by freeradius I take it.
Yep. The general plan is that we spend the time once building an rpm, and then have much less questions on random build problems on various OS' Around 90% of build questions on the list are NOT bugs in freeradius :-) Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
Peter Nixon wrote:
Yep. The general plan is that we spend the time once building an rpm, and then have much less questions on random build problems on various OS'
Ideally, we should have packages on the web site. This is sometimes difficult to do... Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
No probs guys, will check for bins 1st in future. On 4/16/07, Alan DeKok <aland@deployingradius.com> wrote:
Peter Nixon wrote:
Yep. The general plan is that we spend the time once building an rpm, and then have much less questions on random build problems on various OS'
Ideally, we should have packages on the web site. This is sometimes difficult to do...
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I just tried building 1.1.6 as an rpm on suse, it fails with this error. [root@localhost src]# rpmbuild -ba /usr/src/packages/SPECS/freeradius.spec error: File /usr/src/redhat/SOURCES/freeradius-1.1.5.tar.gz: No such file or directory This is corrected instructions Notes: * The wiki glosses over a little and gives u an incorrect dir * the spec file expects 1.1.5 tar.gz # cd /usr/src # tar zxvf /root/Desktop/freeradius-1.1.6.tar.gz # cp /root/Desktop/freeradius-1.1.6.tar.gz /usr/src/redhat/SOURCES/freeradius-1.1.5.tar.gz # cp freeradius-1.1.6/suse/freeradius.spec /usr/src/redhat/SPECS/ # rpmbuild -ba /usr/src/redhat/SPECS/freeradius.spec On 4/16/07, Nicolas Baradakis <nbk@sitadelle.com> wrote:
You were not told to pick up a random RPM on the net. The wiki explains how to build yourself a RPM from sources. The resulting package should run without problem on the host where it was compiled.
participants (5)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Jacob Jarick -
Nicolas Baradakis -
Peter Nixon