RE: Error building version 1.1.1
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nicolas Baradakis wrote:
But the next line shows that installation is done in the parent directory /var/tmp/freeradius-root/usr.
That is what I am seeing. Files are being created in the parent directory (see below), but the symlink is being attempted from lib directory which does not exist. [rdev@e15 usr]# pwd /var/tmp/freeradius-root/usr [rdev@e15 usr]# ls bin libradius-1.1.1.so libradius.a libradius.la libradius.so sbin share -----BEGIN PGP SIGNATURE----- Note: This signature can be verified at https://www.hushtools.com/verify Version: Hush 2.5 wkYEARECAAYFAkQglL8ACgkQmw4BJyaatJ2O/ACgrSMol1U1pxGJKWfe18MYcHW1MaoA n0w8lr3c+EyDX4R7DLhLYcTaQ8v0 =2Zi1 -----END PGP SIGNATURE-----
"Sandworm" <sandworm@mepd.hush.com> wrote:
That is what I am seeing. Files are being created in the parent directory (see below), but the symlink is being attempted from lib directory which does not exist.
The makefile in src/lib creates the lib directory before it installs anything in it. I have no idea why building an RPM would result in things happening in the reverse order. Alan DeKok.
Hi,
The makefile in src/lib creates the lib directory before it installs anything in it. I have no idea why building an RPM would result in things happening in the reverse order.
It doesn't only happen when building an RPM. I installed from the tarball and the same thing happened. It worked when I manually created lib/ after the first failed attempt und tried it a second time (SuSE 8.2). Nicolas Baradakis sent me a patched Makefile, I will try that soon and report back if it fixes the issue. Greetings, Stefan Winter -- Stefan WINTER Stiftung RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche Ingenieur Forschung & Entwicklung 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg E-Mail: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
On Thu, Mar 23, 2006 at 08:19:19AM +0100, Stefan Winter wrote:
Hi,
The makefile in src/lib creates the lib directory before it installs anything in it. I have no idea why building an RPM would result in things happening in the reverse order.
Indeed the installation fails (I used --prefix in configure) and I compiled from sources without trying to make a package of any sort. By searching I found the following patch: Index: Makefile =================================================================== RCS file: /source/radiusd/src/lib/Makefile,v retrieving revision 1.28 diff -u -r1.28 Makefile --- Makefile 22 Jan 2006 21:46:35 -0000 1.28 +++ Makefile 6 Mar 2006 17:51:34 -0000 -48,6 +48,6 rm -rf .libs install: all - $(LIBTOOL) --mode=install $(INSTALL) -c $(TARGET).la $(R)$(libdir) + $(LIBTOOL) --mode=install $(INSTALL) -c $(TARGET).la $(R)$(libdir)/$(TARGET).la rm -f $(R)$(libdir)/$(TARGET)-$(RADIUSD_VERSION).la; ln -s $(TARGET).la $(R)$(libdir)/$(TARGET)-$(RADIUSD_VERSION).la This solved the issue.
It doesn't only happen when building an RPM. I installed from the tarball and the same thing happened. It worked when I manually created lib/ after the first failed attempt und tried it a second time (SuSE 8.2). Nicolas Baradakis sent me a patched Makefile, I will try that soon and report back if it fixes the issue.
Greetings,
Stefan Winter
-- Stefan WINTER
Stiftung RESTENA - Rιseau Tιlιinformatique de l'Education Nationale et de la Recherche Ingenieur Forschung & Entwicklung
6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg E-Mail: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Kostas Zorbadelos m@il contact: kzorba (at) otenet.gr Out there in the darkness, out there in the night out there in the starlight, one soul burns brighter than a thousand suns.
It doesn't only happen when building an RPM. I installed from the tarball and the same thing happened. It worked when I manually created lib/ after the first failed attempt und tried it a second time (SuSE 8.2). Nicolas Baradakis sent me a patched Makefile, I will try that soon and report back if it fixes the issue.
Tested and worked. It would be great to have that patch in cvs. Nicolas? Greetings, Stefan Winter -- Stefan WINTER RESTENA Foundation - Réseau Téléinformatique de l'Education Nationale et de la Recherche R&D Engineer 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg email: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
Stefan Winter wrote:
It doesn't only happen when building an RPM. I installed from the tarball and the same thing happened. It worked when I manually created lib/ after the first failed attempt und tried it a second time (SuSE 8.2). Nicolas Baradakis sent me a patched Makefile, I will try that soon and report back if it fixes the issue.
Tested and worked. It would be great to have that patch in cvs. Nicolas?
Thanks for testing the patch. I needed some feedback because I've no problem to build a Debian package. It's fixed in CVS, and version 1.1.2 will contain the fix. -- Nicolas Baradakis
Hi,
It's fixed in CVS, and version 1.1.2 will contain the fix.
then maybe 1.1.2 should be pushed out _soon_. The current version doesn't install correctly on many platforms... Greetings, Stefan Winter -- Stefan WINTER RESTENA Foundation - Réseau Téléinformatique de l'Education Nationale et de la Recherche R&D Engineer 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg email: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
Stefan Winter wrote:
It's fixed in CVS, and version 1.1.2 will contain the fix.
then maybe 1.1.2 should be pushed out _soon_. The current version doesn't install correctly on many platforms...
From what I read on the mailing list until now, the current version *does* install on any system unless you (or rpmbuild) change installation paths through ./configure options.
I didn't catch the problem before the release of 1.1.1 because on Debian dpkg-buildpackage automatically creates the tree of directories before building the freeradius package. -- Nicolas Baradakis
Before 1.1.1 all was ok, with rpmbuild. Only since 1.1.1 it will fail. I built it on and for Fedora Core 4. Nicolas Baradakis schrieb:
Stefan Winter wrote:
It's fixed in CVS, and version 1.1.2 will contain the fix. then maybe 1.1.2 should be pushed out _soon_. The current version doesn't install correctly on many platforms...
From what I read on the mailing list until now, the current version *does* install on any system unless you (or rpmbuild) change installation paths through ./configure options.
I didn't catch the problem before the release of 1.1.1 because on Debian dpkg-buildpackage automatically creates the tree of directories before building the freeradius package.
participants (6)
-
Alan DeKok -
Frank Büttner -
Kostas Zorbadelos -
Nicolas Baradakis -
Sandworm -
Stefan Winter