Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
On Sunday 31 August 2008 02:24:43 am Nicholas Brealey wrote: Gary Greene wrote: /opt/samba/bin, /opt/samba/lib and RPATH=$ORIGIN/../lib would be OK. /usr/local/bin, /usr/local/lib and RPATH=$ORIGIN/../lib would bad. /usr/bin, /usr/lib and RPATH=$ORIGIN/../lib would be very bad. Nick This is not true. The reason most distributions cannot use RPATH is that when packaging, you build a package into a temp root for the packaging software to turn into a package. In this case, you'd get unusable RPATHs since it'd be sometime like PATH TO BUILDROOT/usr/lib, etc. I don't think this is a valid reason. If you follow the GNU/GNU Make/autoconf guidelines you should be able to do: configure --prefix=/usr/local gmake gmake DESTDIR=/tmp/package install Then package the files in /tmp/package. The Samba Makefile uses DESTDIR. Regards Nick Try it sometime. I'm fairly certain that the rpaths won't be what you're expecting. -- Gary L. Greene, Jr. Sent from: peorth 00:13:39 up 14 min, 3 users, load average: 0.42, 0.88, 0.51 == Developer and Project Lead for the AltimatOS open source project Volunteer Developer for the KDE open source project See http://www.altimatos.com/ and http://www.kde.org/ for more information == Please avoid sending me Word or PowerPoint attachments. signature.asc Description: This is a digitally signed message part. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Gary Greene wrote: /opt/samba/bin, /opt/samba/lib and RPATH=$ORIGIN/../lib would be OK. /usr/local/bin, /usr/local/lib and RPATH=$ORIGIN/../lib would bad. /usr/bin, /usr/lib and RPATH=$ORIGIN/../lib would be very bad. Nick This is not true. The reason most distributions cannot use RPATH is that when packaging, you build a package into a temp root for the packaging software to turn into a package. In this case, you'd get unusable RPATHs since it'd be sometime like PATH TO BUILDROOT/usr/lib, etc. I don't think this is a valid reason. If you follow the GNU/GNU Make/autoconf guidelines you should be able to do: configure --prefix=/usr/local gmake gmake DESTDIR=/tmp/package install Then package the files in /tmp/package. The Samba Makefile uses DESTDIR. Regards Nick -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
On Wednesday 27 August 2008 02:03:55 pm Nicholas Brealey wrote: Brian H. Nelson wrote: Michael Adam wrote: ... What is more, rpath also has some bad effects (when updating libraries, e.g.), so it should not be set unconditionally. Could you elaborate on why/when setting rpath would cause problems? I'm having trouble coming up with an example. I think there was an issue with RPATH in the executable taking higher priority than the LD_LIBRARY_PATH environment variable and Linux distributions updating libraries in a funny way (moving the old libraries to a different directory). On Solaris LD_LIBRARY_PATH always had a higher priority than RPATH although I think this broke some standard. To comply with standards, RUNPATH was introduced which has a lower priority than LD_LIBRARY_PATH matching the behaviour of the Solaris RPATH. The -R option on Solaris now sets both RPATH and RUNPATH but RPATH is ignored when RUNPATH is present. A cannot think of any objection to using -R with $ORIGIN on Solaris. See: http://docs.sun.com/app/docs/doc/817-1984/6mhm7pld8?a=view#indexterm-814 I don't see why there should be a problem on Linux provided the RPATH only includes directories which are part of the Samba build and are exclusive to Samba. /opt/samba/bin, /opt/samba/lib and RPATH=$ORIGIN/../lib would be OK. /usr/local/bin, /usr/local/lib and RPATH=$ORIGIN/../lib would bad. /usr/bin, /usr/lib and RPATH=$ORIGIN/../lib would be very bad. Nick This is not true. The reason most distributions cannot use RPATH is that when packaging, you build a package into a temp root for the packaging software to turn into a package. In this case, you'd get unusable RPATHs since it'd be sometime like PATH TO BUILDROOT/usr/lib, etc. -- Gary L. Greene, Jr. Sent from: peorth 20:43:51 up 3 days, 23:55, 8 users, load average: 0.14, 0.20, 0.22 == Developer and Project Lead for the AltimatOS open source project Volunteer Developer for the KDE open source project See http://www.altimatos.com/ and http://www.kde.org/ for more information == Please avoid sending me Word or PowerPoint attachments. -- Gary L. Greene, Jr. Sent from: peorth 21:55:49 up 3:24, 6 users, load average: 1.27, 0.90, 0.56 == Developer and Project Lead for the AltimatOS open source project Volunteer Developer for the KDE open source project See http://www.altimatos.com/ and http://www.kde.org/ for more information == Please avoid sending me Word or PowerPoint attachments. signature.asc Description: This is a digitally signed message part. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Nicholas Brealey wrote: Brian H. Nelson wrote: Michael Adam wrote: What is more, rpath also has some bad effects (when updating libraries, e.g.), so it should not be set unconditionally. Could you elaborate on why/when setting rpath would cause problems? I'm having trouble coming up with an example. I think there was an issue with RPATH in the executable taking higher priority than the LD_LIBRARY_PATH environment variable and Linux distributions updating libraries in a funny way (moving the old libraries to a different directory). I think that pretty much nails it down. This for instance makes it impossible (on Linux) to make test from a source/build directory with RPATH without doing make install first. On Solaris LD_LIBRARY_PATH always had a higher priority than RPATH although I think this broke some standard. To comply with standards, RUNPATH was introduced which has a lower priority than LD_LIBRARY_PATH matching the behaviour of the Solaris RPATH. The -R option on Solaris now sets both RPATH and RUNPATH but RPATH is ignored when RUNPATH is present. Ah, interesting to know. A cannot think of any objection to using -R with $ORIGIN on Solaris. Why not simple give it the absolute LIBDIR path from configure? By the way, as already stated in another mail: You can link your binaries with any RPATH you like by calling configure this way (without modifications to samba code): LDFLAGS=-R... ./configure --prefix=... ... Cheers - Michael -- Michael Adam [EMAIL PROTECTED] [EMAIL PROTECTED] SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.SerNet.DE, mailto: Info @ SerNet.DE pgp8BcN9ajL6d.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Quoting Dennis Clarke ([EMAIL PROTECTED]): out of more than just idle curiosity .. how are you going to deliver Samba? As one package or as eight or nine little broken up packages such that other packages which have dependencies will need to only install something small? I hope you can see why I am asking. samba in Debian has always (at least for so many years that I can't really remember unless digging in changelogs) been split into several packages: [EMAIL PROTECTED]:~/src/debian/samba/samba-3.2.2/debian$ grep ^Package: control Package: samba Package: samba-common Package: samba-tools Package: smbclient Package: swat Package: samba-doc Package: samba-doc-pdf Package: smbfs Package: libpam-smbpass Package: libsmbclient Package: libsmbclient-dev Package: winbind Package: samba-dbg Package: libwbclient0 I think that anyone can easily spot what is in what package..:-) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Hi folks! Nicholas Brealey wrote: On Solaris I think the best option for packages which have a directory structure like: package/bin package/lib is to link the executables with: -R$ORIGIN/../lib (In a Makefile use: LDFLAGS = -R\$$ORIGIN/../lib) This means the package can installed anywhere and still pick up the correct libraries. Using LD_LIBRARY_PATH or crle is bad practice. Well, we had the discussion of whether to use rpath or LD_LIBRARY_PATH (or ld.so.conf) already on this and/or the samba-technical mailing list. (I should look up that thread...) James Kosin wrote: -Original Message- From: Daniel Eischen [mailto:[EMAIL PROTECTED] Using -rpath/-R is the norm for Solaris packages. Samba already is built with knowledge of where it is installed and where its lib, data, var, etc directories reside. What is _not_ the norm, is having to set LD_LIBRARY_PATH in order for your applications to work. Take a look at all the packages at sunfreeware.com - they are all built for /usr/local and, at least from hundred or so packages I've installed from there, none require LD_LIBRARY_PATH to work when their libraries are in /usr/local/lib. Well on the other hand, in Linux distributions, it is considered bad practise to link using an RPATH. You either put your libs into /usr/lib or /usr/local/lib or else use a ld.so.conf file. So there are advocates for and more significantly against each of rpath and LD_LIBRARY_PATH. I decided not to compile with an RPATH because at that time most people argued that this is a bad thing. 1. easiest solution: put libs into folder searched by dynamic linker (e.g. /usr/lib) 2. next solution: use LD_LIBRARY_PATH when installing to /some/package/dir (or use an ld.so.conf file when available) 3. modify LDFLAGS to use an rpath. I had the plan to provide the option of linking with an rpath as a configure option. But it is not so easy to get it right for all supported platforms (Nicholas only mentioned solaris and Linux...). And I did not have the time yet to complete this in an upstream compliant manner. Patches welcome!! James Kosin wrote: Actually, I'll have to check to see if Michael back-ported the configure option to specify the destination directory for the libraries. The default seems to be in the %prefix/lib/samba directory with many packages moving them to the %prefix/lib directory and keeping the rest in the %prefix/lib/samba structure. * creation and installation of shared libs as filename = SONAME and symlink .so -- .so.VERSION is fixed in samba 3.2.2. (Bug #5592) * splitting of libdir into libdir (for the libs) and modulesdir (for shared modules and such) is done in v3-devel / v3-3-test. This probably won't go into 3.2.X since it is a new feature and not really a bug. This will be 3.3.0 (planned for Dec 15, 2008). Thanks for your thougths and comments. This is much appreciated. Cheers - Michael -- Michael Adam [EMAIL PROTECTED] [EMAIL PROTECTED] SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.SerNet.DE, mailto: Info @ SerNet.DE pgpVo0Cv87h4V.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Michael Adam wrote: Hi folks! Nicholas Brealey wrote: James Kosin wrote: -Original Message- From: Daniel Eischen [mailto:[EMAIL PROTECTED] Using -rpath/-R is the norm for Solaris packages. Samba already is built with knowledge of where it is installed and where its lib, data, var, etc directories reside. What is _not_ the norm, is having to set LD_LIBRARY_PATH in order for your applications to work. Take a look at all the packages at sunfreeware.com - they are all built for /usr/local and, at least from hundred or so packages I've installed from there, none require LD_LIBRARY_PATH to work when their libraries are in /usr/local/lib. I had the plan to provide the option of linking with an rpath as a configure option. But it is not so easy to get it right for all supported platforms (Nicholas only mentioned solaris and Linux...). And I did not have the time yet to complete this in an upstream compliant manner. Patches welcome!! To be more concrete: I suggest adding a configure option --enable-rpath that adds the appropriate LDFLAGS when appropriate for the build system (e.g. solaris and linux for a start) and gives notice when the system is unsupported (for rpath). See http://gitweb.samba.org/?p=samba.git;a=commit;h=3a0f781352f364ce625a35ffd78257b27d984c47 and http://gitweb.samba.org/?p=samba.git;a=commitdiff;h=6850dc242b010bdcef5e427e51be04201f55b7f3 for what has already been in the sources and has been removed. By the way: It is not strictly necessary to modify the sources to create binaries linked with an rpath: By setting an appropriate LDFLAGS environment variable containing an RPATH option before calling configure, you can use an RPATH option for your install without modifying the sources, since the configure script picks up any externally set LDFLAGS and CFLAGS settings! ... :-) Cheers - Michael -- Michael Adam [EMAIL PROTECTED] [EMAIL PROTECTED] SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-37-0, fax: +49-551-37-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.SerNet.DE, mailto: Info @ SerNet.DE pgpEZP5KAXBCl.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Michael Adam wrote: To be more concrete: I suggest adding a configure option --enable-rpath that adds the appropriate LDFLAGS when appropriate for the build system (e.g. solaris and linux for a start) and gives notice when the system is unsupported (for rpath). See http://gitweb.samba.org/?p=samba.git;a=commit;h=3a0f781352f364ce625a35ffd78257b27d984c47 and http://gitweb.samba.org/?p=samba.git;a=commitdiff;h=6850dc242b010bdcef5e427e51be04201f55b7f3 for what has already been in the sources and has been removed. From link #2: What is more, rpath also has some bad effects (when updating libraries, e.g.), so it should not be set unconditionally. Could you elaborate on why/when setting rpath would cause problems? I'm having trouble coming up with an example. Thanks, -Brian -- --- Brian H. Nelson Youngstown State University System Administrator Media and Academic Computing bnelson[at]cis.ysu.edu --- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
On Wed, 27 Aug 2008, Michael Adam wrote: Michael Adam wrote: Hi folks! Nicholas Brealey wrote: James Kosin wrote: -Original Message- From: Daniel Eischen [mailto:[EMAIL PROTECTED] Using -rpath/-R is the norm for Solaris packages. Samba already is built with knowledge of where it is installed and where its lib, data, var, etc directories reside. What is _not_ the norm, is having to set LD_LIBRARY_PATH in order for your applications to work. Take a look at all the packages at sunfreeware.com - they are all built for /usr/local and, at least from hundred or so packages I've installed from there, none require LD_LIBRARY_PATH to work when their libraries are in /usr/local/lib. I had the plan to provide the option of linking with an rpath as a configure option. But it is not so easy to get it right for all supported platforms (Nicholas only mentioned solaris and Linux...). And I did not have the time yet to complete this in an upstream compliant manner. Patches welcome!! To be more concrete: I suggest adding a configure option --enable-rpath that adds the appropriate LDFLAGS when appropriate for the build system (e.g. solaris and linux for a start) and gives notice when the system is unsupported (for rpath). Yes, it if is not on be default, then having a knob to enable it is the next best thing. See http://gitweb.samba.org/?p=samba.git;a=commit;h=3a0f781352f364ce625a35ffd78257b27d984c47 and http://gitweb.samba.org/?p=samba.git;a=commitdiff;h=6850dc242b010bdcef5e427e51be04201f55b7f3 for what has already been in the sources and has been removed. By the way: It is not strictly necessary to modify the sources to create binaries linked with an rpath: By setting an appropriate LDFLAGS environment variable containing an RPATH option before calling configure, you can use an RPATH option for your install without modifying the sources, since the configure script picks up any externally set LDFLAGS and CFLAGS settings! ... :-) That is nice to know too. -- DE -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Brian H. Nelson wrote: Michael Adam wrote: ... What is more, rpath also has some bad effects (when updating libraries, e.g.), so it should not be set unconditionally. Could you elaborate on why/when setting rpath would cause problems? I'm having trouble coming up with an example. I think there was an issue with RPATH in the executable taking higher priority than the LD_LIBRARY_PATH environment variable and Linux distributions updating libraries in a funny way (moving the old libraries to a different directory). On Solaris LD_LIBRARY_PATH always had a higher priority than RPATH although I think this broke some standard. To comply with standards, RUNPATH was introduced which has a lower priority than LD_LIBRARY_PATH matching the behaviour of the Solaris RPATH. The -R option on Solaris now sets both RPATH and RUNPATH but RPATH is ignored when RUNPATH is present. A cannot think of any objection to using -R with $ORIGIN on Solaris. See: http://docs.sun.com/app/docs/doc/817-1984/6mhm7pld8?a=view#indexterm-814 I don't see why there should be a problem on Linux provided the RPATH only includes directories which are part of the Samba build and are exclusive to Samba. /opt/samba/bin, /opt/samba/lib and RPATH=$ORIGIN/../lib would be OK. /usr/local/bin, /usr/local/lib and RPATH=$ORIGIN/../lib would bad. /usr/bin, /usr/lib and RPATH=$ORIGIN/../lib would be very bad. Nick -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Since all I saw were bugfixes, no feature changes - do we need to *gently* press the Debian team to use 3.2.2, instead of 3.2.1? -- Daniel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
On Tue, Aug 26, 2008 at 03:42:13PM -0700, Daniel L. Miller wrote: Since all I saw were bugfixes, no feature changes - do we need to *gently* press the Debian team to use 3.2.2, instead of 3.2.1? That would help -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Quoting Jeremy Allison ([EMAIL PROTECTED]): On Tue, Aug 26, 2008 at 03:42:13PM -0700, Daniel L. Miller wrote: Since all I saw were bugfixes, no feature changes - do we need to *gently* press the Debian team to use 3.2.2, instead of 3.2.1? That would help We're doing our best, folks. 3.2.2 packages are ready (working the package wasn't that straightforward after some binary renaming that happened for cifs utilities..as well as some (good) changes to libraries installation). 3.2.1 entered testing two days ago and we now need to talk with our release team to get a pre-agreement by them that they will accept 3.2.2 for lenny. Steve Langasek is the one who know how to write such mails (he combines two qualities I don't have: being an English native speaker and understandign Samba's code...:-) ). We also have issues we need to work on: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495653 has to be reported to you guys http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496073 is also a concern. This is Bugzilla bug #5715... I think we'll make it, indeed. But, at least for #496073, we know we'll need another upload for a very probably 3.2.3...:-) As, and that's a major difference with, say OpenSuse packaging, all this happens on our unpaid time, we sometimes lag behind the two efficient Samba developers...-) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Quoting Jeremy Allison ([EMAIL PROTECTED]): On Tue, Aug 26, 2008 at 03:42:13PM -0700, Daniel L. Miller wrote: Since all I saw were bugfixes, no feature changes - do we need to *gently* press the Debian team to use 3.2.2, instead of 3.2.1? That would help We're doing our best, folks. 3.2.2 packages are ready (working the package wasn't that straightforward after some binary renaming that happened for cifs utilities..as well as some (good) changes to libraries installation). out of more than just idle curiosity .. how are you going to deliver Samba? As one package or as eight or nine little broken up packages such that other packages which have dependencies will need to only install something small? I hope you can see why I am asking. Dennis -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Evans Sent: Thursday, August 21, 2008 10:00 PM Subject: Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download Karolin Seeger wrote: o Fix creation and installation of shared libraries. On Solaris 10 (Solaris 10 5/08 s10s_u5wos_10 SPARC), the build completes, but starting the daemons results in: # /etc/init.d/samba start ld.so.1: smbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed ld.so.1: nmbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed Configure command was: CC=cc ./configure --with-acl-support --with-included-popt --with-ldap=no --with-ads=no Previously, the make failed with reference to the same shared libs, as was reported by others on this list. Tim, You still may have to move the libraries to their normal spot or make an entry in /etc/ld.so.conf to point to the directory where the libraries are kept for samba. James -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download]
Karolin Seeger wrote: o Fix creation and installation of shared libraries. On Solaris 10 (Solaris 10 5/08 s10s_u5wos_10 SPARC), the build completes, but starting the daemons results in: # /etc/init.d/samba start ld.so.1: smbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed ld.so.1: nmbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed Configure command was: CC=cc ./configure --with-acl-support --with-included-popt --with-ldap=no --with-ads=no Previously, the make failed with reference to the same shared libs, as was reported by others on this list. -- Tim Evans, TKEvans.com, Inc.| 5 Chestnut Court UNIX System Admin Consulting| Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
James Kosin wrote: Tim, You still may have to move the libraries to their normal spot or make an entry in /etc/ld.so.conf to point to the directory where the libraries are kept for samba. James On Solaris, one uses the crle command to achieve the same result. Aside from that, I believe that the general practice for packages that include their own libraries is to hard-code the libpath into any applicable binaries using '-rpath $prefix/lib' in the linking step (or '-R $prefix/lib' with Solaris ld). If you install samba into its own area (say /usr/local/samba) and the libraries are installed in a non-system location (perhaps /usr/local/samba/lib), messing with the runtime linker config to make samba work should NOT be required. -Brian -- --- Brian H. Nelson Youngstown State University System Administrator Media and Academic Computing bnelson[at]cis.ysu.edu --- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
On 21.08-21:42, Tim Evans wrote: Karolin Seeger wrote: o Fix creation and installation of shared libraries. On Solaris 10 (Solaris 10 5/08 s10s_u5wos_10 SPARC), the build completes, but starting the daemons results in: # /etc/init.d/samba start ld.so.1: smbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed ld.so.1: nmbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed Configure command was: CC=cc ./configure --with-acl-support --with-included-popt --with-ldap=no --with-ads=no Previously, the make failed with reference to the same shared libs, as was reported by others on this list. Add something like export LDFLAGS=-L/usr/lib/samba -R/usr/lib/samba to your environment, with paths pointing to where the samba libs are going to be installed. -- -- Christoph Kaegi [EMAIL PROTECTED] -- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
-Original Message- From: Brian H. Nelson [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 9:18 AM To: James Kosin Cc: [EMAIL PROTECTED]; samba@lists.samba.org Subject: Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download James Kosin wrote: Tim, You still may have to move the libraries to their normal spot or make an entry in /etc/ld.so.conf to point to the directory where the libraries are kept for samba. James On Solaris, one uses the crle command to achieve the same result. Aside from that, I believe that the general practice for packages that include their own libraries is to hard-code the libpath into any applicable binaries using '-rpath $prefix/lib' in the linking step (or '-R $prefix/lib' with Solaris ld). If you install samba into its own area (say /usr/local/samba) and the libraries are installed in a non-system location (perhaps /usr/local/samba/lib), messing with the runtime linker config to make samba work should NOT be required. -Brian Well anyway, the problem is that ld cannot find the dynamic runtime libraries for samba. This is a common problem when the libraries are not installed in the correct place or ld is not told the new location for the required libraries. I yield the rest of the discussion to Brian who is a Solaris EXPERT. :- James -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
On Fri, 22 Aug 2008, Brian H. Nelson wrote: James Kosin wrote: Tim, You still may have to move the libraries to their normal spot or make an entry in /etc/ld.so.conf to point to the directory where the libraries are kept for samba. James On Solaris, one uses the crle command to achieve the same result. Aside from that, I believe that the general practice for packages that include their own libraries is to hard-code the libpath into any applicable binaries using '-rpath $prefix/lib' in the linking step (or '-R $prefix/lib' with Solaris ld). If you install samba into its own area (say /usr/local/samba) and the libraries are installed in a non-system location (perhaps /usr/local/samba/lib), messing with the runtime linker config to make samba work should NOT be required. Exactly! I had the same problem, I believe with 3.0.31. I think I solved it by editing the Makefile (after configuring samba) to add '-R $prefix/lib' as described above. On Solaris, the configure step _should_ generate a Makefile with the -R (or -rpath) option above, but it does not. -- DE -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
On Fri, 22 Aug 2008, Christoph Kaegi wrote: On 21.08-21:42, Tim Evans wrote: Karolin Seeger wrote: o Fix creation and installation of shared libraries. On Solaris 10 (Solaris 10 5/08 s10s_u5wos_10 SPARC), the build completes, but starting the daemons results in: # /etc/init.d/samba start ld.so.1: smbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed ld.so.1: nmbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed Configure command was: CC=cc ./configure --with-acl-support --with-included-popt --with-ldap=no --with-ads=no Previously, the make failed with reference to the same shared libs, as was reported by others on this list. Add something like export LDFLAGS=-L/usr/lib/samba -R/usr/lib/samba to your environment, with paths pointing to where the samba libs are going to be installed. This is a band-aid. The binaries should be rebuilt with the linker's -R or -rpath option. -- DE -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
-Original Message- From: Daniel Eischen [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 11:44 AM To: Brian H. Nelson Cc: James Kosin; samba@lists.samba.org Subject: Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download On Fri, 22 Aug 2008, Brian H. Nelson wrote: James Kosin wrote: Tim, You still may have to move the libraries to their normal spot or make an entry in /etc/ld.so.conf to point to the directory where the libraries are kept for samba. James On Solaris, one uses the crle command to achieve the same result. Aside from that, I believe that the general practice for packages that include their own libraries is to hard-code the libpath into any applicable binaries using '-rpath $prefix/lib' in the linking step (or '-R $prefix/lib' with Solaris ld). If you install samba into its own area (say /usr/local/samba) and the libraries are installed in a non-system location (perhaps /usr/local/samba/lib), messing with the runtime linker config to make samba work should NOT be required. Exactly! I had the same problem, I believe with 3.0.31. I think I solved it by editing the Makefile (after configuring samba) to add '-R $prefix/lib' as described above. On Solaris, the configure step _should_ generate a Makefile with the -R (or -rpath) option above, but it does not. -- DE Maybe, we should have an option. Packagers don't really want or need to modify their 'ld' settings with the '-R' option. Or really install in the same path as the destination system for packaging. Is the ld -R option only temporary; or does this add an entry in the ld.so.cache for future reference? Sorry, I'm a bit ignorant and have been out of touch. The bigger issue may be having the libraries actually being installed in a shared area known by ld on the destination system, as oppose to HARD CODING or RE-CONFIGURING ld to accept a new location hmmm The '-rpath' option would cause issues if a third party developed tools that linked to libnetapi.so in the normal way of using '-lnetapi'... causing confusion when porting to another platform where the libraries may/could be located elsewhere. The -R option looks harmless enough; but, packagers (RPM, etc) might take notice of ld not operating correctly after building a package for release. James -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
James Kosin wrote: Maybe, we should have an option. Packagers don't really want or need to modify their 'ld' settings with the '-R' option. Or really install in the same path as the destination system for packaging. The odd thing is that the 3.0.x series works correctly, with no diddling of configure options or the makefile. -- Tim Evans, TKEvans.com, Inc.| 5 Chestnut Court UNIX System Admin Consulting| Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
James Kosin wrote: Maybe, we should have an option. Packagers don't really want or need to modify their 'ld' settings with the '-R' option. Or really install in the same path as the destination system for packaging. The odd thing is that the pre-3.2 series works correctly, with no diddling of configure options or the makefile. -- Tim Evans, TKEvans.com, Inc.| 5 Chestnut Court UNIX System Admin Consulting| Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
-Original Message- From: Tim Evans [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 1:37 PM To: James Kosin Cc: Daniel Eischen; Brian H. Nelson; samba@lists.samba.org Subject: RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download James Kosin wrote: Maybe, we should have an option. Packagers don't really want or need to modify their 'ld' settings with the '-R' option. Or really install in the same path as the destination system for packaging. The odd thing is that the pre-3.2 series works correctly, with no diddling of configure options or the makefile. Maybe this got broken with the changes to the library builds. Several libraries were added and the linking and link creation were fixed. Or maybe someone broke the Solaris options somewhere in the configure script. James -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
On Fri, 22 Aug 2008, James Kosin wrote: -Original Message- From: Daniel Eischen [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 11:44 AM To: Brian H. Nelson Cc: James Kosin; samba@lists.samba.org Subject: Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download On Fri, 22 Aug 2008, Brian H. Nelson wrote: James Kosin wrote: Tim, You still may have to move the libraries to their normal spot or make an entry in /etc/ld.so.conf to point to the directory where the libraries are kept for samba. James On Solaris, one uses the crle command to achieve the same result. Aside from that, I believe that the general practice for packages that include their own libraries is to hard-code the libpath into any applicable binaries using '-rpath $prefix/lib' in the linking step (or '-R $prefix/lib' with Solaris ld). If you install samba into its own area (say /usr/local/samba) and the libraries are installed in a non-system location (perhaps /usr/local/samba/lib), messing with the runtime linker config to make samba work should NOT be required. Exactly! I had the same problem, I believe with 3.0.31. I think I solved it by editing the Makefile (after configuring samba) to add '-R $prefix/lib' as described above. On Solaris, the configure step _should_ generate a Makefile with the -R (or -rpath) option above, but it does not. -- DE Maybe, we should have an option. Packagers don't really want or need to modify their 'ld' settings with the '-R' option. Or really install in the same path as the destination system for packaging. Is the ld -R option only temporary; or does this add an entry in the ld.so.cache for future reference? Sorry, I'm a bit ignorant and have been out of touch. It only affects the binaries produced when using the option. Packages/binaries can be built by any user, -R doesn't require root privileges. The bigger issue may be having the libraries actually being installed in a shared area known by ld on the destination system, as oppose to HARD CODING or RE-CONFIGURING ld to accept a new location hmmm The '-rpath' option would cause issues if a third party developed tools that linked to libnetapi.so in the normal way of using '-lnetapi'... causing confusion when porting to another platform where the libraries may/could be located elsewhere. The -R option looks harmless enough; but, packagers (RPM, etc) might take notice of ld not operating correctly after building a package for release. Using -rpath/-R is the norm for Solaris packages. Samba already is built with knowledge of where it is installed and where its lib, data, var, etc directories reside. What is _not_ the norm, is having to set LD_LIBRARY_PATH in order for your applications to work. Take a look at all the packages at sunfreeware.com - they are all built for /usr/local and, at least from hundred or so packages I've installed from there, none require LD_LIBRARY_PATH to work when their libraries are in /usr/local/lib. -- DE -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
-Original Message- From: Daniel Eischen [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 3:34 PM To: James Kosin Cc: Brian H. Nelson; samba@lists.samba.org Subject: RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download Using -rpath/-R is the norm for Solaris packages. Samba already is built with knowledge of where it is installed and where its lib, data, var, etc directories reside. What is _not_ the norm, is having to set LD_LIBRARY_PATH in order for your applications to work. Take a look at all the packages at sunfreeware.com - they are all built for /usr/local and, at least from hundred or so packages I've installed from there, none require LD_LIBRARY_PATH to work when their libraries are in /usr/local/lib. -- DE Actually, I'll have to check to see if Michael back-ported the configure option to specify the destination directory for the libraries. The default seems to be in the %prefix/lib/samba directory with many packages moving them to the %prefix/lib directory and keeping the rest in the %prefix/lib/samba structure. James K. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
On Solaris I think the best option for packages which have a directory structure like: package/bin package/lib is to link the executables with: -R$ORIGIN/../lib (In a Makefile use: LDFLAGS = -R\$$ORIGIN/../lib) This means the package can installed anywhere and still pick up the correct libraries. Using LD_LIBRARY_PATH or crle is bad practice. On Linux you can get similar results by linking with: -Wl,-zorigin,-rpath,$ORIGIN/../lib (In a Makefile use: LDFLAGS = -Wl,-zorigin,-rpath,\$$ORIGIN/../lib) The use of $ORIGIN is an unfortunate design choice because of $ having a special meaning in shells and make. In can be hard or impossible to work out the correct level of quoting required with configure scripts so it is often easiest just to edit the Makefiles after they have been generated by the configure script. libtool is a real pain: I have not yet worked out how to get libtool to use $ORIGIN in the RUNPATH. Nick James Kosin wrote: -Original Message- From: Daniel Eischen [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 3:34 PM To: James Kosin Cc: Brian H. Nelson; samba@lists.samba.org Subject: RE: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download Using -rpath/-R is the norm for Solaris packages. Samba already is built with knowledge of where it is installed and where its lib, data, var, etc directories reside. What is _not_ the norm, is having to set LD_LIBRARY_PATH in order for your applications to work. Take a look at all the packages at sunfreeware.com - they are all built for /usr/local and, at least from hundred or so packages I've installed from there, none require LD_LIBRARY_PATH to work when their libraries are in /usr/local/lib. -- DE Actually, I'll have to check to see if Michael back-ported the configure option to specify the destination directory for the libraries. The default seems to be in the %prefix/lib/samba directory with many packages moving them to the %prefix/lib directory and keeping the rest in the %prefix/lib/samba structure. James K. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] [ANNOUNCE] Samba 3.2.2 Available for Download
Karolin Seeger wrote: o Fix creation and installation of shared libraries. On Solaris 10 (Solaris 10 5/08 s10s_u5wos_10 SPARC), the build completes, but starting the daemons results in: # /etc/init.d/samba start ld.so.1: smbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed ld.so.1: nmbd: fatal: libtalloc.so.1: open failed: No such file or directory Killed Configure command was: CC=cc ./configure --with-acl-support --with-included-popt --with-ldap=no --with-ads=no Previously, the make failed with reference to the same shared libs, as was reported by others on this list. -- Tim Evans, TKEvans.com, Inc.| 5 Chestnut Court UNIX System Admin Consulting| Owings Mills, MD 21117 http://www.tkevans.com/ | 443-394-3864 http://www.come-here.com/News/ | [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
